Re: [OSPF] status of draft-ietf-ospf-rfc3137bis

Acee Lindem <acee.lindem@ericsson.com> Thu, 15 March 2012 14:44 UTC

Return-Path: <acee.lindem@ericsson.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2524B21F86F7 for <ospf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.912
X-Spam-Level:
X-Spam-Status: No, score=-5.912 tagged_above=-999 required=5 tests=[AWL=-0.513, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, J_CHICKENPOX_92=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aWdKI+CjVMfj for <ospf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:44:52 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7B6E421F8455 for <ospf@ietf.org>; Thu, 15 Mar 2012 07:44:52 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q2FEhw7s016784; Thu, 15 Mar 2012 09:44:51 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.229]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Thu, 15 Mar 2012 10:44:49 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Shishio Tsuchiya <shtsuchi@cisco.com>
Date: Thu, 15 Mar 2012 10:44:48 -0400
Thread-Topic: [OSPF] status of draft-ietf-ospf-rfc3137bis
Thread-Index: Ac0Cuix/TJdYeYEUQduPVL5e+Xaxtg==
Message-ID: <20C678C1-E925-408B-B67B-22DC399AB8E1@ericsson.com>
References: <4F471A4C.1020107@cisco.com> <233E5A64-2E97-4F22-9D92-6C072952EE20@ericsson.com> <4F4C7F16.3040004@cisco.com> <DA1B868A-3ECC-4997-A447-F05877C8F9BB@ericsson.com> <4F615BD0.4010601@cisco.com>
In-Reply-To: <4F615BD0.4010601@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-6--819313561"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-rfc3137bis@tools.ietf.org" <draft-ietf-ospf-rfc3137bis@tools.ietf.org>
Subject: Re: [OSPF] status of draft-ietf-ospf-rfc3137bis
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 14:44:53 -0000

Hi Shishio,

I just looked at the expired draft and it doesn't include any discussion of the R-bit. 

http://tools.ietf.org/id/draft-ietf-ospf-rfc3137bis-00.txt

Can you put that in the next revision? 

Thanks,
Acee

On Mar 14, 2012, at 11:02 PM, Shishio Tsuchiya wrote:

> Acee
> Thank you for reply.
> 2012/03/15 6:28), Acee Lindem wrote:
>> [Speaking as a WG member]
>> 
>> Hi Shishio,
>> 
>> I guess I didn't read this close enough the first time.
>> 
>> On Feb 28, 2012, at 2:15 AM, Shishio Tsuchiya wrote:
>> 
>>> Acee
>>> Thank you for information.
>>> But a lot of vendors already supported the high link metric to announce as stub.
>>> Therefore I think the draft should describe both of high link metric and R-bit.
>>> What do you think if the author add only one or two sentence which mentioned exist of R-bit to current internet draft?
>> 
>> Due to its simplicity, I think the R-bit should be the preferred option. 
>> Since all OSPFv3 implementations should support the R-bit, there are no compatibility issues. Does everyone agree?
> 
> Yes,I strong agree that OSPFv3 should support the R-bit.
> It's described on rfc5340.
> My draft described two mode R-bit and high link metric.
> http://tools.ietf.org/html/draft-shishio-ospf-ospfv3-stub
> 
> I thought Alvaro's the draft should describe only high link metric.
> http://www.ietf.org/proceedings/80/slides/ospf-2.pdf
> 
>> 
>> The only value I can see in using the high-link metric is that it allows the existing implementations you cite to say they conform this draft.  
>> Is that worth having two mechanisms?
> 
> I could not find any difference essentially in 2 modes when I wrote the draft and discuss about this topic.
> But merit of high-link metric are
> -easy to implementation : most of vendor already supported this mode.
> -same operation OSPFv2 and OSPFv3: the operator needs to check metric value.(do not need to know new bit)
> 
> I agree R-bit should be preferred option, but I think the draft should describe high-link metric also.
> 
> Regards,
> -Shishio
> 
>> 
>> Thanks,
>> Acee
>> 
>> 
>>> 
>>> Regards,
>>> -Shishio
>>> 
>>> (2012/02/28 7:23), Acee Lindem wrote:
>>>> Hi Shishio,
>>>> If I remember correctly, there was discussion as to whether to just use the R-bit rather than the high link metric for OSPFv3. Given the goals of the draft, I'd be in favor of this change.
>>>> Thanks,
>>>> Acee
>>>> On Feb 24, 2012, at 12:04 AM, Shishio Tsuchiya wrote:
>>>> 
>>>>> Hi
>>>>> After this draft be WG documents,it expired.
>>>>> https://datatracker.ietf.org/doc/draft-ietf-ospf-rfc3137bis/
>>>>> 
>>>>> Was there any objection? or just maintenance issue?
>>>>> 
>>>>> Regards,
>>>>> -Shishio
>>>>> _______________________________________________
>>>>> OSPF mailing list
>>>>> OSPF@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ospf
>>>> 
>>> 
>>> 
>> 
> 
>