Robert,
I think that I might have been unclear,
- I understand that RFC 8200 does not use normative language, nor MUST
neither RECOMMENDED, just normal English "recommended". I also
understand that this is fine for the situation before draft-ali-6man-
spring-srv6-oam, we recommend an order for the extension headers, but
nothing bad happens if that order is not strictly followed.
- What Rajesh comment seems to imply is that it will fore draft-
ali-6man-spring-srv6-oam as long recommended the ordering is kept.
- what I was wondering was if it is possible to demonstrate that it
will not work if the recommended ordering is not kept.
- and a follow up to this, if it is possible to demonstrate that it will
not work if the recommended is not kept, should we in this case mnake
the now "recommended" order "MANDATORY"?
/Loa
On 2019-05-23 16:31, Robert Raszuk wrote:
Hi Loa,
On Thu, May 23, 2019 at 5:42 AM Loa Andersson <[email protected]
<mailto:[email protected]>> wrote:
Rajesh,
It seems to me that "it is recommended" indicate that the ordering is
optional/OPTIONAL.
Indeed. There is no MUST there. That is precisely what section 4.1 of
RFC8200 says:
4.1 <https://tools.ietf.org/html/rfc8200#section-4.1>. Extension
Header Order
When more than one extension header is used in the same packet, it is
* recommended *that those headers appear in the following order:
Does this document (or your comment) create a
MANDATORY ordering of EH's??
If by "this document" you mean draft-ali-6man-spring-srv6-oam then no -
I do not see any text there which would even attempt to enforce any EH
ordering.
As far as creating MANDATORY ordering "by a comment" that must be pretty
new extension to the IETF process :)
Best,
R..
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
--
Loa Andersson email: [email protected]
Senior MPLS Expert
Bronze Dragon Consulting phone: +46 739 81 21 64
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
