[Isis-wg] [Errata Verified] RFC6822 (4520)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 11 November 2015 16:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9002F1B2B9F; Wed, 11 Nov 2015 08:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.312
X-Spam-Level:
X-Spam-Status: No, score=-106.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EuxoSgqpo3j; Wed, 11 Nov 2015 08:40:36 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id F0B531B2A78; Wed, 11 Nov 2015 08:40:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 637E0180092; Wed, 11 Nov 2015 08:39:14 -0800 (PST)
To: alexander.okonnikov@gmail.com, sprevidi@cisco.com, ginsberg@cisco.com, imc.shand@gmail.com, akr@cisco.com, wardd@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20151111163914.637E0180092@rfc-editor.org>
Date: Wed, 11 Nov 2015 08:39:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/ywsITrF2VzqBsw-fKLyIt2fAWJ0>
Cc: rfc-editor@rfc-editor.org, akatlas@juniper.net, iesg@ietf.org, isis-wg@ietf.org
Subject: [Isis-wg] [Errata Verified] RFC6822 (4520)
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 16:40:37 -0000
The following errata report has been verified for RFC6822, "IS-IS Multi-Instance". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6822&eid=4520 -------------------------------------- Status: Verified Type: Technical Reported by: Alexander Okonnikov <alexander.okonnikov@gmail.com> Date Reported: 2015-11-02 Verified by: Alia Atlas (IESG) Section: 2.6.1 Original Text ------------- An MI-RTR will use the AllL1IS or AllL2IS ISIS MAC-layer address (as defined in [ISO10589]) as the destination address when sending an IS-IS PDU for the standard instance. An MI-RTR will use one of two new dedicated layer 2 multicast addresses (AllL1MI-ISs or AllL2MI- ISs) as the destination address when sending an IS-IS PDU for any non-zero IID. These addresses are specified in Section 6. If operating in point-to-point mode on a broadcast circuit [RFC5309], an MI-RTR MUST use one of the two new multicast addresses as the destination address when sending point-to-point IIHs associated with a non-zero instance. (Either address will do.) MI-RTRs MUST discard IS-IS PDUs received if either of the following is true: o The destination multicast address is AllL1IS or AllL2IS and the PDU contains an IID-TLV. o The destination multicast address is one of the two new addresses, and the PDU contains an IID-TLV with a zero value for the IID or has no IID-TLV. NOTE: If the multicast addresses AllL1IS and/or AllL2IS are improperly used to send IS-IS PDUs for non-zero IIDs, legacy systems will interpret these PDUs as being associated with IID #0. This will cause inconsistencies in the LSDB in those routers, may incorrectly maintain adjacencies, and may lead to inconsistent DIS election. Corrected Text -------------- An MI-RTR will use the AllL1ISs or AllL2ISs ISIS MAC-layer address (as defined in [ISO10589]) as the destination address when sending an IS-IS PDU for the standard instance. An MI-RTR will use one of two new dedicated layer 2 multicast addresses (AllL1MI-ISs or AllL2MI-ISs) as the destination address when sending an IS-IS PDU for any non-zero IID. These addresses are specified in Section 6. If operating in point-to-point mode on a broadcast circuit [RFC5309], an MI-RTR will use the AllL1ISs, AllL2ISs or AllISs MAC-layer address (as defined in [ISO10589]) as the destination address when sending an IS-IS PDU for the standard instance, and will use one of two new multicast addresses (AllL1MI-ISs or AllL2MI-ISs; either address will do) as the destination address when sending an IS-IS PDU for any non-zero IID. MI-RTRs MUST discard IS-IS PDUs received if either of the following is true: o The destination multicast address is AllL1ISs, AllL2ISs or AllISs and the PDU contains an IID-TLV. o The destination multicast address is one of the two new addresses and the PDU contains an IID-TLV with a zero value for the IID or has no IID-TLV. NOTE: If the multicast addresses AllL1ISs and/or AllL2ISs and/or AllISs are improperly used to send IS-IS PDUs for non-zero IIDs, legacy systems will interpret these PDUs as being associated with IID #0. This will cause inconsistencies in the LSDB in those routers, may incorrectly maintain adjacencies, and may lead to inconsistent DIS election. Notes ----- 1. While operating in point-to-point mode over broadcast circuit, MI-RTR can use any of three multicast addresses for PDUs in standard instance - AllL1ISs, AllL2ISs or AllISs. 2. New multicast addresses must be used for all kinds of IS-IS PDUs, not only for IIHs 3. AllL1IS and AllL2IS are replaced by AllL1ISs and AllL2ISs, respectively (according to ISO 10589:2002). -------------------------------------- RFC6822 (draft-ietf-isis-mi-08) -------------------------------------- Title : IS-IS Multi-Instance Publication Date : December 2012 Author(s) : S. Previdi, Ed., L. Ginsberg, M. Shand, A. Roy, D. Ward Category : PROPOSED STANDARD Source : IS-IS for IP Internets Area : Routing Stream : IETF Verifying Party : IESG
- [Isis-wg] [Technical Errata Reported] RFC6822 (45… RFC Errata System
- Re: [Isis-wg] [Technical Errata Reported] RFC6822… Les Ginsberg (ginsberg)
- [Isis-wg] [Errata Verified] RFC6822 (4520) RFC Errata System