Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)

mike shand <mshand@cisco.com> Thu, 22 April 2010 10:00 UTC

Return-Path: <mshand@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 0B81B28C0CE for <isis-wg@core3.amsl.com>; Thu, 22 Apr 2010 03:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 d68ArP8pP604 for <isis-wg@core3.amsl.com>; Thu, 22 Apr 2010 03:00:13 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 5F3C43A689D for <isis-wg@ietf.org>; Thu, 22 Apr 2010 03:00:13 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvgBAHe7z0uQ/uCWiWdsb2JhbACcIhUBAQEKCxERBhyjNZpWhQ8E
X-IronPort-AV: E=Sophos;i="4.52,255,1270425600"; d="scan'208";a="59859755"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 22 Apr 2010 10:00:02 +0000
Received: from [10.61.107.214] (dhcp-10-61-107-214.cisco.com [10.61.107.214]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o3MA01rb002422 for <isis-wg@ietf.org>; Thu, 22 Apr 2010 10:00:02 GMT
Message-ID: <4BD01E21.6090200@cisco.com>
Date: Thu, 22 Apr 2010 11:00:01 +0100
From: mike shand <mshand@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: isis-wg@ietf.org
References: <OF706EDF7F.8687ECCF-ON4825770D.001074B3-4825770D.001074CB@china.mobile><C7F532C3.D1D2%tony.li@tony.li> <AE36820147909644AD2A7CA014B1FB520A9E2E79@xmb-sjc-222.amer.cisco.com> <AE36820147909644AD2A7CA014B1FB520A9E2E80@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520A9E2E80@xmb-sjc-222.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)
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: Thu, 22 Apr 2010 10:00:15 -0000

On 22/04/2010 07:41, Les Ginsberg (ginsberg) wrote:
> A couple of other comments that come to mind:
>
> We need to define what an implementation SHOULD do when it receives a
> purged LSP with the additional TLVs i.e. store it (including the body)
> and flood it unchanged.
>    
Yes. I think that is what would be expected from the existing spec, but 
it does no harm to clarify it. I wonder if any existing implementations 
would take it upon themselves to remove the body from a purge? I hope not.
> If the same purged LSP is received from two different originators, the
> choice of which "copy" to flood is a local matter.
>    

Hmmm. Would it not be the case that the first one received was always 
the one flooded, since any later ones received would be regarded as 
duplicates?
>     Les
>
>    
>> -----Original Message-----
>> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On
>> Behalf Of Les Ginsberg (ginsberg)
>> Sent: Wednesday, April 21, 2010 11:25 PM
>> To: Tony Li; lizhenqiang@chinamobile.com; Jie Dong;
>> bruno.decraene@orange-ftgroup.co; isis-wg@ietf.org;
>> weifang@chinamobile.com
>> Subject: Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)
>>
>>
>>
>>      
>>> -----Original Message-----
>>> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On
>>> Behalf Of Tony Li
>>> Sent: Wednesday, April 21, 2010 10:55 PM
>>> To: lizhenqiang@chinamobile.com; Jie Dong; bruno.decraene@orange-
>>> ftgroup.co; isis-wg@ietf.org; weifang@chinamobile.com
>>> Subject: Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)
>>>
>>>
>>>
>>>
>>>        
>>>> I renamed the draft as draft-ietf-isis-purge-tlv-00.txt and
>>>>          
>> submitted
>>      
>>>> it to IETF. Its status is Initial Version Approval Requested.
>>>>          
>>>
>>> As long as that's stuck in the queue, there's not much point in
>>> submitting a
>>> -01 verison.  So here's the document as an attachment.
>>>        
>> But hopefully we can comment on 01 anyway?? :-)
>>
>> ****************
>>
>> I don't see the need for Section 3. It was interesting discussion
>> material while we were debating the merits of making this a WG
>> document,
>> but I think it has drawbacks when it is included in what is intended
>>      
> to
>    
>> become a standards document.
>>
>> The first three points suggest (no doubt unintentionally) that this
>> document may in some way be redefining/clarifying the base spec in
>> regards to when it is permissible to purge. I don't think we want to
>> even remotely suggest that. If you want to know when it is OK to
>>      
> purge,
>    
>> look at the base spec.
>>
>> In the second set of three points, only the first (which documents the
>> lamentable purge on checksum error experience) has value. The last two
>> are anecdotal and could be translated as "there are some weird bugs
>>      
> out
>    
>> there". Interesting - but unnecessary. The first point could be
>> mentioned in the introduction as part of the justification for the
>> protocol extensions - but I think even that is unnecessary.
>>
>> ********************
>> In Section 5 I would like to see language which says "hostname TLV
>> SHOULD only be used in addition to the system ID TLV". As every IS
>>      
> MUST
>    
>> have a unique systemID but hostnames are optional I would prefer that
>> if
>> an implementation chooses to include the extra info in the purge that
>> the system ID ALWAYS be there. (This is unenforceable of course)
>>
>> *******************
>>
>> I think there needs to be language which makes clear that the absence
>> or
>> presence of this additional information has no impact on the
>>      
> acceptance
>    
>> of a purged LSP as valid i.e. no changes to the operation of the
>>      
> Update
>    
>> process are introduced by this draft.
>>
>> Thanx.
>>
>>     Les
>>
>>
>>      
>>> Tony
>>>        
>> _______________________________________________
>> Isis-wg mailing list
>> Isis-wg@ietf.org
>> https://www.ietf.org/mailman/listinfo/isis-wg
>>      
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>
>    

-- 
For corporate legal information go to:
www.cisco.com/web/about/doing_business/legal/cri