[Last-Call] Yangdoctors last call review of draft-ietf-bfd-large-packets-07

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Reviewer: Jürgen Schönwälder
Review result: Almost Ready

This is	a fairly short document	with very little YANG in it; the
document defines a new YANG feature for BDF padding and a padding leaf
to configure padding	of BFD packets.

The definition of the padded-pdu-size type may be a bit	confusing:

         "The padded PDU size for the encapsulated BFD control packets.
          The minimum size is 24 or 26; see Section 6.8.6 of RFC 5880.
          The maximum PDU size may be limited by the supported interface
          MTU of the system.";

I _assume_ a value of this type determines the Length field of the BDF
Control packet. Perhaps define it that way and leave out "for the
encapsulated BFD control packets", which may	be confusing.

	 "The padded PDU size carried in the Length field of a	BDF
	  Control packet. The minimum size is 24 or 26; see Section
          6.8.6 of RFC 5880. The maximum PDU size may be limited by
          the supported interface MTU of the system.";

Is there anything to be	said about the padding data? All zeros, random
bits, implementation specific?

The value of Appendix A	is not clear, perhaps drop it?


-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux