Suresh Krishnan has entered the following ballot position for draft-ietf-softwire-multicast-prefix-option-12: Discuss
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-multicast-prefix-option/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- * Section 3: How can the ASM_mPrefix64 and SSM_mPrefix64 be (variable) as described in the packet format when the asm-length and the ssm-length MUST be set to 96? Not sure which of these is correct and which is wrong but one of these things (either the fixed length or the variable prefix) needs to be fixed. * Section 4: This section contains a bunch of must and may level requirements but contains the following "disclaimer" text. "This section is not normative but specifies a set of configuration guidelines." Not sure what the intent behind this is. Can you clarify? _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
