Re: [CCAMP] Review Request For Changes in draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-04.txt
Lou Berger <lberger@labn.net> Wed, 12 September 2012 16:10 UTC
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2BA21F85A4 for <ccamp@ietfa.amsl.com>; Wed, 12 Sep 2012 09:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.084
X-Spam-Level:
X-Spam-Status: No, score=-100.084 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZUMoi08p8bZh for <ccamp@ietfa.amsl.com>; Wed, 12 Sep 2012 09:10:46 -0700 (PDT)
Received: from oproxy8-pub.bluehost.com (oproxy8.bluehost.com [IPv6:2605:dc00:100:2::a8]) by ietfa.amsl.com (Postfix) with SMTP id 32F1B21F859C for <ccamp@ietf.org>; Wed, 12 Sep 2012 09:10:46 -0700 (PDT)
Received: (qmail 14413 invoked by uid 0); 12 Sep 2012 16:10:45 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy8.bluehost.com with SMTP; 12 Sep 2012 16:10:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=FgJq2SgZNUpQd5BZM9itp9NFjhgmw9pVeG+HPHQrzzc=; b=fcQVTHhd6lxAhwr5fYvov5CB3o/DDWt9GcQotuUvKHoru9iXZu13f24PN465z6DlHdmX6Km9kuu64UaFDDpcGAVIEt6jR3swcuK/KjMKkKC+fq3us5k9WAu7rYbN7f9g;
Received: from box313.bluehost.com ([69.89.31.113]:56167 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1TBpWW-0006DV-NK; Wed, 12 Sep 2012 10:10:45 -0600
Message-ID: <5050B401.6070008@labn.net>
Date: Wed, 12 Sep 2012 12:10:41 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>
References: <B7D2A316AA32B6469D9670B6A81B7C24071272@xmb-aln-x07.cisco.com> <5037C010.7010605@labn.net> <B7D2A316AA32B6469D9670B6A81B7C240721E2@xmb-aln-x07.cisco.com> <5037E6C4.5050507@labn.net> <B7D2A316AA32B6469D9670B6A81B7C24072413@xmb-aln-x07.cisco.com> <503A3309.4020907@labn.net> <B7D2A316AA32B6469D9670B6A81B7C240732EF@xmb-aln-x07.cisco.com>
In-Reply-To: <B7D2A316AA32B6469D9670B6A81B7C240732EF@xmb-aln-x07.cisco.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] Review Request For Changes in draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-04.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 16:10:47 -0000
Rakesh, Looks like you switched threads in your last message. (BTW I think I'm getting lost in the number of changes being discussed and think having a new version capturing changes to date would help...) Let me try to merge them: >On 8/27/2012 5:16 PM, Rakesh Gandhi (rgandhi) wrote: >> >> Let me propose revised texts for section 3.2.6 [item 7], 3.2.7 [item 8] and 4.1 [items 1,2,3,6]. >> >> Regards, >> Rakesh >> >> >> -----Original Message----- >> From: Lou Berger [mailto:lberger@labn.net] >> Sent: Sunday, August 26, 2012 10:31 AM >> To: Rakesh Gandhi (rgandhi) >> Cc: ccamp@ietf.org; zhang.fei3@zte.com.cn >> Subject: Re: [CCAMP] Review Request For Changes in draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-04.txt >> >> >> Rakesh, >> See below (using normal reply notation)... >> >> On 8/24/2012 5:18 PM, Rakesh Gandhi (rgandhi) wrote: >>> Hi Lou, >>> >>> Please see inline..<RG2>.. >>> >>> -----Original Message----- >>> From: Lou Berger [mailto:lberger@labn.net] >>> Sent: Friday, August 24, 2012 4:41 PM >>> To: Rakesh Gandhi (rgandhi) >>> Cc: ccamp@ietf.org; zhang.fei3@zte.com.cn >>> Subject: Re: [CCAMP] Review Request For Changes in >>> draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-04.txt >>> >>> Rakesh, >>> >>> See below. >>> >>> On 8/24/2012 2:31 PM, Rakesh Gandhi (rgandhi) wrote: >>>> Hi Lou, >>>> >>>> Thanks for your review. Please see inline..<RG>.. >>>> >>>> -----Original Message----- >>>> From: Lou Berger [mailto:lberger@labn.net] >>>> Sent: Friday, August 24, 2012 1:55 PM >>>> To: Rakesh Gandhi (rgandhi) >>>> Cc: ccamp@ietf.org >>>> Subject: Re: [CCAMP] Review Request For Changes in >>>> draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-04.txt >>>> >>>> Rakesh, >>>> >>>> Speaking as a WG participant, and ignoring changes 4 and 5 as you plan to revert these: >>>> >>>> On 8/23/2012 12:20 PM, Rakesh Gandhi (rgandhi) wrote: >[...] > >>>>> 7. Path Protection object: >>>>> Version 03 of the draft vaguely mentioned and assumed of >>>>> using protection object for path protection. New version 04 >>>>> adds some texts to clarify it, no new rule is added. >>>>> >>>> >>>> I think providing informative text on interactions of this >>>> document with the various defined recovery (4872 and 4872) and >>>> reroute (4090) mechanisms is a really good idea. That said, I >>>> found this section a bit opaque. Ignoring the wordsmithing, what >>>> specific points are you trying to make? >>>> >>>> >>>> <RG> It just highlights that for a bi-directional tunnel, there >>>> can be a working bidirectional LSPs and protecting bidirectional >>>> LSPs. That's all. >>>> >>> >>> I think the proposed text is really confusing and doesn't cover the >>> full scope (in particular 4872 is about recovery which is both >>> protection and restoration, it doesn't cover 4873 or 4090). Can you >>> propose (one the >>> list) some alternate text? >>> >>> <RG2> Idea here is that there are multiple bidirectional LSPs for a >>> tunnel for different LSP roles. We could remove the LSP type as >>> primary and secondary reference from the text, and just state LSPs >>> for different roles. >>> >> >> Again, I think the issue is with the proposed language. On 9/4/2012 12:26 PM, Rakesh Gandhi (rgandhi) wrote: > Thanks Lou. > Potential text for the remained two sections in the draft can be as > follows. Please feel free to revise. > > 3.2.6 Signaling of Associated Bidirectional LSP For Different LSP > Roles > There can also be a pair of recovery and/or reroute LSPs as per > procedures define in [RFC4872], [RFC4873] and [RFC4090]. Together > with those procedures, a node uses Extended ASSOCIATION object or > ASSOCIATION object defined in this document to form an associated > bidirectional LSP pair for each LSP role. I still don't understand this text. Perhaps you mean something like: 3.2.6. Associated Bidirectional LSPs and LSP Recovery LSP recovery as defined in [RFC4872], [RFC4873] and [RFC4090] is not impacted by this document. The recovery mechanisms defined in [RFC4872] and [RFC4873] rely on the use of ASSOCIATION Objects, but use a different Association Type field value than defined in this document so should not be impacted. The mechanisms defined in [RFC4090] does not rely on the use of ASSOCIATION Objects and is therefore also not impacted by the mechanisms defined in this document. >> >> >>>> >>>>> 8. Auto-tunnel mesh: >>>>> New version 04 adds a section to elaborate on a use case for >>>>> auto-tunnel mesh. This is added as an FYI and can be removed if >>>>> WG thinks so. >>>>> >>>> >>>> How is the association id field value selected in this case? >>>> >>>> <RG> Proposal allows that single association-id can be provisioned >>>> for a mesh-group. >>> I don't think you have text that supports this. The closest you >>> come is: >>> A node provisioned to >>> build a mesh of associated bidirectional LSPs may use identical >>> association ID for the given mesh-group member peers. >>> >>> which doesn't say that the "identical association ID" MUST be >>> provisioned. >>> >>> <RG2> Yes, we can clarify this. On 9/4/2012 12:26 PM, Rakesh Gandhi (rgandhi) wrote: > > 3.2.7. Signaling of Auto-tunnel Mesh-group LSPs > A node may build LSPs automatically to remote peers in a mesh using > the mesh-group membership defined in [RFC4972]. A node MUST be > provisioned with identical association ID for the given mesh-group > members peers to build a mesh of associated bidirectional LSPs. The > extended association ID can be used to form unique Extended > ASSOCIAITON object in each LSP to different remote peers. How about something along the lines of: 3.2.7. Associated Bidirectional LSPs and TE Mesh-Groups TE mesh-groups is defined in [RFC4972]. A node supporting both Associated Bidirectional LSPs and TE mesh-groups, MAY include an ASSOCIATION object as defined in this document in Path messages of LSPs used to support the mesh-group. To enable unambiguous identification of the mesh-group's associated bidirectional LSPs, the information carried in the ASSOCIATION object, including the contents of the Association Source and Identifier fields MUST be provisioned. Lou (as WG participant) >>> >> >> Great! >> >> Lou >> >>> Thanks, >>> Rakesh >>> >>> Lou >
- [CCAMP] Review Request For Changes in draft-ietf-… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… John E Drake
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… zhang.fei3
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… zhang.fei3
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… zhang.fei3
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… zhang.fei3
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… zhang.fei3
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)
- Re: [CCAMP] Review Request For Changes in draft-i… Lou Berger
- Re: [CCAMP] Review Request For Changes in draft-i… Rakesh Gandhi (rgandhi)