Return-Path: X-Original-To: idr@ietfa.amsl.com Delivered-To: idr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B94643A1182 for ; Mon, 24 Feb 2020 11:21:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 3tW2SfPVzqEi for ; Mon, 24 Feb 2020 11:21:57 -0800 (PST) Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2109.outbound.protection.outlook.com [40.107.243.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 956033A117D for ; Mon, 24 Feb 2020 11:21:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dLNJXjCvfxdxZmXfldyX0DqjFaFtJ//1+hC6w0HPxspfnlSjmUKvOevdRLAKZ2aT8CWD2Rg0dsHDrmVs5V176eePtmtahQiZicwppsqpsLS7eUvADSApZ080jPEAJMSIPpKuzlykaOYR+cREBzufULay9BCj11hU0YMJNC3mT/Om+vxeqHZbyi7TlGiWKGBJCH94L4xwD9AdTb3+9SLYuNzeOgQNz4bmvsouxvvbuXqgZYQhYT4t1wGn4pdcJjK2e7SIXfo4kmgWUFsc2UqxVcdeOhRfMtrDIrET638ex7N9MXBHYHWnRqDMj6NJ8IkwrhMjLSS5yqLcd9b0w1QR8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=j0Pc9irF6fXYZ0k1/9q4OSkhzlNcsG5ZpUxp82APhGo=; b=KenCKOuh0osW35hwc7l0HCcKlJlsg3z+CYxvQetJqN2NP+9TVnNUVNEGow3PrLt4G/GOG0NfL+koORuVTnEi1ASRITnYqvIvjdC3vkVU8UT6OW+7MjAdklfyymHeWdQBkvPSs3d6NwE8i0F5nLjNTTDfW83aPbiqjAweUviZOuqxcbSXkrcGmXNBO5IYKaFUTDNCXIliMLrncTeDLV+fYHaFpOdGdgZgNbet3U+R/TKaOtRO6eVLL9LmQy7xCDViBlPit0iGN5VmbD6fuz2bjHLygf1g1knzjd9p35rjMreOKenaMlEmyVZ8yl79x6FuZnhRQM/sVS/uuyrjk9mW4A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=j0Pc9irF6fXYZ0k1/9q4OSkhzlNcsG5ZpUxp82APhGo=; b=a35G/qUEgw/BiRTJj79Wj8MOzN7+X0LGccJbMoYOxb6hOuCjnJurl2F9csCl6FJqygwHoiP6l60sgo9URWNFFdbKgoEtxmnaNRTSEM+so2SEI8/qrwCU42RkKvosBGBauT/hoLXRwh5H2bokTWYYRHp7bPtH0SCl2hN2FBpSW1U= Received: from BY5PR13MB3651.namprd13.prod.outlook.com (2603:10b6:a03:22e::19) by BY5PR13MB3540.namprd13.prod.outlook.com (2603:10b6:a03:1ab::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.9; Mon, 24 Feb 2020 19:21:54 +0000 Received: from BY5PR13MB3651.namprd13.prod.outlook.com ([fe80::789b:f4a:c3e3:e921]) by BY5PR13MB3651.namprd13.prod.outlook.com ([fe80::789b:f4a:c3e3:e921%7]) with mapi id 15.20.2772.012; Mon, 24 Feb 2020 19:21:54 +0000 From: Huaimo Chen To: Robert Raszuk , Susan Hares CC: "idr@ietf. org" Thread-Topic: [Idr] draft-wu-idr-bgp-segment-allocation-ext-04 - IPR call prior to WG adoption call (2/24 to 3/4) Thread-Index: AdXrGPiwgmyjrHdoRa2SgqmdS5rX2AAAnOOAAAp/6kk= Date: Mon, 24 Feb 2020 19:21:54 +0000 Message-ID: References: <002101d5eb19$12b85e00$38291a00$@ndzh.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=huaimo.chen@futurewei.com; x-originating-ip: [12.111.81.95] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: f9c4330c-41cb-4836-51cd-08d7b95ecf11 x-ms-traffictypediagnostic: BY5PR13MB3540: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 032334F434 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(376002)(366004)(346002)(39850400004)(136003)(189003)(199004)(76116006)(186003)(5660300002)(9686003)(8936002)(55016002)(966005)(64756008)(86362001)(66446008)(66556008)(66946007)(66476007)(4326008)(110136005)(8676002)(26005)(71200400001)(316002)(19627405001)(2906002)(7696005)(478600001)(44832011)(81156014)(6506007)(52536014)(53546011)(81166006)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY5PR13MB3540; H:BY5PR13MB3651.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 3IwVhbBqmOAPeaJmzn0+cWD00BgtHtecSv7GyBU0yAJmIIimlajwbol7UKptApJTfVGYqXS9QhJY6bzHvmX9rLBCVKBJO0wze0Hw+6RgUeE5sNUKUgoxy6Z4wVBElLofpbpgdusW+KmhbhyhCpzFM8D4Cj8CQL9GiHABlmXKNLIRFEXYJ/6qnG0ep/vE7iN9rBnuAFimYC+0g2hiIdUailoUt6WiaG6rseZRsMOJoc7sBbn9/8equR8D59sLkCMQEy5S21NL8KmCRiL7kdTRoozIcG7Bkda8/hgZBVsFrg6IWJeoWUcACQ4CgKdXUVY6cZ48zDZmaPL5tLNi7T+xY8lPNnh3Tqr56lFd+mEsZLJZMKfR+uSdSfkldq0+q4tWDCJGzp0l5hs8YDVXgCChyvccvSmPjgps2yQNd3o6NkqkZ9/iGfGsO+09xThngB7L/trXClehUem+pUu6TTjH21D4rEgLY/916Dc4vrxDDvVnGelwIv2UBDFV1xVJZ4Gu5iwQiGxHhfM18BB6eOO4JQ== x-ms-exchange-antispam-messagedata: AKL7mKbmYg0mK7TI1DGGA3nW1RMMuSLDFsgwPXh2cIebbzLO+dMU3IDUwQgbXCwGzbTnxQVfyKiTspyY1iqL/kR9G5jkqvLIUI/oDBYNZPi7fgvpR88XI8T5LF3heACAymUDvcxb4klfz3yHnFYI2A== x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_BY5PR13MB3651BBA5ACA8C037B3292289F2EC0BY5PR13MB3651namp_" MIME-Version: 1.0 X-OriginatorOrg: Futurewei.com X-MS-Exchange-CrossTenant-Network-Message-Id: f9c4330c-41cb-4836-51cd-08d7b95ecf11 X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Feb 2020 19:21:54.7471 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: oANV9cWUhMrEhI1iD9U+Tm0opeX84uO5A/UNu9G8QxwSe3U6WOPCSKfTHlfWShUH1rMsoUuxVQvPgKF7Jh7Jbg== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB3540 Archived-At: Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-04 - IPR call prior to WG adoption call (2/24 to 3/4) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2020 19:22:00 -0000 --_000_BY5PR13MB3651BBA5ACA8C037B3292289F2EC0BY5PR13MB3651namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Robert, We have addressed all the comments from the last adoption call [4/18 - = 5/2/2019] in the updated document/draft. For example, the extensions to BG= P-LS for SIDs are removed, and a new AFI/SAFI for SIDs is used as suggested= by some people. This seems a core change. The updated document is presented in IETF 106, and there is no objectio= n during our presentation. In addition, I have communicated with all the people who were against t= he adoption during the last adoption call and did not receive any objection= . Only one person hopes that Yang could be used for SIDs. Best Regards, Huaimo ________________________________ From: Idr on behalf of Robert Raszuk Sent: Monday, February 24, 2020 9:05 AM To: Susan Hares Cc: idr@ietf. org Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-04 - IPR call pr= ior to WG adoption call (2/24 to 3/4) Hi, We already had adoption call for this draft and comments received were not = in favor. May I ask why are we to repeat this all over again especially as the core t= heme of the draft did not change ? Ref: https://mailarchive..ietf.org/arch/msg/idr/nxjbsrSAsg8TmxKqn_xlUWGbgJU/ https://mailarchive.ietf.org/arch/msg/idr/Jdv3np6vFI8gA7BKkQa1VByCuuI/ https://mailarchive.ietf.org/arch/msg/idr/H_ERZ1h1Ia6K6PR7hQrmIXaJkvI/ Thx, R. PS. Below is the original adoption call: From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares Sent: Thursday, April 18, 2019 10:05 AM To: idr@ietf.org Subject: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2= 019] - 2 week WG adoption call This begins a 2 week WG Adoption call for draft-wu-idr-bgp-segment-allocati= on-ext-02.txt. You can access the draft at: https://datatracker.ietf.org/doc/draft-wu-idr-bgp-segment-allocation-ext/ In your comments, consider: On Mon, Feb 24, 2020 at 2:48 PM Susan Hares > wrote: Greetings: This begins an IPR call for draft-wu-idr-bgp-segment-ext-04.txt prior to WG= adoption call. The WG adoption call will begin as soon as all the author= s have responded to this message. For authors who have responded to an IPR call, please you will need to agai= n respond to this IPR call. Cheers, Susan Hares _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr --_000_BY5PR13MB3651BBA5ACA8C037B3292289F2EC0BY5PR13MB3651namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Robert,
  
    We have addressed all the comments from the last adoption cal= l [4/18 - 5/2/2019] in the updated document/draft.  For example,&= nbsp;the extensions to BGP-LS for SIDs are removed, and a new AFI/SAFI for = SIDs is used as suggested by some people. This seems a core change.

    The= updated document is presented in IETF 106, and there is no objectio= n during our presentation.

    In addition, I have communicated with all the people who were= against the adoption during the last adoption call and did not receive any= objection. Only one person hopes that Yang could be used for SIDs.

Best Regards,
Huaimo
From: Idr <idr-bounces@i= etf.org> on behalf of Robert Raszuk <robert@raszuk.net>
Sent: Monday, February 24, 2020 9:05 AM
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf. org <idr@ietf.org>
Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-04 - IPR = call prior to WG adoption call (2/24 to 3/4)
 
Hi,

We already had adoption call for this draft and comments received were= not in favor. 

May I ask why are we to repeat this all over again especially as the c= ore theme of the draft did not change ? 

Ref: 

h= ttps://mailarchive..ietf.org/arch/msg/idr/nxjbsrSAsg8TmxKqn_xlUWGbgJU/&= nbsp;


Thx,
R.

PS. Below is the original adoption call: 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Thursday, April 18, 2019 10:05 AM
To: idr@ietf.org
Subject: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call

 

This begins a 2 week WG Adopt= ion call for draft-wu-idr-bgp-segment-allocation-ext-02.= txt.  You can access the draft at:

 

https://datatrack= er.ietf.org/doc/draft-wu-idr-bgp-segment-allocation-ext/

 

In your comments, consider:

 


On Mon, Feb 24, 2020 at 2:48 PM Sus= an Hares <shares@ndzh.com> wro= te:

Greetings:

 

This begins an IPR call for draft-wu-idr-bgp-segme= nt-ext-04.txt prior to WG adoption call.   The WG adoption call w= ill begin as soon as all the authors have responded to this message. 

 

For authors who have responded to an IPR call, ple= ase you will need to again respond to this IPR call.

 

Cheers, Susan Hares

 

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr=
--_000_BY5PR13MB3651BBA5ACA8C037B3292289F2EC0BY5PR13MB3651namp_--