Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis-01.txt
Acee Lindem <acee.lindem@ericsson.com> Mon, 02 July 2012 15:29 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 68DEB21F86CB for <ospf@ietfa.amsl.com>; Mon, 2 Jul 2012 08:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level:
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, 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 dplxUMpeXAPX for <ospf@ietfa.amsl.com>; Mon, 2 Jul 2012 08:29:30 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id BD7A221F861C for <ospf@ietf.org>; Mon, 2 Jul 2012 08:29:30 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q62FTWic017771; Mon, 2 Jul 2012 10:29:35 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.236]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Mon, 2 Jul 2012 11:29:32 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>
Date: Mon, 02 Jul 2012 11:29:21 -0400
Thread-Topic: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis-01.txt
Thread-Index: Ac1YZ3o4/di48ousSnyLOVTcmmF2rw==
Message-ID: <CC0FB959-2878-4708-9236-6AB9C3EB0238@ericsson.com>
References: <20120629154505.32213.79435.idtracker@ietfa.amsl.com> <4FEE8683.1010706@cisco.com> <C03AAF38AD209F4BB02BC0A34B774CE707E8EC@G1W3777.americas.hpqcorp.net> <AE5A393F-251A-427B-ACE6-60CEF33ADFA0@ericsson.com> <C03AAF38AD209F4BB02BC0A34B774CE7081B52@G1W3777.americas.hpqcorp.net>
In-Reply-To: <C03AAF38AD209F4BB02BC0A34B774CE7081B52@G1W3777.americas.hpqcorp.net>
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-11025589"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis-01.txt
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: Mon, 02 Jul 2012 15:29:31 -0000
Alvaro, On Jul 2, 2012, at 11:05 AM, Retana, Alvaro wrote: > Acee: > >> -----Original Message----- >> From: Acee Lindem [mailto:acee.lindem@ericsson.com] >> Sent: Monday, July 02, 2012 9:56 AM > ... >>>> -move R-bit to solution from Deployment Considerations >>>> ex.) >>>> 3. Proposed Solution >>>> 3-1.maximum metric >>>> 3-2.R-bit >>>> >>>> What do you think of my recommendation? >>> >>> 3173 is about documenting the MaxLinkMetric approach, which is why we >> chose to reference the R-bit as other solutions. 3137 is not about >> comparing or describing the full functionality of the different >> approaches. >> >> The main we respin RFCs is to incorporate changes and there is no >> reason not to document the R-bit mechanism to accomplish the OSPFv3 >> stub router function. > > Besides from the reference (see below), what else do you think we should include? > > The point I'm trying to make is: rfc5340 already defines and documents the R-bit functionality (and it is the standard!). IMHO, there is no need to rehash here what is already defined and explained somewhere else...which is why I think the reference is enough. I don't think you have to describe the mechanism. However, I agree R-bit should be on equal ground as the max-metric links. Also, it would be good to point out the difference in behavior. With max-metric links, transit traffic is discouraged while with the R-bit, transit traffic is completely suppressed. Thanks, Acee > > Thanks! > > Alvaro. > > > 4.1. Other Solutions > > This document describes a technique that has been implemented and > deployed in a wide variety of networks. OSPFv3 [RFC5340] introduced > additional options to provide similar, if not better, control of the > forwarding topology; the R-bit and the V6-bit provide a more granular > indication of whether a router is active and/or whether it should be > used specifically for IPv6 traffic, respectively. > > It is left to network operators to decide which technique to use in > their network. > >
- [OSPF] Fwd: I-D Action: draft-ietf-ospf-rfc3137bi… Shishio Tsuchiya
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Retana, Alvaro
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Acee Lindem
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Retana, Alvaro
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Acee Lindem
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Retana, Alvaro
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Retana, Alvaro
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Acee Lindem
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Retana, Alvaro
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Acee Lindem
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Shishio Tsuchiya
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Acee Lindem
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Shishio Tsuchiya
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Retana, Alvaro
- Re: [OSPF] I-D Action: draft-ietf-ospf-rfc3137bis… Shishio Tsuchiya