[OSPF] Re: draft-acee-ospf-multi-instance-00
Acee Lindem <acee@redback.com> Thu, 24 January 2008 18:56 UTC
Return-path: <ospf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI7FC-00035H-KA; Thu, 24 Jan 2008 13:56:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI7FB-00035B-KI for ospf@ietf.org; Thu, 24 Jan 2008 13:56:09 -0500
Received: from prattle.redback.com ([155.53.12.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI7F9-0005t1-Kx for ospf@ietf.org; Thu, 24 Jan 2008 13:56:09 -0500
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id DFC8ADA1E5B; Thu, 24 Jan 2008 10:56:06 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13845-02; Thu, 24 Jan 2008 10:56:06 -0800 (PST)
Received: from [?|??/??IPv6???1] (login004.redback.com [155.53.12.57]) by prattle.redback.com (Postfix) with ESMTP id 34037DA1E58; Thu, 24 Jan 2008 10:56:06 -0800 (PST)
In-Reply-To: <77ead0ec0801240949y123f577au9dc36b99694a506@mail.gmail.com>
References: <77ead0ec0801240949y123f577au9dc36b99694a506@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <FA8A6B7C-F299-4FFF-A633-E716626B7B45@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Thu, 24 Jan 2008 13:56:01 -0500
To: Vishwas Manral <vishwas.ietf@gmail.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae
Cc: OSPF List <ospf@ietf.org>
Subject: [OSPF] Re: draft-acee-ospf-multi-instance-00
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0037160655=="
Errors-To: ospf-bounces@ietf.org
Hi Vishwas, From a protocol standpoint, it is completely backward compatible. OSPF routers not supporting the draft but receiving a multicast OSPF packet with a non-zero instance ID will simply treat it as an unknown AuType and fail authentication. With this respect, RFC 2328 simply states: 8.2. Receiving protocol packets o o o o The packet must be authenticated. The authentication procedure is indicated by the setting of AuType (see Appendix D). The authentication procedure may use one or more Authentication keys, which can be configured on a per- interface basis. The authentication procedure may also verify the checksum field in the OSPF packet header (which, when used, is set to the standard IP 16-bit one's complement checksum of the OSPF packet's contents after excluding the 64-bit authentication field). If the authentication procedure fails, the packet should be discarded. And: D.5 Message verification When an OSPF packet has been received on an interface, it must be authenticated. The authentication procedure is indicated by the setting of Autype in the standard OSPF packet header, which matches the setting of Autype for the receiving OSPF interface. If an OSPF protocol packet is accepted as authentic, processing of the packet continues as specified in Section 8.2. Packets which fail authentication are discarded. Speaking as a draft author (not OSPF WG Co-chair): Unfortunately, some well-deployed implementations make a bigger fuss than is necessary when an authentication failure occurs. IMHO, now would be a good time to rectify this to lesses the impact should this draft be accepted as a standards track document. Of course, there are manual ways of segregating the multi-access networks to avoid down- level routers from receiving multicast packets for non-zero instances. Perhaps, we should discuss these in the draft and dispense with the more radical discussions of requesting new multicast addresses or other IANA code points. Thanks, Acee On Jan 24, 2008, at 12:49 PM, Vishwas Manral wrote: > Hi Acee, > > I wanted to know if this draft was backward compatible with current > implementation. If its not, I was also eager to know, if we have a way > for incremental deployment. > > Thanks, > Vishwas
_______________________________________________ OSPF mailing list OSPF@ietf.org https://www1.ietf.org/mailman/listinfo/ospf
- [OSPF] draft-acee-ospf-multi-instance-00 Vishwas Manral
- [OSPF] Re: draft-acee-ospf-multi-instance-00 Acee Lindem
- [OSPF] Re: draft-acee-ospf-multi-instance-00 Vishwas Manral
- [OSPF] Re: draft-acee-ospf-multi-instance-00 Acee Lindem
- [OSPF] Re: draft-acee-ospf-multi-instance-00 Vishwas Manral
- RE: [OSPF] Re: draft-acee-ospf-multi-instance-00 Sina Mirtorabi
- [OSPF] Re: draft-acee-ospf-multi-instance-00 Acee Lindem