[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    RE: <draft-hinden-6man-rfc2460bis-04.txt>
From:       "Manfredi, Albert E" <albert.e.manfredi () boeing ! com>
Date:       2015-08-14 21:25:43
Message-ID: 021E64FECA7E5A4699562F4E66716481534F5ED8 () XCH-PHX-503 ! sw ! nos ! boeing ! com
[Download RAW message or body]

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Bob Hinden

> Please review this draft to verify that the changes are appropriate.
> 
> This is part of the project to move the core IPv6 specifications to Internet
> Standard.

Bob, not specifically responding to those changes you made, but to the more general \
topic of RFC 2460bis, is there any reason why RFC 791 Appendix B is not being \
included in these RFCs? That's the one that specifies the bit numbering order and the \
byte transmission sequence.

Last time I asked, the general response was that "any sane person would do it this \
way." But the fact is, I keep running into vendors who don't. A cut and paste of that \
old appendix B would do the trick, pretty much.

Thanks.

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread]