Mirja Kühlewind has entered the following ballot position for draft-ietf-softwire-yang-14: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-softwire-yang/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Some minor comments: 1) Sec 4.2: "softwire-path-mru: optionally used to set the maximum IPv6 softwire packet size that can be received, including the encapsulation/translation overhead. Needed if the softwire implementation is unable to correctly calculate the correct IPv4 Maximum Receive Unit (MRU) size automatically [RFC4213]." I guess this should both be IPv6...? 2) Why does the description of "rcvd-ipv4-bytes" say "IPv4 traffic received for processing, in bytes"..? Does the "for processing" have any special meaning or why is it only phrased like this for that one entry? 3) Also the description for "sent-ipv4-bytes" and "sent-ipv4-packets" could be unified. _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
