IETF Logo Mail Archive

Re: [Idr] Implementation call for draft-ietf-idr-bgp-extended-messages (1/24/2017 to 1/31/2017)

"Borchert, Oliver (Fed)" <oliver.borchert@nist.gov> Thu, 16 February 2017 13:39 UTC

Return-Path: <oliver.borchert@nist.gov>
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 76EA712948F; Thu, 16 Feb 2017 05:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nistgov.onmicrosoft.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 e_Hu3uffm4s7; Thu, 16 Feb 2017 05:39:49 -0800 (PST)
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0096.outbound.protection.outlook.com [23.103.200.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86A65129558; Thu, 16 Feb 2017 05:39:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2ILNrjhrDv7MNZwD3zNJxiEHhJr5v4oIiYvquL6em50=; b=pZKfw4ikc426ockTTzs1jC+L5fMyzdPoHmDdNPuaBMFJi2oQS+gkNyn+0RMCeHiAyfJA2M+McPlrPiw0XcJOjwc3u37kHAY4GH5mgYvXPHbV594KGHKtV0I7tyGtP9QyzSQJZZ8M5JXANztDTlzHIS//JlhqCxMzjZtCFvKDYbY=
Received: from BL2PR09MB0996.namprd09.prod.outlook.com (10.167.102.15) by BL2PR09MB0996.namprd09.prod.outlook.com (10.167.102.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Thu, 16 Feb 2017 13:39:47 +0000
Received: from BL2PR09MB0996.namprd09.prod.outlook.com ([10.167.102.15]) by BL2PR09MB0996.namprd09.prod.outlook.com ([10.167.102.15]) with mapi id 15.01.0888.034; Thu, 16 Feb 2017 13:39:47 +0000
From: "Borchert, Oliver (Fed)" <oliver.borchert@nist.gov>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Susan Hares <shares@ndzh.com>, 'John Scudder' <jgs@juniper.net>
Thread-Topic: Implementation call for draft-ietf-idr-bgp-extended-messages (1/24/2017 to 1/31/2017)
Thread-Index: AdJ8sBDDhskHW5f6TcW8KGLFsDty8QBpc3kAAJdU7gABxAtQAAAW6y8AAARLj4A=
Date: Thu, 16 Feb 2017 13:39:47 +0000
Message-ID: <446A644B-6778-4F78-A819-ACF277CE683E@nist.gov>
References: <CY1PR09MB0444DBE54A903BB24A2A0F45844D0@CY1PR09MB0444.namprd09.prod.outlook.com> <24581E62-94D7-4D2E-8157-21ADF1CE7AF1@nist.gov> <00ff01d280b3$33771830$9a654890$@ndzh.com> <944428A7-399E-4DDF-9E65-9FBF94DF3F44@nist.gov> <76CD132C3ADEF848BD84D028D243C927935813E7@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <76CD132C3ADEF848BD84D028D243C927935813E7@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1e.0.170107
authentication-results: spf=none (sender IP is ) smtp.mailfrom=oliver.borchert@nist.gov;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [129.6.140.59]
x-ms-office365-filtering-correlation-id: c4935258-91de-47b3-f58b-08d45671464d
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BL2PR09MB0996;
x-microsoft-exchange-diagnostics: 1; BL2PR09MB0996; 7:dbEBqVpOUib2KHsMRFmA9Z85bOZUhkGWW19O207UWJr7JP2fSEUMRxmjsphyZfN855Mm9gWQNWFd2y8dZuVdFW60JP0rU+NsBmtYv7JjgmurArKAc/C9Dpd+jlx5vmRBsVPzBJ9T0iyA9FoL8Ye1Ev/QmyE9MtLzPQwtwNzCijrZQWcXW2l4k+feFfrKPWmoBje46+bUmW1CIiiCO0tYO+Yn8xq8jWZI849Y10Mh+uH7usdpv5mzWRbtwilf9OEdz6P4BCuxLtARm+hfEoyZ3qcWcUrWbs8zVexxc+5QhU+I1E4srRcoSNpsjAgWEhl1TdohXUGU0Lagc+dtG0uPcQ==
x-microsoft-antispam-prvs: <BL2PR09MB099660FBA01AB61D6CE1A6E4985A0@BL2PR09MB0996.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(65766998875637)(20558992708506)(50582790962513)(138986009662008);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123562025)(20161123564025)(20161123558025)(20161123560025)(20161123555025)(6072148); SRVR:BL2PR09MB0996; BCL:0; PCL:0; RULEID:; SRVR:BL2PR09MB0996;
x-forefront-prvs: 0220D4B98D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39850400002)(39410400002)(39450400003)(39840400002)(377454003)(199003)(24454002)(51914003)(13464003)(189002)(5423002)(30584003)(99286003)(3846002)(6306002)(54906002)(6116002)(102836003)(83506001)(83716003)(25786008)(8936002)(2950100002)(6512007)(15650500001)(8666007)(6436002)(97736004)(5660300001)(53936002)(189998001)(93886004)(4001350100001)(82746002)(3280700002)(66066001)(68736007)(2900100001)(92566002)(1941001)(33656002)(7736002)(230783001)(86362001)(4326007)(305945005)(50986999)(54356999)(76176999)(36756003)(2906002)(8676002)(81156014)(6246003)(53546003)(81166006)(229853002)(122556002)(106356001)(101416001)(3660700001)(6506006)(77096006)(6486002)(389900003)(105586002)(38730400002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR09MB0996; H:BL2PR09MB0996.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <D82CC5AB465A764AA219759825975BE4@namprd09.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2017 13:39:47.5548 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR09MB0996
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/SbAKAdSeEZHB8STP6nR_DFwYgpo>
Cc: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] Implementation call for draft-ietf-idr-bgp-extended-messages (1/24/2017 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 13:39:52 -0000

Looks good to me,
Oliver

On 2/16/17, 1:36 AM, "Dongjie (Jimmy)" <jie.dong@huawei.com> wrote:

    Hi Oliver, 
    
    Thanks for the updates of the implementation report. I've updated the wiki page accordingly, including some editorial changes:
    
    https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-extended-implementations
    
    Please review and let me know if you have any comments.
    
    Best regards,
    Jie
    
    > -----Original Message-----
    > From: Borchert, Oliver (Fed) [mailto:oliver.borchert@nist.gov]
    > Sent: Thursday, February 16, 2017 8:41 AM
    > To: Susan Hares <shares@ndzh.com>; 'John Scudder' <jgs@juniper.net>
    > Cc: idr-chairs@ietf.org; idr@ietf.org
    > Subject: Re: Implementation call for draft-ietf-idr-bgp-extended-messages
    > (1/24/2017 to 1/31/2017)
    > 
    > Sue,
    > We updated our implementations and below find the updated implementation
    > reports for QuaggaSRx and BGPSEC-IO:
    > 
    > Current Wiki summary:
    > https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-extended-implementations
    > 
    > 1	Announce via BGP Capability advertisement (RFC5492) as BGP Extended
    > Capability	Yes	Yes
    > 2	If Extended Message Capability supported, Implementation MUST be able
    > to:	-	-
    > 2a	RECEIVE OPEN message larger than 4096 bytes (section 4, paragraph 2)	Yes
    > 	Yes
    > 2b	RECEIVE A UPDATE message larger tan 4096 bytes	Yes	Yes
    > 3	Applications putting data into BGP Extended messages MUST limit size of
    > payload to handle max message sizes on pathway	Yes	Yes
    > 4	Supports EXTENDED MESSAGE, but peer has not advertised BGP Extended
    > Capability	-	-
    > 4a	SHOULD NOT accept message	yes	yes
    > 4b	MAY Accept EXTENDED MESSAGE (config/implementation knob)	Yes	Yes
    > 5	Does not support EXTENDED Message (no support in code)
    > 5a	Does not send Extended Message capability
    > 5b	If receives Extended Message, follows RFC4221 handling and sends Bad
    > message length Notification
    > 
    > 
    > Updated Summary:
    > 
    > QuaggaSRx
    > ==========
    > 1) yes
    > 2a) – Draft was updated – N/A
    > 2b) yes
    > 3) yes
    > 4a) yes
    > 4b) yes
    > 5a) yes, can be configured
    > 5b) yes, if configured to not support
    > 
    > BGPSEC-IO
    > =========
    > 1) yes
    > 2a) – Draft was updated – N/A
    > 2b) yes
    > 3) yes
    > 4a) yes
    > 4b) yes
    > 5a) yes, can be configured
    > 5b) yes, if configured to not support
    > 
    > Oliver
    > -------------------------------------------------------------
    > Oliver Borchert, Computer Scientist
    > National Institute of Standards and Technology
    > (Phone) 301.975.4856 , (Fax) 301.975.6238
    >

v2.23.0 | Report a Bug | By Email