Section 2 “Scope of the Ethernet based OAM ACH Type” contains the following text:
"The code point allocated by this document is intended to be used only for Ethernet based OAM messages, defined in the ITU-T Recommendation [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages and procedures, address the OAM functional requirements defined in [RFC5860]. Other message types should not be carried behind this code point."
The restrictions on the future use of the code point could be made more explicit by modifying the text as follows:
The code point allocated by this document should only be used for Ethernet based OAM messages, defined in the ITU-T Recommendation [G.8113.1], carried in the G-ACh. The messages and procedures carried behind this code point, are restricted to only those that the address the OAM functional requirements defined in [RFC5860]. Other message types should not be carried behind this code point.
I hope that this addresses your concern.
Regards,
Malcolm
| "Sprecher, Nurit (NSN
- IL/Hod HaSharon)" <nurit.sprecher@xxxxxxx>
14/03/2012 06:43 AM |
|
Malcolm,
As mentioned before, I cannot support the publication of the current version of draft-betts...it must be revised first to address the concerns I and others raised on the list.
Maybe you could clarify how the text in your draft can be improved to protect the use of the code point from future extensions beyond the purpose of the code point allocation?
Best regards,
Nurit
________________________________
>-------------------------snip
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf