Re: [bess] WG Last Call for draft-ietf-bess-mvpn-expl-track
<zhang.zheng@zte.com.cn> Thu, 13 July 2017 00:56 UTC
Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F2212EC48 for <bess@ietfa.amsl.com>; Wed, 12 Jul 2017 17:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 GJeUN2CfajwT for <bess@ietfa.amsl.com>; Wed, 12 Jul 2017 17:56:23 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 50BCE12EC01 for <bess@ietf.org>; Wed, 12 Jul 2017 17:56:21 -0700 (PDT)
X-scanvirus: By SEG_CYREN AntiVirus Engine
X-scanresult: CLEAN
X-MAILFROM: <zhang.zheng@zte.com.cn>
X-RCPTTO: <draft-ietf-bess-mvpn-expl-track@ietf.org>
X-FROMIP: 10.30.3.21
X-SEG-Scaned: 1
X-Received: unknown,10.30.3.21,20170713084647
Received: from unknown (HELO mse02.zte.com.cn) (10.30.3.21) by localhost with (AES256-SHA encrypted) SMTP; 13 Jul 2017 00:46:47 -0000
Received: from njxapp02.zte.com.cn ([10.41.132.201]) by mse02.zte.com.cn with SMTP id v6D0uEIb092032; Thu, 13 Jul 2017 08:56:14 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Thu, 13 Jul 2017 08:56:15 +0800 (CST)
Date: Thu, 13 Jul 2017 08:56:15 +0800
X-Zmail-TransId: 2afb5966c52f395-7209e
X-Mailer: Zmail v1.0
Message-ID: <201707130856154985830@zte.com.cn>
References: e208212c-9cc0-5e13-23fe-2352ae98d0ff@orange.com
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: thomas.morin@orange.com
Cc: bess@ietf.org, draft-ietf-bess-mvpn-expl-track@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse02.zte.com.cn v6D0uEIb092032
X-HQIP: 127.0.0.1
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/mlPrCP0s2Aq3-z0UJSjJ1D5D2fM>
Subject: Re: [bess] WG Last Call for draft-ietf-bess-mvpn-expl-track
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 00:56:26 -0000
Support the publication of this draft. And in section 3, " Note that if there is no installed S-PMSI A-D route for (C-S2,C-G2), then Route1 would be (C-S2,C-G2)'s match for reception and also its match for tracking. Also note that if a match for tracking does not have the LIR flag or the LIR-pF flag set, no explicit tracking information will be generated. See Section 5. " It seems like that it should be " then Route1 would be (C-S1,C-G1)'s match for reception and also its match for tracking. " If it is a nit? Thanks, Sandy 原始邮件 发件人: <thomas.morin@orange.com> 收件人: <bess@ietf.org> <draft-ietf-bess-mvpn-expl-track@ietf.org> 日 期 :2017年07月10日 23:24 主 题 :[bess] WG Last Call for draft-ietf-bess-mvpn-expl-track Hello Working Group, This email starts a Working Group Last Call on draft-ietf-bess-mvpn-expl-track-02 [1] which is considered mature and ready for a final working group review. Please read this document if you haven't read the most recent version yet, and send your comments to the list, no later than *24th of July*. Note that this is *not only* a call for comments on the document it is also a call for support (or not) to publish this document as a Standard Track RFC. *Coincidentally*, we are also polling for knowledge of any IPR that applies to draft-ietf-bess-mvpn-expl-track, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document Author or Contributor of the draft please respond to this email and indicate whether or not you are aware of any relevant IPR, additionally to what was already disclosed ([2]). We are **also polling for knowledge of implementations** of part or all of what this document specifies. This information is expected as per [2]. Please inform the mailing list, or the chairs, or only one of the chairs. Thank you, T&M [1] https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-expl-track [2] https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-bess-mvpn-expl-track [3] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
- [bess] WG Last Call for draft-ietf-bess-mvpn-expl… Thomas Morin
- Re: [bess] WG Last Call for draft-ietf-bess-mvpn-… Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [bess] WG Last Call for draft-ietf-bess-mvpn-… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] WG Last Call for draft-ietf-bess-mvpn-… Eric C Rosen
- Re: [bess] WG Last Call for draft-ietf-bess-mvpn-… Kotalwar, Jayant (Nokia - US/Mountain View)
- Re: [bess] WG Last Call for draft-ietf-bess-mvpn-… zhang.zheng
- Re: [bess] WG Last Call for draft-ietf-bess-mvpn-… Jeffrey (Zhaohui) Zhang