Re: [mpls] Question raised in the MPLS-RT review of draft-rosen-mpls-rfc3107bis

"Acee Lindem (acee)" <acee@cisco.com> Thu, 18 August 2016 19:49 UTC

Return-Path: <acee@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19DB912B04F; Thu, 18 Aug 2016 12:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.768
X-Spam-Level:
X-Spam-Status: No, score=-15.768 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0fZ89CgI4DQ; Thu, 18 Aug 2016 12:49:05 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B89F712B069; Thu, 18 Aug 2016 12:49:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4320; q=dns/txt; s=iport; t=1471549745; x=1472759345; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=jAx/G4XUPSSrUl7CZxlGefsaSm5l+mqg6R2kZYGE6lA=; b=Iv5jdKRzUbykRgglyr41ccaVl0Lk86If/4JhmfacYW8SToaOvD4To1cv fiurMZr6D7KQUq4RLw0etOiOg6PJQaDxET2zmu/5YFKKhKq8LGtd7RDzK gDM35HiOusYC+QDpPS/1+BViEPKzV3Hug01GMXXxB1hAlCecbTPJCsfcg I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BeAgDEELZX/4UNJK1dg0NWfAe3Y4F9JIV5AhyBVTgUAgEBAQEBAQFeJ4RfAQUBASERNwMEBw4CAgEIGAICJgICAhkMCxUQAgQBDQWIMQ6tI5AaAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwUFfIl2hBIRATOCaoJaBYYPkzUBjBeDBoFrhFyJAow7g3cBHjaDem6Fdzd/AQEB
X-IronPort-AV: E=Sophos;i="5.28,541,1464652800"; d="scan'208";a="311902897"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Aug 2016 19:49:03 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u7IJn37w017446 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 18 Aug 2016 19:49:03 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 18 Aug 2016 15:49:02 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Thu, 18 Aug 2016 15:49:02 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Loa Andersson <loa@pi.nu>, Eric C Rosen <erosen@juniper.net>, Mach Chen <mach.chen@huawei.com>, "draft-rosen-mpls-rfc3107bis.all@ietf.org" <draft-rosen-mpls-rfc3107bis.all@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: [mpls] Question raised in the MPLS-RT review of draft-rosen-mpls-rfc3107bis
Thread-Index: AQHR+YmR0S/RSyfjp0yPMnkA4TqQ4Q==
Date: Thu, 18 Aug 2016 19:49:02 +0000
Message-ID: <D3DB8804.7A503%acee@cisco.com>
References: <041801d1ecdb$317d1910$94774b30$@olddog.co.uk> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28E782AA6@SZXEMA510-MBX.china.huawei.com> <5d7fcd92-f663-50fc-4057-9827746886ca@juniper.net> <6d39a0bf-df2d-8a33-3194-f693760683d8@pi.nu>
In-Reply-To: <6d39a0bf-df2d-8a33-3194-f693760683d8@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <89DD1181A6DA1A4289D0D4500128C2D7@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/7_KLJQguWCn6aQ0AXa9n2BldKPk>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, BESS <bess@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Subject: Re: [mpls] Question raised in the MPLS-RT review of draft-rosen-mpls-rfc3107bis
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 19:49:07 -0000

Hi Loa, et al, 

Since I commented on the MPLS-RT review with respect to the IDR-specific
content, there may be some confusion as to where I stand on the ownership
of this draft. I’ve reviewed this document and agree with the approach
described below. I’m convinced we will get the right level cross-WG review
along as we recognize that it does span multiple WGs. I would expect that
we’ll have implementations conforming to the draft in the near future.

Thanks,
Acee

On 8/17/16, 1:36 PM, "mpls on behalf of Loa Andersson"
<mpls-bounces@ietf.org on behalf of loa@pi.nu> wrote:

>Eric, et.al., (copied also idr-chairs and idr-list + bess-chairs and
>bess-list)
>
>For those of you that are not subscribed to the mpls-list.
>
>- the mpls wg has started the initial steps for working group adoption,
>   there are three steps
>   -- mpls-rt review (what you see below is the follow-up discussion on
>      that review)
>   -- IPR poll, will be sent out soon
>   -- working group adoption poll (wgap), that poll will be copied to
>      the idr and bess. Hopefully we can that shortly.
>
>I'm sending this to mpls, idr and bess working group, since it has
>to do where things should be documented.
>
>
>On 2016-08-17 17:59, Eric C Rosen wrote:
>> Hi Mach,
>>
>> Thanks for your review.
>>
>> On 8/3/2016 4:51 AM, Mach Chen wrote:
>>> I have only one comment regarding to Section 5. IMHO, although it's
>>> informational, the description about the relationship between SAFI-1
>>> and SAFI-4 routes should not belong to this document, it's a more
>>> common description that is not specific to this label binding process.
>>> I'd suggest to remove this section if there is no any other reasons.
>>
>> Differing interpretations about the relationship between SAFI-1 and
>> SAFI-4 are a very common source of interoperability problems among
>> implementations of different vendors.  Thus I think it is very useful to
>> document this issue and to call attention to some of the differing
>> interpretations.  I think this document is an appropriate place for this
>> information; even though this information is not about label binding, it
>> is about the semantics of SAFI-4.
>
>I agree that this needs to be documented! I can accept that it is done
>in draft-rosen-mpls-rfc3107bis, but I would like to have all three wg's
>agree to this. I see a few alternatives
>
>- we could document this is in draft-rosen-mpls-rfc3107bis; or
>- we could write a separate document
>- we could find another document where this has a better fit than in
>   draft-rosen-mpls-rfc3107bis
>- any other suggestion
>
>Let us know if you have an opinion.
>
>Please send your responses to the mpls wg mailing list (mpls@ietf.org).
>
>/Loa
>mpls wg-co-chair
>
>>
>> Eric
>
>-- 
>
>
>Loa Andersson                        email: loa@mail01.huawei.com
>Senior MPLS Expert                          loa@pi.nu
>Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls