Re: [Isis-wg] [Technical Errata Reported] RFC5310 (2462)

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Fri, 13 August 2010 23:50 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E9523A67C0 for <isis-wg@core3.amsl.com>; Fri, 13 Aug 2010 16:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level:
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6LuUvNfdOWw for <isis-wg@core3.amsl.com>; Fri, 13 Aug 2010 16:50:41 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 473BA3A67B3 for <isis-wg@ietf.org>; Fri, 13 Aug 2010 16:50:41 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.55,366,1278288000"; d="scan'208";a="171852070"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 13 Aug 2010 23:51:18 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o7DNpITo006416; Fri, 13 Aug 2010 23:51:18 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Aug 2010 16:51:18 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 Aug 2010 16:51:18 -0700
Message-ID: <AE36820147909644AD2A7CA014B1FB520BA23099@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <58011C09-93A3-4DC6-82B6-B00A791759C8@tony.li>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Isis-wg] [Technical Errata Reported] RFC5310 (2462)
Thread-Index: Acs7Nk8pNhdvz+gxRbWamNjhqPWyeQACuThQ
References: <20100812185517.34298E06D7@rfc-editor.org><7C362EEF9C7896468B36C9B79200D8350CD03DB216@INBANSXCHMBSA1.in.alcatel-lucent.com> <DBCA1447-F194-41A5-9CAF-67AF4644D5E5@tony.li> <AE36820147909644AD2A7CA014B1FB520BA22E92@xmb-sjc-222.amer.cisco.com> <58011C09-93A3-4DC6-82B6-B00A791759C8@tony.li>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Tony Li <tony.li@tony.li>
X-OriginalArrivalTime: 13 Aug 2010 23:51:18.0393 (UTC) FILETIME=[6C78D690:01CB3B42]
Cc: Chris Hopps <chopps@rawdofmt.org>, isis-wg@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>, mfanto@aegisdatasecurity.com, adrian.farrel@huawei.com, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, riw@cisco.com, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Isis-wg] [Technical Errata Reported] RFC5310 (2462)
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 13 Aug 2010 23:50:42 -0000

Tony -

> -----Original Message-----
> From: Tony Li [mailto:tony.li@tony.li]
> Sent: Friday, August 13, 2010 3:23 PM
> To: Les Ginsberg (ginsberg)
> Cc: Bhatia, Manav (Manav); Chris Hopps; isis-wg@ietf.org list; Ran
> Atkinson; mfanto@aegisdatasecurity.com; RFC Errata System;
> adrian.farrel@huawei.com Farrel; riw@cisco.com White
> Subject: Re: [Isis-wg] [Technical Errata Reported] RFC5310 (2462)
> 
> 
> Les,
> 
> > In the context of the discussion regarding
> > draft-ietf-isis-purge-tlv-03.txt, what is the point of
> > clarifying/correcting RFC5310 in this way given that we now need to
> > update this behavior to allow TLVs other than the authentication TLV
> in
> > purged LSPs?
> 
> 
> Do you have a better way?  There needs to be some text in 5310 for how
> to handle purges.  We don't want to add text that is a forward
> reference to every explicit TLV that can appear in purges in the
> future.  The text that I'm proposing simply puts 5310 on the same
> footing as 5304, which we have to address anyways.

I am thinking of this from what I think is a practical point of view.
RFC5304 updates RFC3567 - which is several years old. I would have
expected that folks who implemented RFC5310 would have used the same
purge strategy that was specified in 5304/3567 - despite the fact that
5310 (quite unintentionally I assume) did not include the necessary
explicit language. If they did, then they are already doing what the
errata is intended to clarify.

If they have not followed the RFC5304 procedures in regards to purge,
then telling them they need to introduce RFC5304 behavior seems
pointless if we intend to "immediately" follow this up by telling them
that the RFC5304 behavior needs to be updated to allow for TLVs other
than the authentication TLV in purge LSPs.

??

> 
> 
> > I would also point out that draft-ietf-isis-mi-03.txt also
stipulates
> > that the instance TLV MUST be retained in purged LSPs (see the last
> > paragraph of Section 2.1) - so we now have two cases that require
> TLVs
> > other than the authentication TLV to be included in purge LSPs.
> 
> 
> Excellent, thanks for pointing that out.
> 
> This suggests that we need a more generic mechanism.  It seems to me
> that the correct approach here is to create or extend an IANA registry
> of TLVs that can be found in purges.  This could become another column
> in the "TLV Codepoint Registry" or another independent registry.
> 

An additional column in the existing registry seems like an excellent
idea to me.

   Les

> RFC's that are then discussing purges could reference this registry.
> 
> Thoughts?
> 
> Tony