The following errata report has been submitted for RFC8678, "Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8124 -------------------------------------- Type: Technical Reported by: Scott Shambarger <scott-...@shambarger.net> Section: 6.3.2 Original Text ------------- Let's consider a scenario in which all uplinks are operational, and H41 receives two different RAs from R3: one from LLA_A with a PIO for 2001:db8:0:a020::/64 and the default router preference set to 11 (low), and another one from LLA_B with a PIO for 2001:db8:0:a020::/64, the default router preference set to 01 (high), and a RIO for 2001:db8:0:6666::/64. As a result, H41 uses Corrected Text -------------- Let's consider a scenario in which all uplinks are operational, and H41 receives two different RAs from R3: one from LLA_A with a PIO for 2001:db8:0:a020::/64 and the default router preference set to 11 (low), and another one from LLA_B with a PIO for 2001:db8:0:b020::/64, the default router preference set to 01 (high), and a RIO for 2001:db8:0:6666::/64. As a result, H41 uses Notes ----- Minor technical fix to paragraph 2, 1st sentence: PIO of 2001:db8:0:a020::/64 is used for both LLA_A and LLA_B. Based on the remaining contents of the paragraph, the PIO of LLA_B should be 2001:db8:0:b020::/64. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC8678 (draft-ietf-rtgwg-enterprise-pa-multihoming-12) -------------------------------------- Title : Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions Publication Date : December 2019 Author(s) : F. Baker, C. Bowers, J. Linkova Category : INFORMATIONAL Source : Routing Area Working Group Stream : IETF Verifying Party : IESG _______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
