Eric Rescorla has entered the following ballot position for draft-ietf-trill-centralized-replication-12: 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-trill-centralized-replication/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- if a triple of {ingress nickname, tree, receiving RBridge port} is allowed. (The tree is indicted by the nickname of its root which is stored in the TRILL Header "egress nickname" field.) When I think this probably should be "indicated" 7. Centralized replication forwarding process This diagram would be helpful earlier * ----------*-------------*-- ^ ***************************** | ^ LAALP1 * LAALP2 | ^ What are the asterisks? equals (m mod k) as egress nickname for BUM traffic unicast TRILL encapsulation. This text might be easier to read as: "For data label ID m, choose R-nickname = m mod k" The "equals" isn't that helpful here, but if you wanted to say it that way, you might try "choose the R-nickname n which is equal to m (mod k)" o C = If C flag is one, it indicates that the TRILL traffic with this nickname as an ingress nickname that requires the special Nit: I would use ":" here instead of equals _______________________________________________ trill mailing list [email protected] https://www.ietf.org/mailman/listinfo/trill
