[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Selector fields for ICMP in Arch doc
-----BEGIN PGP SIGNED MESSAGE-----
One point that I think ICMP group is unanimous is that the SPD/SAD support
for ICMP. We feel that it should be extended to include ICMP type and code
fields as selectors.
Matt Crawford has suggested that since the architecture document provides
a minimum set, the IPv6 people can impose additional requirements if they
need.
The question is do we want to make these an item for the IPv4 Standard's
Arch document? I suggest that the text read like:
"An implementation MAY support ICMP as a selector for the SAD. If an
implementation does support ICMP, then it MUST support both ICMP
type and code as selectors"
Stephen? What say you?
This has ramifications for IKE as well: however, if you consider type/code
to be a 16 bit item, you might pretend that it is the "port" field. I suggest
that type be made the MSB and code the LSB.
[do we have RFCs yet???? Do we even have numbers?]
:!mcr!: | Solidum Systems Corporation, http://www.solidum.com
Michael Richardson |For a better connected world,where data flows faster<tm>
Personal: <A HREF="http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html">mcr@sandelman.ottawa.on.ca</A>. PGP key available.
Corporate: <A HREF="mailto:mcr@solidum.com">mcr@solidum.com</A>.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBNlBVtG5vCG0TOZrRAQHa1gP+N75TxUHvxvvcseZdOvstZksB0RGEzm9g
/zQ4QVuB0gWrhv+JMiATieJ9JjgWOXV8qV7f/S0WqKGg7jRVfBCIWvaQ4YpHXd8d
+t/RaaSutfTS9e08OnJbwS6F9ZrmsPzfui2NAYJ6nn1drf4y6+KDQf/HFYMK8w8z
bmtj7w4XJnY=
=O2p1
-----END PGP SIGNATURE-----
Follow-Ups: