From nobody Sun Jan 1 18:50:40 2017 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2FC1129466; Sun, 1 Jan 2017 18:50:34 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Joel Jaeggli" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148332543492.25163.10499443805665312317.idtracker@ietfa.amsl.com> Date: Sun, 01 Jan 2017 18:50:34 -0800 Archived-At: Cc: idr@ietf.org, idr-chairs@ietf.org, draft-ietf-idr-deprecate-30-31-129@ietf.org, shares@ndzh.com Subject: [Idr] Joel Jaeggli's Yes on draft-ietf-idr-deprecate-30-31-129-02: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2017 02:50:35 -0000 Joel Jaeggli has entered the following ballot position for draft-ietf-idr-deprecate-30-31-129-02: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-30-31-129/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Stop them before they kill again. Imho, while we're not doing it here, we should probably provide advice to implementers or even revisit how we allocate them on how to do this safely in the future cause squatting on code points is definite minefield here. From nobody Mon Jan 2 05:14:32 2017 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 62F8B124281; Mon, 2 Jan 2017 05:14:31 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "Mirja Kuehlewind" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148336287139.21869.17056871012280815893.idtracker@ietfa.amsl.com> Date: Mon, 02 Jan 2017 05:14:31 -0800 Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, idr-chairs@ietf.org Subject: [Idr] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-idr-large-community-11=3A_=28with_COMMENT=29?= X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2017 13:14:31 -0000 Mirja Kühlewind has entered the following ballot position for draft-ietf-idr-large-community-11: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- One question: Since the Global Administrator field could also be not an ASN, would it be useful to say something about what should be done if an unknow value is received (ignore, remove, log an error...)? From nobody Mon Jan 2 05:25:48 2017 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 E0C4A1295EB for ; Mon, 2 Jan 2017 05:25:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 MvwfuEA3a5vb for ; Mon, 2 Jan 2017 05:25:41 -0800 (PST) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AB8B124281 for ; Mon, 2 Jan 2017 05:25:40 -0800 (PST) Received: by mail-wm0-x22b.google.com with SMTP id a197so365602998wmd.0 for ; Mon, 02 Jan 2017 05:25:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=arKPVUKnFhvRfpKDjDdgOob62ZN7sm/mBaQbe8tUBG0=; b=2IoKIePsU9x2G9qsmC+0jPTkTB7TW0xqNPNCjqrYDMCLmgKJomOI7wooDUwKJGx9YI HbtgbTIthGX+7fpKkUXk2HMUE2OJ89/eQfmnhqym8uAfi3WwnD4LmA74AhQLtLE12U8W V51zKSLK8fkiyY48sVRPgkzI71ribg79Xyu8rs+YGdZJKLQur3vWNO5cNnFgKA6y0cSC 466JskypgbnCrP2UfAP1qlORrAPVq69M/kSwSefqVaXDCyF7aGEV7kSys/ymwlhwy5+/ XrNGU1KbNmX8Ee8v8wAPHXhE7RCVq/XhM+ZE7AfRXKE12t6PY6d6m9bTnr/KbNoKIpBt 2E4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=arKPVUKnFhvRfpKDjDdgOob62ZN7sm/mBaQbe8tUBG0=; b=edwQw0GEku1YixJ/P8mXgKACxDqnGx4Aj7/XU5V8pK4wamnxs/L/8sBVN73ZzzHDIY hoW9N3Sj904grPdNNJ886FH+572mDL/yHpizJEd0kXVxT6zl22ETCg0w/ycuuZXxzlN/ 67ZV6M/LPil85ebpYulv6DJRF4zVoQ3vv6TKqGvy7006mxrJgoyq/fzjHXygeFQBRNdG CrSLOk6QjNTS1cTimMF3HLyjsV4p4gVgMPWQUYdlIlMrP/bynKkBK9Dk1mTkl+q8oIMH qYISfQjrnQVBicT1Ce5BsIaeaxvlld0VFq1e1MoVi93YnrW2a57TKc7Sn+Doy+329aSz KY1g== X-Gm-Message-State: AIkVDXJsnHWDI1uX/pYA1pxeLf8X5gs0Rl4GUPPkO/JAm21Drbd/+D/jTMPlYnLKZpZ2bA== X-Received: by 10.28.229.72 with SMTP id c69mr54567387wmh.110.1483363539025; Mon, 02 Jan 2017 05:25:39 -0800 (PST) Received: from localhost ([2001:67c:208c:10:4994:c3aa:ef45:cccf]) by smtp.gmail.com with ESMTPSA id i10sm87985945wjd.15.2017.01.02.05.25.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Jan 2017 05:25:36 -0800 (PST) Date: Mon, 2 Jan 2017 14:25:35 +0100 From: Job Snijders To: Mirja Kuehlewind Message-ID: <20170102132535.GE60639@Vurt.local> References: <148336287139.21869.17056871012280815893.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <148336287139.21869.17056871012280815893.idtracker@ietfa.amsl.com> X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.7.2 (2016-11-26) Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, The IESG , idr-chairs@ietf.org Subject: Re: [Idr] =?iso-8859-1?q?Mirja_K=FChlewind=27s_No_Objection_on_draft-?= =?iso-8859-1?q?ietf-idr-large-community-11=3A_=28with_COMMENT=29?= X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2017 13:25:45 -0000 Dear Mirja, On Mon, Jan 02, 2017 at 05:14:31AM -0800, Mirja Kuehlewind wrote: > Mirja Kühlewind has entered the following ballot position for > draft-ietf-idr-large-community-11: No Objection Thank you for your review. > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > One question: Since the Global Administrator field could also be not an > ASN, would it be useful to say something about what should be done if an > unknow value is received (ignore, remove, log an error...)? Section 5 states: """ The BGP Large Communities Global Administrator field may contain any value, and a BGP Large Communities attribute MUST NOT be considered malformed if the Global Administrator field contains an unallocated, unassigned or reserved ASN. """ Further more, based on our experience with the current implementations [1], [2] there was no perceived ambiguity amongst the implementers what to do with non ASN values in the Global Administator field. The global administrator field contains just an unsigned 32-bit integer. The consensus on the mailing list was to treat the non ASN values exactly the same as normal values. As such it would not be correct to ignore, remove, or log an error. In other words, the ability to put a non-ASN values in the Global Administrator field is by design. Kind regards, Job [1]: http://largebgpcommunities.net/implementations/ [2]: https://trac.tools.ietf.org/wg/idr/trac/wiki/draft-ietf-idr-large-community%20implementations From nobody Mon Jan 2 05:42:39 2017 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 0AC2E1295EF for ; Mon, 2 Jan 2017 05:42:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.002 X-Spam-Level: X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-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 1TXR_iIykCdg for ; Mon, 2 Jan 2017 05:42:34 -0800 (PST) Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CF93129459 for ; Mon, 2 Jan 2017 05:42:34 -0800 (PST) Received: (qmail 17668 invoked from network); 2 Jan 2017 14:42:31 +0100 Received: from p5dec2761.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.39.97) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 2 Jan 2017 14:42:31 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) From: "Mirja Kuehlewind (IETF)" In-Reply-To: <20170102132535.GE60639@Vurt.local> Date: Mon, 2 Jan 2017 14:42:29 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <99BB7D9F-1715-422B-86E5-9C01F0D6C35B@kuehlewind.net> References: <148336287139.21869.17056871012280815893.idtracker@ietfa.amsl.com> <20170102132535.GE60639@Vurt.local> To: Job Snijders X-Mailer: Apple Mail (2.3259) Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, The IESG , idr-chairs@ietf.org Subject: Re: [Idr] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-idr-large-community-11=3A_=28with_COMMENT=29?= X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2017 13:42:37 -0000 Okay, thanks for your clarification. Was reading this part in section 5 = and therefore wondering if any action should follow. But if that was = discussed that=E2=80=99s fine. > Am 02.01.2017 um 14:25 schrieb Job Snijders : >=20 > Dear Mirja, >=20 > On Mon, Jan 02, 2017 at 05:14:31AM -0800, Mirja Kuehlewind wrote: >> Mirja K=C3=BChlewind has entered the following ballot position for >> draft-ietf-idr-large-community-11: No Objection >=20 > Thank you for your review. >=20 >> = ---------------------------------------------------------------------- >> COMMENT: >> = ---------------------------------------------------------------------- >>=20 >> One question: Since the Global Administrator field could also be not = an >> ASN, would it be useful to say something about what should be done if = an >> unknow value is received (ignore, remove, log an error...)? >=20 > Section 5 states: >=20 > """ > The BGP Large Communities Global Administrator field may contain > any value, and a BGP Large Communities attribute MUST NOT be > considered malformed if the Global Administrator field contains an > unallocated, unassigned or reserved ASN. > """ >=20 > Further more, based on our experience with the current implementations > [1], [2] there was no perceived ambiguity amongst the implementers = what > to do with non ASN values in the Global Administator field. The global > administrator field contains just an unsigned 32-bit integer. >=20 > The consensus on the mailing list was to treat the non ASN values > exactly the same as normal values. As such it would not be correct to > ignore, remove, or log an error. >=20 > In other words, the ability to put a non-ASN values in the Global > Administrator field is by design. >=20 > Kind regards, >=20 > Job >=20 > [1]: http://largebgpcommunities.net/implementations/ > [2]: = https://trac.tools.ietf.org/wg/idr/trac/wiki/draft-ietf-idr-large-communit= y%20implementations >=20 From nobody Tue Jan 3 07:48:22 2017 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 0FFE612962D; Tue, 3 Jan 2017 07:48:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.621 X-Spam-Level: X-Spam-Status: No, score=-17.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, 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 HSjT8zqcCrCF; Tue, 3 Jan 2017 07:48:16 -0800 (PST) Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CC00129579; Tue, 3 Jan 2017 07:48:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6960; q=dns/txt; s=iport; t=1483458496; x=1484668096; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=GuPiFvBzUDTdXwiiso8L1gGzsj4TORJRibn8ghAl3tI=; b=SuRVufFlPxb51RGeCad98ILQZQuqpcv2BL922WZtAhWAncvBE7cZUJlz ArT6PfyUKnL/+o7ojVFZayUUTdC2OYeW6KIokkBRwxOQxgN0bn8XGILPE 90HNfTVVqGJlVmhjVetD8VZXiqDBxqKgIvxRoksU05Jt07Nq4In/fXGPE A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A9AQALx2tY/5FdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgnE5DQEBAQEBH1+BDAeNUKQ5gxmCD4IIKoV4AhqBLT8UAQIBAQE?= =?us-ascii?q?BAQEBYiiEaQYjVhACAQg/AwICAjAUEQIEAQ0FiHAOrmyCJSuKFwEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARgFhkWCAoJfh0otgjAFlQmFdAGGU4pqkFWSPAEfOIEqPAG?= =?us-ascii?q?FTnKHMYENAQEB?= X-IronPort-AV: E=Sophos;i="5.33,455,1477958400"; d="scan'208,217";a="367202368" Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jan 2017 15:48:15 +0000 Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v03FmFTo006017 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 3 Jan 2017 15:48:15 GMT Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 3 Jan 2017 09:48:15 -0600 Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Tue, 3 Jan 2017 09:48:14 -0600 From: "Alvaro Retana (aretana)" To: Joel Jaeggli , The IESG Thread-Topic: Joel Jaeggli's Yes on draft-ietf-idr-deprecate-30-31-129-02: (with COMMENT) Thread-Index: AQHSZKL+ybZvtQFHH0KPZGD34kRhsqEm+RMA Date: Tue, 3 Jan 2017 15:48:14 +0000 Message-ID: References: <148332543492.25163.10499443805665312317.idtracker@ietfa.amsl.com> In-Reply-To: <148332543492.25163.10499443805665312317.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/f.1d.0.161209 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.117.15.4] Content-Type: multipart/alternative; boundary="_000_BFECD3D545E245ACB393DAED2F0BC55Bciscocom_" MIME-Version: 1.0 Archived-At: Cc: "idr@ietf.org" , "draft-ietf-idr-deprecate-30-31-129@ietf.org" , "shares@ndzh.com" , "idr-chairs@ietf.org" Subject: Re: [Idr] Joel Jaeggli's Yes on draft-ietf-idr-deprecate-30-31-129-02: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2017 15:48:18 -0000 --_000_BFECD3D545E245ACB393DAED2F0BC55Bciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sm9lbDoNCg0KSGkhDQoNClllcywgdGhlcmXigJlzIGJlZW4gcGxlbnR5IG9mIGRpc2N1c3Npb24g aW4gdGhlIFdH4oCmb25lIG9mIHRoZSBwcm9wb3NhbHMgaXMgZGVmaW5lIGV4cGVyaW1lbnRhbCBw YXRoIGF0dHJpYnV0ZXM7IHBvaW50aW5nIGF0IHRoaXMganVzdCBiZWNhdXNlIGl0IHdhcyBkaXNj dXNzZWQgaW4gS29yZWE6IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1oYWFzLWlk ci1leHRlbmRlZC1leHBlcmltZW50YWwtMDANCg0KVGhhbmtzIQ0KDQpBbHZhcm8uDQoNCk9uIDEv MS8xNywgOTo1MCBQTSwgIkpvZWwgSmFlZ2dsaSIgPGpvZWxqYUBib2d1cy5jb208bWFpbHRvOmpv ZWxqYUBib2d1cy5jb20+PiB3cm90ZToNCg0KSW1obywgd2hpbGUgd2UncmUgbm90IGRvaW5nIGl0 IGhlcmUsIHdlIHNob3VsZCBwcm9iYWJseSBwcm92aWRlIGFkdmljZSB0bw0KaW1wbGVtZW50ZXJz IG9yIGV2ZW4gcmV2aXNpdCBob3cgd2UgYWxsb2NhdGUgdGhlbSBvbiBob3cgdG8gZG8gdGhpcw0K c2FmZWx5IGluIHRoZSBmdXR1cmUgY2F1c2Ugc3F1YXR0aW5nIG9uIGNvZGUgcG9pbnRzIGlzICBk ZWZpbml0ZQ0KbWluZWZpZWxkIGhlcmUuDQoNCg== --_000_BFECD3D545E245ACB393DAED2F0BC55Bciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: <174CF3BAA9D28C40874BDE90D2FC9890@emea.cisco.com> Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0 IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls eTotd2Via2l0LXN0YW5kYXJkOw0KCXBhbm9zZS0xOjAgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KLyog U3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29O b3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXpl OjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQphOmxpbmssIHNwYW4u TXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRl eHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0Zv bGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1k ZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlw ZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseTpDYWxpYnJpOw0KCWNvbG9yOndpbmRvd3Rl eHQ7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsO30NCnNwYW4ubXNv SW5zDQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCW1zby1zdHlsZS1uYW1lOiIiOw0K CXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7DQoJY29sb3I6dGVhbDt9DQouTXNvQ2hwRGVmYXVs dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBw YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4w aW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9 DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgYmdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVT IiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250 LWZhbWlseTpDYWxpYnJpIj5Kb2VsOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGli cmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPkhpITxvOnA+ PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250 LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0 O2ZvbnQtZmFtaWx5OkNhbGlicmkiPlllcywgdGhlcmXigJlzIGJlZW4gcGxlbnR5IG9mIGRpc2N1 c3Npb24gaW4gdGhlIFdH4oCmb25lIG9mIHRoZSBwcm9wb3NhbHMgaXMgZGVmaW5lIGV4cGVyaW1l bnRhbCBwYXRoIGF0dHJpYnV0ZXM7IHBvaW50aW5nIGF0IHRoaXMganVzdCBiZWNhdXNlIGl0IHdh cyBkaXNjdXNzZWQgaW4gS29yZWE6DQo8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0 bWwvZHJhZnQtaGFhcy1pZHItZXh0ZW5kZWQtZXhwZXJpbWVudGFsLTAwIj5odHRwczovL3Rvb2xz LmlldGYub3JnL2h0bWwvZHJhZnQtaGFhcy1pZHItZXh0ZW5kZWQtZXhwZXJpbWVudGFsLTAwPC9h PiZuYnNwOyZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86 cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5 bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+VGhhbmtzITxvOnA+PC9v OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp emU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv bnQtZmFtaWx5OkNhbGlicmkiPkFsdmFyby48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpD YWxpYnJpIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0i Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0I1QzRERiA0LjVwdDtwYWRkaW5nOjBpbiAw aW4gMGluIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+ DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gMS8xLzE3LCA5OjUwIFBNLCAmcXVvdDtK b2VsIEphZWdnbGkmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpqb2VsamFAYm9ndXMuY29tIj5q b2VsamFAYm9ndXMuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwv ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt aWx5OiZxdW90Oy13ZWJraXQtc3RhbmRhcmQmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6 YmxhY2siPkltaG8sIHdoaWxlIHdlJ3JlIG5vdCBkb2luZyBpdCBoZXJlLCB3ZSBzaG91bGQgcHJv YmFibHkgcHJvdmlkZSBhZHZpY2UgdG88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7 LXdlYmtpdC1zdGFuZGFyZCZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjpibGFjayI+aW1w bGVtZW50ZXJzIG9yIGV2ZW4gcmV2aXNpdCBob3cgd2UgYWxsb2NhdGUgdGhlbSBvbiBob3cgdG8g ZG8gdGhpczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDstd2Via2l0LXN0YW5kYXJk JnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5zYWZlbHkgaW4gdGhlIGZ1dHVy ZSBjYXVzZSBzcXVhdHRpbmcgb24gY29kZSBwb2ludHMgaXMmbmJzcDsmbmJzcDtkZWZpbml0ZTxv OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDstd2Via2l0LXN0YW5kYXJkJnF1b3Q7LCZx dW90O3NlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5taW5lZmllbGQgaGVyZS48bzpwPjwvbzpwPjwv c3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+ PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_BFECD3D545E245ACB393DAED2F0BC55Bciscocom_-- From nobody Tue Jan 3 19:21:54 2017 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CAAF3126BF6; Tue, 3 Jan 2017 19:21:48 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Terry Manderson" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148350010882.28015.13406640106946951460.idtracker@ietfa.amsl.com> Date: Tue, 03 Jan 2017 19:21:48 -0800 Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, idr-chairs@ietf.org Subject: [Idr] Terry Manderson's Yes on draft-ietf-idr-large-community-11: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 03:21:49 -0000 Terry Manderson has entered the following ballot position for draft-ietf-idr-large-community-11: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Brilliant. Thank you! From nobody Wed Jan 4 06:52:43 2017 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 43068124281; Wed, 4 Jan 2017 06:52:42 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Benoit Claise" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> Date: Wed, 04 Jan 2017 06:52:42 -0800 Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, rick.casarez@gmail.com, idr-chairs@ietf.org Subject: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 14:52:42 -0000 Benoit Claise has entered the following ballot position for draft-ietf-idr-large-community-11: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I see from the abstract: "The attribute is suitable for use with four-octet ASNs." I also see this text, which doesn't mention four-octet ASNs The Global Administrator field is intended to allow different Autonomous Systems to define BGP Large Communities without collision. This field SHOULD be an Autonomous System Number (ASN), in which case the Local Data Parts are to be interpreted as defined by the owner of the ASN. The use of Reserved ASNs (0 [RFC7607], 65535 and 4294967295 [RFC7300]) is NOT RECOMMENDED. What if the ASN is two bytes, we use padding? How? Even if we would say: "This field SHOULD be an four-octet Autonomous System Number (ASN)", it doesn't preclude inserting a two-octet ASN in the Global Administrator field. Isn't it better to specify how? >From RFC 6793: Currently assigned two-octet AS numbers are converted into four-octet AS numbers by setting the two high-order octets of the four-octet field to zero. Such a four-octet AS number is said to be mappable to a two-octet AS number. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks John for an excellent shepherd writeup. From nobody Wed Jan 4 07:22:05 2017 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 36FF01294F0; Wed, 4 Jan 2017 07:21:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.302 X-Spam-Level: X-Spam-Status: No, score=-7.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 DoVHLx9Zv5kM; Wed, 4 Jan 2017 07:21:57 -0800 (PST) Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D37129463; Wed, 4 Jan 2017 07:21:57 -0800 (PST) Received: by guelah.shrubbery.net (Postfix, from userid 7053) id C1DB287538; Wed, 4 Jan 2017 15:21:56 +0000 (UTC) Date: Wed, 4 Jan 2017 15:21:56 +0000 From: heasley To: Benoit Claise Message-ID: <20170104152156.GC21501@shrubbery.net> References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc X-note: live free, or die! X-homer: i just want to have a beer while i am caring. X-Claimation: an engineer needs a manager like a fish needs a bicycle X-reality: only YOU can put an end to the embarrassment that is Tom Cruise User-Agent: Mutt/1.6.1 (2016-04-27) Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, The IESG , idr-chairs@ietf.org, rick.casarez@gmail.com Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 15:21:58 -0000 Wed, Jan 04, 2017 at 06:52:42AM -0800, Benoit Claise: > I see from the abstract: "The attribute is suitable for use with > four-octet ASNs." > I also see this text, which doesn't mention four-octet ASNs > > The Global Administrator field is intended to allow different > Autonomous Systems to define BGP Large Communities without > collision. > This field SHOULD be an Autonomous System Number (ASN), in which > case > the Local Data Parts are to be interpreted as defined by the owner > of > the ASN. The use of Reserved ASNs (0 [RFC7607], 65535 and > 4294967295 > [RFC7300]) is NOT RECOMMENDED. > > What if the ASN is two bytes, we use padding? How? > Even if we would say: "This field SHOULD be an four-octet Autonomous > System Number (ASN)", it doesn't preclude inserting a two-octet ASN in > the Global Administrator field. > Isn't it better to specify how? > > >From RFC 6793: > > Currently assigned two-octet AS numbers are converted into > four-octet > AS numbers by setting the two high-order octets of the four-octet > field to zero. Such a four-octet AS number is said to be mappable > to > a two-octet AS number. The draft should just reference rfc 6793, which ISTR it once had, though that version may not have been published. From nobody Wed Jan 4 07:26:54 2017 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 33A2E1294F0; Wed, 4 Jan 2017 07:26:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 t8Hl7joUr79R; Wed, 4 Jan 2017 07:26:50 -0800 (PST) Received: from mail-lf0-x241.google.com (mail-lf0-x241.google.com [IPv6:2a00:1450:4010:c07::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1172D129463; Wed, 4 Jan 2017 07:26:50 -0800 (PST) Received: by mail-lf0-x241.google.com with SMTP id d16so32964979lfb.1; Wed, 04 Jan 2017 07:26:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=yqu345YiYwyJA84l7DM8rJl0SvYILsxla4fSJDuJl6c=; b=DEdsrE7oCSub0072QAl2oMEM1LC1RWVbb2DLCMvU3CeP+JKVzFpt1O0ilqOdrRvGvc Bm3/+jmc9AEQcSattqkbdh9ugJLkrfTMJ26hbNMnckFt5CONxvGwbtOv/Vo1ZJl+6+q5 DwFi2dQ4YrA/FSDwoL74jBzAalRrd7DRBEG6WVsnTGr8yvyPJMcdv305DESZ3aQqSBy0 Tho02zgzEvz1We6QsMj+XmHxSIAHfYfQh4emuUD/Wef45ld7lNr6iB18Hs+kQLiyUsze hY/nH2qVMKvbjYbplUlKLkXqAseC/hOcxP9XOb1Zo7SK1O6ODEcUYVKl39Ni8Bw0odQF b+TA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=yqu345YiYwyJA84l7DM8rJl0SvYILsxla4fSJDuJl6c=; b=QRQi2EeGhTWnQDMKpCkvF9kWeeOZO/Su2dQx5goF9o3ed6hWVPHIyEQpnWxPDEyLpd evExutt/+zcFeivJvHnp0K0NjCLDU88QWpLGs5N9YABsyus/Wt/Ihei5LqKL5vizR3uu G6v51Q8cw/FGkvraqduZLpRB+iiEqyp53i4qaDhO10CwBffnWuq45l/0p1ECKZ9xLTIq C+vkyMd0TSYmOqboiRm8LhqIMP1KnqNiBiLWvEPZCcSljHl7KkilxEDzVkFIJ1tkBpdb Lt+KEiR+sTjtoUME89FzsDhbZ8+hYxWFx3YsxhvOJrbeM7tOhDeMhAUTDXSqWRqt+LrH oBdg== X-Gm-Message-State: AIkVDXJVfr5STET4M9i2G6rBVmtyjIYVI93/2I2WlBi3KlNT9Wzcu7BEiExBTYtdzs+Yog== X-Received: by 10.46.14.10 with SMTP id 10mr24737570ljo.58.1483543608075; Wed, 04 Jan 2017 07:26:48 -0800 (PST) Received: from [192.168.32.185] ([84.15.190.253]) by smtp.gmail.com with ESMTPSA id 26sm17573627ljo.24.2017.01.04.07.26.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 07:26:47 -0800 (PST) To: Benoit Claise , The IESG References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> From: Ignas Bagdonas Message-ID: <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> Date: Wed, 4 Jan 2017 15:26:43 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, rick.casarez@gmail.com, idr-chairs@ietf.org Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 15:26:52 -0000 Hi Benoit, Thank you for reviewing. Global Administrator field is a 4 octet integer that is used to carry AS number but it is not mandatory to interpret it as an AS number only (while a typical use case is for carrying AS number) - two peers can agree on any value that has meaning between those peers. Representation on the wire is in network byte order, and 2 byte AS number will get naturally padded with two zero bytes in front. Virtually all deployments today are AS4 capable and use AS4 encoding even for AS number values that fit into 16 bit value range therefore AS number is a 4 octet entity already. The topics of 2 byte padding and any integer value in global administrator field have been discussed in the WG. Ignas On 04/01/2017 14:52, Benoit Claise wrote: > Benoit Claise has entered the following ballot position for > draft-ietf-idr-large-community-11: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > I see from the abstract: "The attribute is suitable for use with > four-octet ASNs." > I also see this text, which doesn't mention four-octet ASNs > > The Global Administrator field is intended to allow different > Autonomous Systems to define BGP Large Communities without > collision. > This field SHOULD be an Autonomous System Number (ASN), in which > case > the Local Data Parts are to be interpreted as defined by the owner > of > the ASN. The use of Reserved ASNs (0 [RFC7607], 65535 and > 4294967295 > [RFC7300]) is NOT RECOMMENDED. > > What if the ASN is two bytes, we use padding? How? > Even if we would say: "This field SHOULD be an four-octet Autonomous > System Number (ASN)", it doesn't preclude inserting a two-octet ASN in > the Global Administrator field. > Isn't it better to specify how? > > >From RFC 6793: > > Currently assigned two-octet AS numbers are converted into > four-octet > AS numbers by setting the two high-order octets of the four-octet > field to zero. Such a four-octet AS number is said to be mappable > to > a two-octet AS number. > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thanks John for an excellent shepherd writeup. > > From nobody Wed Jan 4 07:30:06 2017 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 89B01129594; Wed, 4 Jan 2017 07:29:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 biosfYQqn_ss; Wed, 4 Jan 2017 07:29:56 -0800 (PST) Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BEEC129592; Wed, 4 Jan 2017 07:29:56 -0800 (PST) X-Envelope-To: idr@ietf.org Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v04FTld1074958 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2017 15:29:47 GMT (envelope-from nick@foobar.org) X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local Message-ID: <586D14EA.5000706@foobar.org> Date: Wed, 04 Jan 2017 15:29:46 +0000 From: Nick Hilliard User-Agent: Postbox 5.0.9 (Macintosh/20161202) MIME-Version: 1.0 To: Benoit Claise References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> In-Reply-To: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.2.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: Cc: idr@ietf.org, idr-chairs@ietf.org, rick.casarez@gmail.com, draft-ietf-idr-large-community@ietf.org, The IESG Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 15:29:57 -0000 Hi Benoit, thanks for your comments. This issue was brought up on idr@ on a couple of occasions. We deliberately didn't include text on the issue for several reasons, one of them being the text in rfc6793 that you noted below; two others were listed here: > https://www.ietf.org/mail-archive/web/idr/current/msg16458.html With regard to implementation, there have been no queries raised by any code authors about this part of the spec, and we haven't come across any reports about incompatibilities between any of the existing implementations. If there had been any ambiguity here, it would have been specified explicitly, but there isn't. Nick Benoit Claise wrote: > I see from the abstract: "The attribute is suitable for use with > four-octet ASNs." > I also see this text, which doesn't mention four-octet ASNs > > The Global Administrator field is intended to allow different > Autonomous Systems to define BGP Large Communities without > collision. This field SHOULD be an Autonomous System Number (ASN), in > which case the Local Data Parts are to be interpreted as defined by > the owner of the ASN. The use of Reserved ASNs (0 [RFC7607], 65535 > and 4294967295 [RFC7300]) is NOT RECOMMENDED. > > What if the ASN is two bytes, we use padding? How? > Even if we would say: "This field SHOULD be an four-octet Autonomous > System Number (ASN)", it doesn't preclude inserting a two-octet ASN in > the Global Administrator field. > Isn't it better to specify how? > >>From RFC 6793: > > Currently assigned two-octet AS numbers are converted into four-octet > AS numbers by setting the two high-order octets of the four-octet > field to zero. Such a four-octet AS number is said to be mappable to > a two-octet AS number. From nobody Wed Jan 4 07:39:51 2017 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 4F1651295AA; Wed, 4 Jan 2017 07:39:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.622 X-Spam-Level: X-Spam-Status: No, score=-17.622 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, 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 gudUc-OhZVdP; Wed, 4 Jan 2017 07:39:49 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 030DC129593; Wed, 4 Jan 2017 07:39:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3419; q=dns/txt; s=iport; t=1483544388; x=1484753988; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=ZuWSYxHF/TMjLO99r0va7s1sTp26PWUY8Tze2qli88Y=; b=mNIHraBG5gEg7104GC5hhehzEKhdc5rCXNwFCp5P3dPhQeBRNykyWsyW +ppf/b3I9x5YSS0p4bEKQIXt2WG9n7YDOWzft7cV2HJtD0sOiJ+1Jve4g biFG1yutAV4VCheNK8eIhzTOxaYmUgSt5I4OxZQY0ZVnEA8Vsjk1CCKQG w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AmAQDDFm1Y/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzgBAQEBAX4vXY1XcpNTkxOCD4IIKoV4AoITFAECAQEBAQEBAWM?= =?us-ascii?q?ohGkBBSMVQRALDgoCAiYCAlcGAQwIAQEQiFwOry6CJYoxAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBGAWBC4U6ggKCX4QYEQGDIYJeBYhuBZIWhlaDEodZgXaFCIMnhjS?= =?us-ascii?q?KSod2HzhoIBYNhBICAxwYgUc9NAGGA4IuAQEB?= X-IronPort-AV: E=Sophos;i="5.33,459,1477958400"; d="scan'208";a="691058695" Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jan 2017 15:39:26 +0000 Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v04FdPUg030284; Wed, 4 Jan 2017 15:39:26 GMT To: Ignas Bagdonas , The IESG References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> From: Benoit Claise Message-ID: Date: Wed, 4 Jan 2017 16:39:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, rick.casarez@gmail.com, idr-chairs@ietf.org Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 15:39:50 -0000 Ignas, > Hi Benoit, > > Thank you for reviewing. > > Global Administrator field is a 4 octet integer that is used to carry > AS number but it is not mandatory to interpret it as an AS number only > (while a typical use case is for carrying AS number) - two peers can > agree on any value that has meaning between those peers. > Representation on the wire is in network byte order, and 2 byte AS > number will get naturally padded with two zero bytes in front. > Virtually all deployments today are AS4 capable and use AS4 encoding > even for AS number values that fit into 16 bit value range therefore > AS number is a 4 octet entity already. Thanks Ignas. Then this sentence in the abstract "The attribute is suitable for use with four-octet ASNs." is misleading, right? At least to me. The attribute is suitable for four-octets ASNs and two-octets ASNs encoded in four-octets. This would be more in line with "This field SHOULD be an Autonomous System Number (ASN)" later on. Regards, B. > > The topics of 2 byte padding and any integer value in global > administrator field have been discussed in the WG. > > Ignas > > > > On 04/01/2017 14:52, Benoit Claise wrote: >> Benoit Claise has entered the following ballot position for >> draft-ietf-idr-large-community-11: Discuss >> >> When responding, please keep the subject line intact and reply to all >> email addresses included in the To and CC lines. (Feel free to cut this >> introductory paragraph, however.) >> >> >> Please refer to >> https://www.ietf.org/iesg/statement/discuss-criteria.html >> for more information about IESG DISCUSS and COMMENT positions. >> >> >> The document, along with other ballot positions, can be found here: >> https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ >> >> >> >> ---------------------------------------------------------------------- >> DISCUSS: >> ---------------------------------------------------------------------- >> >> I see from the abstract: "The attribute is suitable for use with >> four-octet ASNs." >> I also see this text, which doesn't mention four-octet ASNs >> >> The Global Administrator field is intended to allow different >> Autonomous Systems to define BGP Large Communities without >> collision. >> This field SHOULD be an Autonomous System Number (ASN), in which >> case >> the Local Data Parts are to be interpreted as defined by the owner >> of >> the ASN. The use of Reserved ASNs (0 [RFC7607], 65535 and >> 4294967295 >> [RFC7300]) is NOT RECOMMENDED. >> >> What if the ASN is two bytes, we use padding? How? >> Even if we would say: "This field SHOULD be an four-octet Autonomous >> System Number (ASN)", it doesn't preclude inserting a two-octet ASN in >> the Global Administrator field. >> Isn't it better to specify how? >> >> >From RFC 6793: >> >> Currently assigned two-octet AS numbers are converted into >> four-octet >> AS numbers by setting the two high-order octets of the four-octet >> field to zero. Such a four-octet AS number is said to be mappable >> to >> a two-octet AS number. >> >> >> ---------------------------------------------------------------------- >> COMMENT: >> ---------------------------------------------------------------------- >> >> Thanks John for an excellent shepherd writeup. >> >> > > . > From nobody Wed Jan 4 07:46:57 2017 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 80415129463; Wed, 4 Jan 2017 07:46:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.302 X-Spam-Level: X-Spam-Status: No, score=-7.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 u5-3VpMPctAr; Wed, 4 Jan 2017 07:46:52 -0800 (PST) Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 733F41295DB; Wed, 4 Jan 2017 07:46:39 -0800 (PST) Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 54C35876D8; Wed, 4 Jan 2017 15:46:39 +0000 (UTC) Date: Wed, 4 Jan 2017 15:46:39 +0000 From: heasley To: Benoit Claise Message-ID: <20170104154639.GG21501@shrubbery.net> References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc X-note: live free, or die! X-homer: i just want to have a beer while i am caring. X-Claimation: an engineer needs a manager like a fish needs a bicycle X-reality: only YOU can put an end to the embarrassment that is Tom Cruise User-Agent: Mutt/1.6.1 (2016-04-27) Archived-At: Cc: idr@ietf.org, idr-chairs@ietf.org, rick.casarez@gmail.com, draft-ietf-idr-large-community@ietf.org, The IESG Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 15:46:53 -0000 Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise: > Ignas, > > Hi Benoit, > > > > Thank you for reviewing. > > > > Global Administrator field is a 4 octet integer that is used to carry > > AS number but it is not mandatory to interpret it as an AS number only > > (while a typical use case is for carrying AS number) - two peers can > > agree on any value that has meaning between those peers. > > Representation on the wire is in network byte order, and 2 byte AS > > number will get naturally padded with two zero bytes in front. > > Virtually all deployments today are AS4 capable and use AS4 encoding > > even for AS number values that fit into 16 bit value range therefore > > AS number is a 4 octet entity already. > Thanks Ignas. > Then this sentence in the abstract "The attribute is suitable for use > with four-octet ASNs." is misleading, right? At least to me. > The attribute is suitable for four-octets ASNs and two-octets ASNs > encoded in four-octets. > This would be more in line with "This field SHOULD be an Autonomous > System Number (ASN)" later on. No, because it is in reference to rfc1997, which is not usable with AS4. From nobody Wed Jan 4 08:13:47 2017 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 DD017129613; Wed, 4 Jan 2017 08:13:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.035 X-Spam-Level: X-Spam-Status: No, score=-5.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.1, SPF_SOFTFAIL=0.665] autolearn=ham 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 NMBcJ6M9BC_6; Wed, 4 Jan 2017 08:13:40 -0800 (PST) Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 DD8D312960D; Wed, 4 Jan 2017 08:13:40 -0800 (PST) Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOoC1-0008gY-Ey (job@us.ntt.net); Wed, 04 Jan 2017 16:13:38 +0000 Date: Wed, 4 Jan 2017 18:13:29 +0200 From: Job Snijders To: Benoit Claise Message-ID: <20170104161329.GD53926@Vurt.local> References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.7.2 (2016-11-26) Archived-At: Cc: idr@ietf.org, idr-chairs@ietf.org, The IESG , draft-ietf-idr-large-community@ietf.org, rick.casarez@gmail.com Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 16:13:42 -0000 Hi Benoit, On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote: > > Global Administrator field is a 4 octet integer that is used to carry AS > > number but it is not mandatory to interpret it as an AS number only > > (while a typical use case is for carrying AS number) - two peers can > > agree on any value that has meaning between those peers. Representation > > on the wire is in network byte order, and 2 byte AS number will get > > naturally padded with two zero bytes in front. Virtually all deployments > > today are AS4 capable and use AS4 encoding even for AS number values > > that fit into 16 bit value range therefore AS number is a 4 octet entity > > already. > > Then this sentence in the abstract "The attribute is suitable for use > with four-octet ASNs." is misleading, right? At least to me. The > attribute is suitable for four-octets ASNs and two-octets ASNs encoded > in four-octets. This would be more in line with "This field SHOULD be > an Autonomous System Number (ASN)" later on. I am under the impression that nowadays the IETF community considers all ASNs to be four-octet ASNs, however, some of those ASNs can be encoded as a two octet value. The Large Communities specification is suitable for usage in Autonomous Systems from all walks of life, where as rfc1997 communities are unsuitable for all ASNs, specifically those ASNs which cannot be encoded as two-octet values. Kind regards, Job From nobody Wed Jan 4 10:43:35 2017 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 38F921296A5; Wed, 4 Jan 2017 10:43:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.622 X-Spam-Level: X-Spam-Status: No, score=-17.622 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, 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 Xzc3iOV-Ie2A; Wed, 4 Jan 2017 10:43:28 -0800 (PST) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 940201296D1; Wed, 4 Jan 2017 10:43:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1656; q=dns/txt; s=iport; t=1483555408; x=1484765008; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=h5WHe/WMnv5mvAda6X8NPmi94yLTd2U7x1s9x2o8/II=; b=AJMMsttVEe7ONnuIQGLAmSkDApBwD/XnvaC3zy6GTEqvRUWSps4EdS1l XJXD4yaqUQaL62cbqfZhfz5/dJ9JFJtm/u26IatSAotbEkjWU1NKN+qFp ZCSSJQDPUem3HfO/a8fQksVy3FN4t+8b2ZZflEIHp+k5cdxm55Jyx5Nbq M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CVAgAdQW1Y/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzgBAQEBAYEtjyaTVZMTgg+CCIYiAoIXEgECAQEBAQEBAWMohGk?= =?us-ascii?q?BBThBEAsYLlcGDQgBARAFiFeyBYorAQEBAQEBAQEBAQEBAQEBAQEhhkWCAgiCV?= =?us-ascii?q?4opAQSIc5IWiWiHWYolhjSKSod2JQExgQgWDYQSAh8YgUc9iGYBAQE?= X-IronPort-AV: E=Sophos;i="5.33,317,1477958400"; d="scan'208";a="651342037" Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jan 2017 18:43:23 +0000 Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v04IhMOl004597; Wed, 4 Jan 2017 18:43:22 GMT To: Job Snijders References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> <20170104161329.GD53926@Vurt.local> From: Benoit Claise Message-ID: <503f746a-7530-388f-4ed7-6868e53b7ff4@cisco.com> Date: Wed, 4 Jan 2017 19:43:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170104161329.GD53926@Vurt.local> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: idr@ietf.org, idr-chairs@ietf.org, The IESG , draft-ietf-idr-large-community@ietf.org, rick.casarez@gmail.com Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:43:30 -0000 Hi Job, So basically, you're telling me: "The attribute is suitable for use with ASNs.", right? Is this what needs to be in the abstract? Regards, B. > Hi Benoit, > > On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote: >>> Global Administrator field is a 4 octet integer that is used to carry AS >>> number but it is not mandatory to interpret it as an AS number only >>> (while a typical use case is for carrying AS number) - two peers can >>> agree on any value that has meaning between those peers. Representation >>> on the wire is in network byte order, and 2 byte AS number will get >>> naturally padded with two zero bytes in front. Virtually all deployments >>> today are AS4 capable and use AS4 encoding even for AS number values >>> that fit into 16 bit value range therefore AS number is a 4 octet entity >>> already. >> Then this sentence in the abstract "The attribute is suitable for use >> with four-octet ASNs." is misleading, right? At least to me. The >> attribute is suitable for four-octets ASNs and two-octets ASNs encoded >> in four-octets. This would be more in line with "This field SHOULD be >> an Autonomous System Number (ASN)" later on. > I am under the impression that nowadays the IETF community considers all > ASNs to be four-octet ASNs, however, some of those ASNs can be encoded > as a two octet value. The Large Communities specification is suitable > for usage in Autonomous Systems from all walks of life, where as rfc1997 > communities are unsuitable for all ASNs, specifically those ASNs which > cannot be encoded as two-octet values. > > Kind regards, > > Job > . > From nobody Wed Jan 4 11:13:46 2017 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 0C0A3129A6E for ; Wed, 4 Jan 2017 11:13:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 Gz3Mgqbj5gb2 for ; Wed, 4 Jan 2017 11:13:41 -0800 (PST) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5930129A70 for ; Wed, 4 Jan 2017 11:13:38 -0800 (PST) Received: by mail-wm0-x22a.google.com with SMTP id k184so269371318wme.1 for ; Wed, 04 Jan 2017 11:13:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=mB7eZvUWgTMgds09vlAUFa5flWUvQIqLJydnouCeSIU=; b=pVogTfkXuov4KZ186vXD71rpVrc/cxXlIsw7H0yGzcn0Oje6b+kOH54RWki4eg2E6e gkiS4JhzvgXraeDgpAlK2koVszLdie5Plxrf8o8DMtwsZay2CNursB68EoTdtG1M4A0c vmSIuhfQ040fC1yEH/8Wz34N2s+5/wwosCKsDud5OAIN6i1aSfZ4R08JCq2qRS91V6Z1 YTgooZfizuMrRuuOtsJjXra9g/ZxB7cPStiby9WFFAdBQI0Zey2rKdSTQ7rXGJdPh0gq 0BKZci/jF5Zkn2NXqBiC4zsANZp+3pMu7gYCCU6utRcH7HNHfrp73VUm6CMLgzT8wfCw PdKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=mB7eZvUWgTMgds09vlAUFa5flWUvQIqLJydnouCeSIU=; b=BJsqrQP4jl5jQhvPQqpA/ohcXY97n7zG0fhM2jusKDSM7MoK9vMjGUfDuHSDUg+EOd 0V3GJSnbqz4r+bkO3gNN7Ot1fFrGXekpq44lA3foFBppq55esVMto9YJ6HLj89EPMPLD x24AoOBO9SpsjiPHstolxAdimT3aOTFyGSabhKJuuv+TLQERoKONAMorcwJAdw+3h1hL gb96Ch+To4m5JtQ4WNW7MSWyWZMbbNSlH1NFRhCVz0mKbd7h7ZjrfpjFtgTk5F72Un0T IyflLd6XZDKqWQ04VUYGAvURmZILTy/qryST7UqsJt/Mm67FKIUIozFs8k1tnGYWRHXm SWVw== X-Gm-Message-State: AIkVDXJOXIvAmr/IQjkfjQGJSPFJhrfGqRJXE6TZ0v6xVsrSrAW4mnkgAw1Si2h5zsMePQ== X-Received: by 10.28.138.135 with SMTP id m129mr55668901wmd.36.1483557216973; Wed, 04 Jan 2017 11:13:36 -0800 (PST) Received: from [100.119.50.64] ([188.207.113.9]) by smtp.gmail.com with ESMTPSA id wp2sm61902127wjc.35.2017.01.04.11.13.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 11:13:36 -0800 (PST) Date: Wed, 4 Jan 2017 21:13:08 +0200 From: Job Snijders To: Job Snijders , Benoit Claise Message-ID: <41368b03-eaa0-453e-8fd0-7e31a7650d0d@Spark> In-Reply-To: <503f746a-7530-388f-4ed7-6868e53b7ff4@cisco.com> References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> <20170104161329.GD53926@Vurt.local> <503f746a-7530-388f-4ed7-6868e53b7ff4@cisco.com> X-Readdle-Message-ID: 41368b03-eaa0-453e-8fd0-7e31a7650d0d@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="586d4956_6b8b4567_4e8" Archived-At: Cc: idr@ietf.org, rick.casarez@gmail.com, draft-ietf-idr-large-community@ietf.org, The IESG , idr-chairs@ietf.org Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 19:13:43 -0000 --586d4956_6b8b4567_4e8 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Yes, absolutely! I believe it is helpful because many people are looking for a solution like Large Communities provides (with their favorite search engine). This sentence is a hat tip to a 10+ year problem. Large Communities addresses a very urgent problem from the operator community, specifically because it can be used by ASNs which fit only in four-octet values. We are scraping the bottom of the barrel, IANA has run out of two-octet ASNs. Also at the RIR level, the end is also in sight: There are only a few thousand left. We cannot sustain the growth of the internet without a tool like Large Communities. Large Communities specifically addresses an issue which prevents four-octets from being used in a similar way to how RFC1997 is used. Btw, I am not clear on how the topic at hand relates to the actual content of the DISCUSS. Can you update the discuss? Or how should I view the feedback? Kind regards, Job On 4 Jan 2017, 20:43 +0200, Benoit Claise , wrote: > Hi Job, > > So basically, you're telling me: "The attribute is suitable for use with > ASNs.", right? > Is this what needs to be in the abstract? > > Regards, B. > > Hi Benoit, > > > > On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote: > > > > Global Administrator field is a 4 octet integer that is used to carry AS > > > > number but it is not mandatory to interpret it as an AS number only > > > > (while a typical use case is for carrying AS number) - two peers can > > > > agree on any value that has meaning between those peers. Representation > > > > on the wire is in network byte order, and 2 byte AS number will get > > > > naturally padded with two zero bytes in front. Virtually all deployments > > > > today are AS4 capable and use AS4 encoding even for AS number values > > > > that fit into 16 bit value range therefore AS number is a 4 octet entity > > > > already. > > > Then this sentence in the abstract "The attribute is suitable for use > > > with four-octet ASNs." is misleading, right? At least to me. The > > > attribute is suitable for four-octets ASNs and two-octets ASNs encoded > > > in four-octets. This would be more in line with "This field SHOULD be > > > an Autonomous System Number (ASN)" later on. > > I am under the impression that nowadays the IETF community considers all > > ASNs to be four-octet ASNs, however, some of those ASNs can be encoded > > as a two octet value. The Large Communities specification is suitable > > for usage in Autonomous Systems from all walks of life, where as rfc1997 > > communities are unsuitable for all ASNs, specifically those ASNs which > > cannot be encoded as two-octet values. > > > > Kind regards, > > > > Job > > . > > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr --586d4956_6b8b4567_4e8 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Yes, absolutely=21

I believe it is helpful because many people are looking for a solution li= ke Large Communities provides (with their favorite search engine). This s= entence is a hat tip to a 10+ year problem.

Large Communities addresses a very urgent problem from the operator commu= nity, specifically because it can be used by ASNs which fit only in four-= octet values.

We are scraping the bottom of the barrel, IANA has run out of two-octet A= SNs. Also at the RIR level, the end is also in sight: There are only a fe= w thousand left. We cannot sustain the growth of the internet without a t= ool like Large Communities. Large Communities specifically addresses an i= ssue which prevents four-octets from being used in a similar way to how R= =46C1997 is used.

Btw, I am not clear on how the topic at hand relates to the actual conten= t of the DISCUSS. Can you update the discuss=3F Or how should I view the = feedback=3F

Kind regards,

Job


On 4 Jan 2017, 20:43 +0200, Benoit Claise <bclaise=40cisco.com>, wr= ote:
Hi Job,

So basically, you're telling me: =22The attribute is suitable for use wit= h
ASNs.=22, right=3F
Is this what needs to be in the abstract=3F

Regards, B.
Hi Benoit,

On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote:
Global Administrator field is a 4 octet int= eger that is used to carry AS
number but it is not mandatory to interpret it as an AS number only
= (while a typical use case is for carrying AS number) - two peers can
agree on any value that has meaning between those peers. Representation on the wire is in network byte order, and 2 byte AS number will get
= naturally padded with two zero bytes in front. Virtually all deployments<= br /> today are AS4 capable and use AS4 encoding even for AS number values
that fit into 16 bit value range therefore AS number is a 4 octet entity<= br /> already.
Then this sentence in the abstract =22The attribute is suitable for use with four-octet ASNs.=22 is misleading, right=3F At least to me. The
attribute is suitable for four-octets ASNs and two-octets ASNs encoded in four-octets. This would be more in line with =22This field SHOULD be an Autonomous System Number (ASN)=22 later on.
I am under the impression that nowadays the IET=46 community considers al= l
ASNs to be four-octet ASNs, however, some of those ASNs can be encoded as a two octet value. The Large Communities specification is suitable
for usage in Autonomous Systems from all walks of life, where as rfc1997<= br /> communities are unsuitable for all ASNs, specifically those ASNs which cannot be encoded as two-octet values.

Kind regards,

Job
.


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Idr mailing list
Idr=40ietf.org
https://www.ietf.org/mailman/listinfo/idr
--586d4956_6b8b4567_4e8-- From nobody Wed Jan 4 11:51:24 2017 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 8B215129415; Wed, 4 Jan 2017 11:51:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.922 X-Spam-Level: X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=junipernetworks.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 Cv-bJshvdeLY; Wed, 4 Jan 2017 11:51:17 -0800 (PST) Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0112.outbound.protection.outlook.com [104.47.42.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 971D21293FE; Wed, 4 Jan 2017 11:51:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=FAu2eWkVFtMEFrGTioOrIp8Aaaq6UPVsytKEysv6iyc=; b=hLg/c+OLz5R3sTJbNmfLJ51EIyryMAgLk4BKllPW33LSvxEnNDKdfFBE9BApMutslwa4dkzic3dnhmM4JHmWS0c+8V0a/VPqttTVhqSNvzySiP86kruFV2zKsf1rF9U1YRMRIO8roRJGsQZz21WIlo7A6GnYm1WwqRC0y072A78= Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=jgs@juniper.net; Received: from [172.29.36.40] (66.129.241.12) by BN3PR05MB2499.namprd05.prod.outlook.com (10.167.3.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.829.4; Wed, 4 Jan 2017 19:51:10 +0000 Content-Type: text/plain; charset="windows-1252" MIME-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: "John G. Scudder" In-Reply-To: <503f746a-7530-388f-4ed7-6868e53b7ff4@cisco.com> Date: Wed, 4 Jan 2017 14:51:06 -0500 Content-Transfer-Encoding: quoted-printable Message-ID: <5ED073F1-7EB7-438F-81DE-7287D48831EB@juniper.net> References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> <20170104161329.GD53926@Vurt.local> <503f746a-7530-388f-4ed7-6868e53b7ff4@cisco.com> To: Benoit Claise X-Mailer: Apple Mail (2.3124) X-Originating-IP: [66.129.241.12] X-ClientProxiedBy: SN1PR11CA0010.namprd11.prod.outlook.com (10.164.10.20) To BN3PR05MB2499.namprd05.prod.outlook.com (10.167.3.134) X-MS-Office365-Filtering-Correlation-Id: 3f54d291-bb20-438b-6fd9-08d434db090f X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN3PR05MB2499; X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2499; 3:3RiJhe0T/cxi/WFCUJfziS22d6oLyh1dl8oCXhRXczf2moT8jfgv76l11aOGRuoTqP+QKwhD8vCOqw3QDjsW5QLLqBgnmSXuhxQj3aI5VwtECbQkcWhfiFuIOqz37imRiJT6iOLvkRA8QnXPbXcAiPqkqhFRf+5D4R2DqEF72ox4LquPPEIrQ3m993auXXFQt/SsVUoj7eqqyanuytVO5WLAVEsuQlvdYuF+BjAGYlnei3DFrLcNWc7ZPlurMxu9ghxEO35kXHVq0YJm0wf7YA== X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2499; 25:yDYK457O7fypaL8eX06osoMhXaP8V5urSCuOIHM24XfsruZcM+Bss88jg6qw1+t0sevngiWZeW7QOy+5GFld7wu18K3qe5WnJjTy4cIbN/SDjD1JlR+1c0yWuUcVbFUYtZdNkesBF+AC+bXb3Cnh+HaxiR+hkLkv7JV30QsYQYFcDK8j/ZqZ87w+uQDKQ4Dlrkgqkwp02okAF9iSzYRZmr16PvOkJNdCM54C81R0FCgC8FLYFfJRFxffcP12u6/kIUhnJvnJKcbbhmIYEUf1NTb+Yf5n7yWySvlJ00Wu00Y2o8sDdvV6VtIaJXRmgKak/2UEusnzEUp20mmcbf+byc3Y/V0ie2h3Pceu++6adCxmkJB2D3UGxeZf3Ov9TAng3g1sjpromY+YTJY4dRJXEVb5NKRJ1aPt40sqiyspsVO/SUsnYEepx7UAvIBKIXEars6SG+9nDO1DYEWI1XySmb+Wjrcy333PXG52T2kCuSaUK+dRziPav3Ov37q0CvZ0a5hYxs7gtnOsQdN3nLTixEqpVdYy8tGghCrvrX4WHgV2xl+cfs9iIyhl4DDJVVIRiXpjal26L7rADxPf6rzpSI8SvbCq22gcukUx/rjH1rD1ngBZW71tiV5R0PUJ1lXeClNSSeh63X2KBCo8sYvclwn5+J5VKLf/t7SEK626oW4zQGQ0j11XyHhKcg85mchCrxwPrKXJZuN/HwmqsepvrDLLTENODyOvw40p85YoCHd8jyxahRTfiX4IN1XnK5Ux6CmCOlj38BZBkHGfbScQww== X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2499; 31:HEhuGVAtlMtFOXA3E6ej2ysyYtHXFUVzt5Ty7yMU1icO9Nhf1SuoWnztF2NWbVO1iVoKDcH5CMsVF5Bdm/0VNTfk9djWQTZefs65+9JEegoOIaOWa+gZCxq6XF2VRvjv/KHt+HQZzj7HAY36yvhx6li3pNsBgEasMLU3dByBdTND0ObBI1tZwV0ZUb+uglO2fakxdWAoeNeS7AVDTV8ECfc5v5IwukMxj04qwkHFQyyyLBUvfwlq0sFTX/BinURv50ftl3Vwzl4trZg4jOhpejK0re1iNOPLWZ/uu28oroI=; 20:eZd606gVlM/LGpYsJFEvrM3VdNSac5zooichgcAYq9akWtDqvgeuaRutOFdt2qNZ6PF5+nXuNGWwCyROajM3Kp9cvoM33SNCFycBBigM3e2O0HPkdtATlVjwNe6SRRvg9VFFxbTRTKD+RIq2GFAkbGqb6BFSnka/bvSonGgyk4tBn+dz2U0NmDU7fzhqO76Btv1SttLxwFMjTU9mvZEl1iWZY8NG3qn3Fkz04PLV4l3O6HvmhhInJdHLBW1EsqIN2ke+XnIc5gMdb2UKORQKF1PeUV7tVK14YhnD+KAFdffgOXU9XVcFyAlPiNpDdnjceS4CRl6Wpt3hWVz9pYvdS49G2lCWfhG96T/bZWQ+2ZzhJqNE0NHjxN7pBWSfo2l9COIdztz5wYPOzfT3iBphfIHTue8MHyQY1WnkQ2so0uW5ERkZ/ZjVz3E+5umtlE75ce2y2wQcZI8I8e0JbScHalfTQLabNDs9LHfZl49QeKEEDfnJZO161Ts7oncKgXTvTJu3Gf6lQzUxWMb1BA+dGKv9mo5NzsbolP71jQp2z0wzucIs6lYKWaGtORKyP77mtq3nccfe1pCuz+4k2rCJ2GvonVtI3Rz49j4XzSy5SfQ= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(95692535739014); X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123555025)(20161123560025)(20161123564025)(20161123562025)(6072148); SRVR:BN3PR05MB2499; BCL:0; PCL:0; RULEID:; SRVR:BN3PR05MB2499; X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2499; 4:Y5KVEyaZyt4brThui1+UUPxXa1mpenbFpQ8kNt69Gt/pqqLf4tWpAIKKCM0mU3SBbez8RAtEmrGGEF0xfJIlBLDV7IjkQo7XDHJL2I74P3T0U5FPVztJdZuyMYziYunOCNXqxMsaPlgjxGupz1/u5Hqh2tpx/FEB9b5U7hhkBIdiZTLxdgw1RoAzflQKzvGLjtcPIm/2n8upKbmvMpNkWYAf4Rl4VKkidH1EOKMMrCfM9xs4RY2iSZXfqfFjulIHQj6UGre+ew0roPN4fSdHtgxwF5mbMRYvEdN3QxnCqaSXmNGiQJ1jM49xfR3EmGj1MsVoZ8XEqHk3TUez7/jQ8AHk+DQD17EZi+4Aw0u2V7yy6ATcHigtmtYdSwgJJDrbiFu+Exznip1qZMEFDKwIIfVT3sjwTlC9J6jnFBjOMYO62N4bUBDhDj1EBMwP2FlYtbkTL1KZSPNjYUL0DvR/V9EXf9/pMsIUFZibyTGrdu/bTPRNthQqngd6SCsVQYJv/QqkRrM7CVGYemf/2aIFlc/1oMgiGzE4xROpbqTgn3QtxjSFT30hLgm0Tr16ezG8t6dlYqPCQEKJM6B7pZjjnasdc5S+tQnGChVIAiBUxx8P5SYpstVtmGDgbOHVBfD9x6dmpyAwmvEVBt8XOwmzVQ== X-Forefront-PRVS: 0177904E6B X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6049001)(6009001)(7916002)(39850400002)(39860400002)(39450400003)(39840400002)(39410400002)(199003)(377454003)(189002)(24454002)(81156014)(230783001)(66066001)(3846002)(93886004)(42186005)(86362001)(83716003)(57306001)(101416001)(106356001)(33656002)(105586002)(47776003)(76176999)(50986999)(97736004)(189998001)(23746002)(50466002)(25786008)(2950100002)(2906002)(6486002)(4326007)(6916009)(6666003)(229853002)(39060400001)(38730400001)(90366009)(77096006)(6116002)(92566002)(110136003)(5660300001)(8676002)(81166006)(305945005)(54906002)(7736002)(68736007)(36756003)(82746002)(8746002)(50226002)(104396002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2499; H:[172.29.36.40]; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) X-Microsoft-Exchange-Diagnostics: =?Windows-1252?Q?1; BN3PR05MB2499; 23:WmboySAo7Til1PVudXhHxtPd/VQjD8juPGWT+?= =?Windows-1252?Q?ZTSRxFhIDT37PlAApkiSKkM5yT1Oj4Or0RQAukMqlO1zA9g+brOJBBEm?= =?Windows-1252?Q?nAMft21vN27zLGOxX64gGfRevVqfVBL1jYQBmNZHXBnRcxwqlhBLWSFd?= =?Windows-1252?Q?jq6EloFITXN2JwTdtD3N2jWSR86DUwa9EVlGQHNJm5v8hE7aGJr+LM6J?= =?Windows-1252?Q?8UKoH0k66JTWJqyCD4A+R/wbNJes2o38mWATtD6ONkN9lEiPpzqkZjGA?= =?Windows-1252?Q?5mwRDG42PHe/x+87kiEMcEYe/wuv7WFjeX53+h8w5jEnEApOl3FS3yh6?= =?Windows-1252?Q?zxs7HzawckLjGzIOS8kAJHF7PycFCMJm/wm8AR6/RppbuYIwxwnmG3sG?= =?Windows-1252?Q?+fbGjI/fZhIMioaIBSUA/He/SN4j2+uL5VypSkdyARTwQjKEFWkldEby?= =?Windows-1252?Q?7dSz/Ft2CuhQfRsRW9gmOsKXWojvKqTgHlYH9HCY+LqLhYVR5XFiRtPw?= =?Windows-1252?Q?o0gvhu1dz/sUc0G96GUVscjgaWfAjbCwajB9Rn8ZA6i/2xKK05MJ/ReS?= =?Windows-1252?Q?gmkaRHewCZlaX/pipUewsaNXQjSarTJllZlf2vT6pXWpbbGftYBi+qdK?= =?Windows-1252?Q?G6D18lTyKL8UhJ+F/WA2ZDOg0D+x/0nTwmJqMjXdIFC/mkrSliKqN1x4?= =?Windows-1252?Q?1ThV31GYT1LhXeCrsmp+1uFFSr8s6aMg9qbp4dLqDXjdzoF1MLnnY1kt?= =?Windows-1252?Q?MRJE5SQmQZ4iJDXJECuNM0kLkyafP4XNRF5wFGxTdxNW/LcZX0UgUnvu?= =?Windows-1252?Q?6CVg5Sq7+TKmVP7RnoqjXEaSsSq7j8f6EpLjuRLsNOcuZQRNY2XyUhD7?= =?Windows-1252?Q?etTvsjeYLTcxDBmMGPIZlCeA7oWd8nRyXEN8yQu97yWVBUflnRS29UFP?= =?Windows-1252?Q?oSJq3qtmNV5P4M8y+jWCGIvYZZCx0CWhNgivsJXgv8cpXS0ZPuefVZB5?= =?Windows-1252?Q?y88P2mYESa1JUGwIsicpVKfGefstzz6dwNIKzEHt1SqfDA2OeABK6Jrs?= =?Windows-1252?Q?P/Cqyvx0wM8CG0aXKLU0J4pw7W7n3Lg2Erw6/vDsbqF+xfwLNvrIZug2?= =?Windows-1252?Q?/q9pcuYmlumrSHGBs8RwdsR4pafYlNGlJ8dRWxOO8oI/K45abjm85ahU?= =?Windows-1252?Q?tx8ErdNSPOynMFKWSx2UbkHR0RSvsNYxHLAyVaMmN9a/fO6aO4TQBnmx?= =?Windows-1252?Q?ILIrYSUcfYCjII6nIkN7gCjWTgrcHD8Sy81rLHOHDNiU0h1cox3nRFSS?= =?Windows-1252?Q?YLgtl1CvRbx9W1pOim6QcgwPz3d0casSCbfT8+HU4YwEv/ClJDdSbyQv?= =?Windows-1252?Q?gdCp3Aw0cAbBo4YlAkBZRdWIScG/XOq8MWJgb6+6iRsFSnLSaDohQWEK?= =?Windows-1252?Q?v6XddVgLT4RdTfCd8c8R6ov2X9H5g7kE+g6+wsTZ9TLOQnxnSWIsVS5W?= =?Windows-1252?Q?ZPEyVaVAKLA/liMWSTrt3oGYJfoUYorZqw+910J45W5swR4zeG9S77dC?= =?Windows-1252?Q?aNKUgv6rT3N/P9KdWSp6rGbUIkbmN4/zW0F?= X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2499; 6:042iZ1oPAz4M/GjGl0cChVHWjB+MIYOPcq6HWGU52wSeaLJAYjONeosBE/cz5DKMGBu6sKxs9qXGqGUJGUYcIOj/C2TzrnS4gfwk1G1tXjnH2GwVnGq0IobcpP0Q6qyD3+d795YGEEdVwk59v4d+AapisJ6Uz7AEumlOEc9QAh2u0qhehYktrfmY/FuifaHwX3YSUMWF/QPyPdLxwPUpDGDAaWFeX6Rhz7JBBOKLU3MDim0LjYWEIK8sOTOyFIpwLDqdrwhLVG1CmagsYiliXJlnexqKr8ORyJXarGothhEdg1V9Sl8nu+R0DdsP48ZxOWEypnLEGyd83b6Q1Q/MOftaSr3gYq2nOehtzv86EeJRkSaAOyg96u9Nq1fvQcTT3bk1PkZ024koekoo6miUJJCdsX8LBF4IokNgKEdB7XMZNLwIgvMpYDr3zyDp3sD0z8JGBI2rBw+oJkuhz8e12w==; 5:q1sePvG32kU98HG3Nug2cKyNhXuzlySGP1xehm2/VOr0HFhwGI2DcnZnTbktcXyoLLUVtcMVHYkOn/dAmUbl+x+vYYXsQdUIFmd5P1cSjo/iBmGYd3QLqmbhhhhJGRjMoxxZWPfV633sK7/9z1sFNpKRTpRe5Kl7n0dfOjmiJxo=; 24:CgemnTBu6X32n0eTiuD3N8qDkL3RC91RLtUQ4/QWfAH1CcDZgK20yVXiILgPGq9q7tKAL3D2ALgjzVJJY5TNcI6uRpIaKqbZj+cEzT+vZnM= SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2499; 7:8oB3yABwhFR2py6WzoKSHM1hHsGbaQ1pRNnMrIwvDJ34S5WIMUmHzIsiGaRpTfE3/iS0PJ9Sef0fUSbYSIW7HErYH9eQUVkSditGxbrdZT0mIh5NFMOipNpAjs24w2MFHdZzW0R3sbaVUz5vVWG/GaWCNHCIRwKwpdPIG5uoBm8i7kOfrk2NXN6Oyw47A8FFA3bLzyEzPUUVQ3VatNASjkhluN1OS7SKpq+wuiiZEpD46j2jUZ1J0yS+KmWZnEM/a7+6qJaPyhMkdVdtYQUUdRLqDFpgv9rMvxs9sQe++YhLZAdzd4SR4dY1CqAMskbDV6QArlSxvaCUTTYvNDDVADXxJwqy9lM4kbgh6bZGpGMtZViLhNQ4QxNexR24OHnPFG5M7sJ7mQ5ULKGmAmkHgkZFR9d7CMjHWHbmEYmCT8QahPjWeIwp09crsE5olOvUs0DCQ5mlhKd/fpazQFS9jA== X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Jan 2017 19:51:10.7100 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2499 Archived-At: Cc: idr@ietf.org, idr-chairs@ietf.org, The IESG , draft-ietf-idr-large-community@ietf.org, rick.casarez@gmail.com Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 19:51:19 -0000 Benoit, I think the wording is accurate as written, but I see your point. I = think your suggested wording is terse to a fault since it abandons the = important "this will work with your four-byte ASN" information. IMO a = change is not strictly needed, but if one is desired how about something = like this? OLD: The attribute is suitable for use with four-octet Autonomous System Numbers NEW: The attribute is suitable for use with all Autonomous System Numbers = including four-octet Autonomous System Numbers Or a lawyer would probably say :-) The attribute is suitable for use with, inter alia, four-octet Autonomous System Numbers Regards, =97John > On Jan 4, 2017, at 1:43 PM, Benoit Claise wrote: >=20 > Hi Job, >=20 > So basically, you're telling me: "The attribute is suitable for use = with ASNs.", right? > Is this what needs to be in the abstract? >=20 > Regards, B. >> Hi Benoit, >>=20 >> On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote: >>>> Global Administrator field is a 4 octet integer that is used to = carry AS >>>> number but it is not mandatory to interpret it as an AS number only >>>> (while a typical use case is for carrying AS number) - two peers = can >>>> agree on any value that has meaning between those peers. = Representation >>>> on the wire is in network byte order, and 2 byte AS number will get >>>> naturally padded with two zero bytes in front. Virtually all = deployments >>>> today are AS4 capable and use AS4 encoding even for AS number = values >>>> that fit into 16 bit value range therefore AS number is a 4 octet = entity >>>> already. >>> Then this sentence in the abstract "The attribute is suitable for = use >>> with four-octet ASNs." is misleading, right? At least to me. The >>> attribute is suitable for four-octets ASNs and two-octets ASNs = encoded >>> in four-octets. This would be more in line with "This field SHOULD = be >>> an Autonomous System Number (ASN)" later on. >> I am under the impression that nowadays the IETF community considers = all >> ASNs to be four-octet ASNs, however, some of those ASNs can be = encoded >> as a two octet value. The Large Communities specification is suitable >> for usage in Autonomous Systems from all walks of life, where as = rfc1997 >> communities are unsuitable for all ASNs, specifically those ASNs = which >> cannot be encoded as two-octet values. >>=20 >> Kind regards, >>=20 >> Job >> . >>=20 >=20 From nobody Wed Jan 4 12:21:09 2017 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 9557D129AAA; Wed, 4 Jan 2017 12:21:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.622 X-Spam-Level: X-Spam-Status: No, score=-17.622 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=-3.1, SPF_HELO_PASS=-0.001, 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 9Lr1hFXI5v1P; Wed, 4 Jan 2017 12:21:03 -0800 (PST) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B40AF129A88; Wed, 4 Jan 2017 12:21:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3325; q=dns/txt; s=iport; t=1483561262; x=1484770862; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=0xDB3/IKkpXwx7HyGMpERT24wKRVQbYmwlDCJIDMnv0=; b=Gv5uC2POfx/BNDN6ARRs88AM8DJ8Rlm0CcBBxOE8x7CVVlwKCa9yvk/p yYm0agq7TSE8GYELm3mccIaZNuIJzF1WvH9W0XPjP4T3ijWCAXUwk6gJb HgQqR11op6NjNiuXPj1xdekE5MGQ3kirkDMgrt/I/yWzle9rwFXkgc7Pz Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAQDAWG1Y/4wNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzgBAQEBAR+BaweNUJRIh36LFYIPggiGIgKBVj8UAQIBAQEBAQE?= =?us-ascii?q?BYyiEaAEBAQQ6PwwEAgEIEQQBAQEeCQchERQJCAIEAQ0FCAwFiDwDGLIVh0ENg?= =?us-ascii?q?l0BAQEBAQEBAQEBAQEBAQEBAQEBAQEdhkWEYYJOh1sFiHORXjgBiWeDX4NxkGK?= =?us-ascii?q?JdYhKAR84gSuEEgIfGIFGcoclAYEMAQEB?= X-IronPort-AV: E=Sophos;i="5.33,317,1477958400"; d="scan'208";a="193294979" Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Jan 2017 20:20:48 +0000 Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v04KKmCS004168 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 4 Jan 2017 20:20:48 GMT Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 4 Jan 2017 14:20:47 -0600 Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Wed, 4 Jan 2017 14:20:47 -0600 From: "Jakob Heitz (jheitz)" To: "John G. Scudder" , "Benoit Claise (bclaise)" Thread-Topic: Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) Thread-Index: AQHSZqWFUmGq1C8fDk+RJ+bRj4wJEaEpDCSAgAAS7AD//6KlIA== Date: Wed, 4 Jan 2017 20:20:47 +0000 Message-ID: References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> <20170104161329.GD53926@Vurt.local> <503f746a-7530-388f-4ed7-6868e53b7ff4@cisco.com> <5ED073F1-7EB7-438F-81DE-7287D48831EB@juniper.net> In-Reply-To: <5ED073F1-7EB7-438F-81DE-7287D48831EB@juniper.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [128.107.151.21] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "idr@ietf.org" , "idr-chairs@ietf.org" , The IESG , "draft-ietf-idr-large-community@ietf.org" , "rick.casarez@gmail.com" Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 20:21:04 -0000 There is no need to change the text. The attribute is in fact suitable for use with four-octet ASNs. Since all ASNs can be represented in 4 octets, there is no problem. Thanks, Jakob. > -----Original Message----- > From: John G. Scudder [mailto:jgs@juniper.net] > Sent: Wednesday, January 04, 2017 11:51 AM > To: Benoit Claise (bclaise) > Cc: Job Snijders ; Ignas Bagdonas ;= The IESG ; draft-ietf-idr- > large-community@ietf.org; idr-chairs@ietf.org; idr@ietf.org; rick.casarez= @gmail.com > Subject: Re: Benoit Claise's Discuss on draft-ietf-idr-large-community-11= : (with DISCUSS and COMMENT) >=20 > Benoit, >=20 > I think the wording is accurate as written, but I see your point. I think= your suggested wording is terse to a fault > since it abandons the important "this will work with your four-byte ASN" = information. IMO a change is not strictly > needed, but if one is desired how about something like this? >=20 > OLD: > The attribute is suitable for use with four-octet > Autonomous System Numbers >=20 > NEW: > The attribute is suitable for use with all Autonomous System Numbers i= ncluding four-octet > Autonomous System Numbers >=20 > Or a lawyer would probably say :-) > The attribute is suitable for use with, inter alia, four-octet > Autonomous System Numbers >=20 > Regards, >=20 > -John >=20 > > On Jan 4, 2017, at 1:43 PM, Benoit Claise wrote: > > > > Hi Job, > > > > So basically, you're telling me: "The attribute is suitable for use wit= h ASNs.", right? > > Is this what needs to be in the abstract? > > > > Regards, B. > >> Hi Benoit, > >> > >> On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote: > >>>> Global Administrator field is a 4 octet integer that is used to carr= y AS > >>>> number but it is not mandatory to interpret it as an AS number only > >>>> (while a typical use case is for carrying AS number) - two peers can > >>>> agree on any value that has meaning between those peers. Representat= ion > >>>> on the wire is in network byte order, and 2 byte AS number will get > >>>> naturally padded with two zero bytes in front. Virtually all deploym= ents > >>>> today are AS4 capable and use AS4 encoding even for AS number values > >>>> that fit into 16 bit value range therefore AS number is a 4 octet en= tity > >>>> already. > >>> Then this sentence in the abstract "The attribute is suitable for use > >>> with four-octet ASNs." is misleading, right? At least to me. The > >>> attribute is suitable for four-octets ASNs and two-octets ASNs encode= d > >>> in four-octets. This would be more in line with "This field SHOULD be > >>> an Autonomous System Number (ASN)" later on. > >> I am under the impression that nowadays the IETF community considers a= ll > >> ASNs to be four-octet ASNs, however, some of those ASNs can be encoded > >> as a two octet value. The Large Communities specification is suitable > >> for usage in Autonomous Systems from all walks of life, where as rfc19= 97 > >> communities are unsuitable for all ASNs, specifically those ASNs which > >> cannot be encoded as two-octet values. > >> > >> Kind regards, > >> > >> Job > >> . > >> > > From nobody Wed Jan 4 14:06:37 2017 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED25212966F; Wed, 4 Jan 2017 14:06:35 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Ben Campbell" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148356759596.13056.13444019601334237871.idtracker@ietfa.amsl.com> Date: Wed, 04 Jan 2017 14:06:35 -0800 Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, idr-chairs@ietf.org Subject: [Idr] Ben Campbell's No Objection on draft-ietf-idr-large-community-11: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 22:06:36 -0000 Ben Campbell has entered the following ballot position for draft-ietf-idr-large-community-11: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The first sentence of section 6 seems to delegate at least some security considerations to RFC 1997. That RFC's security considerations entirely comprises the statement that the RFC does not discuss security. (This would have been a DISCUSS, but I gather from discussion of the genart review that the authors intend to remove the sentence.) From nobody Thu Jan 5 00:26:01 2017 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 43056129484; Thu, 5 Jan 2017 00:25:55 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Benoit Claise" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148360475527.20665.11545913165681988756.idtracker@ietfa.amsl.com> Date: Thu, 05 Jan 2017 00:25:55 -0800 Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, rick.casarez@gmail.com, idr-chairs@ietf.org Subject: [Idr] Benoit Claise's No Objection on draft-ietf-idr-large-community-11: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 08:25:55 -0000 Benoit Claise has entered the following ballot position for draft-ietf-idr-large-community-11: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks John for an excellent shepherd writeup. I see from the abstract: "The attribute is suitable for use with four-octet ASNs." I also see this text, which doesn't mention four-octet ASNs The Global Administrator field is intended to allow different Autonomous Systems to define BGP Large Communities without collision. This field SHOULD be an Autonomous System Number (ASN), in which case the Local Data Parts are to be interpreted as defined by the owner of the ASN. The use of Reserved ASNs (0 [RFC7607], 65535 and 4294967295 [RFC7300]) is NOT RECOMMENDED. What if the ASN is two bytes, we use padding? How? Even if we would say: "This field SHOULD be an four-octet Autonomous System Number (ASN)", it doesn't preclude inserting a two-octet ASN in the Global Administrator field. Isn't it better to specify how? >From RFC 6793: Currently assigned two-octet AS numbers are converted into four-octet AS numbers by setting the two high-order octets of the four-octet field to zero. Such a four-octet AS number is said to be mappable to a two-octet AS number. =============================== After some discussion on the idr list. My reasoning has been: either you mention that two-octet ASN can be represented in four-octets (RFC6793) or you mention: suitable for all ASNs (2 or 4) It's so obvious to you guys in your community. Ok, it seems that we're going in circle here. You guys understood my issue. It was DISCUSSed. I believe the draft should be clearer, but this is not DISCUSS-level point any longer. Moving to a COMMENT, and trusting the responsible shepherd and AD. For the record, John's proposal solveds my issue. OLD: The attribute is suitable for use with four-octet Autonomous System Numbers NEW: The attribute is suitable for use with all Autonomous System Numbers including four-octet Autonomous System Numbers From nobody Thu Jan 5 03:29:38 2017 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 54D8A129483; Thu, 5 Jan 2017 03:29:32 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Jari Arkko" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148361577234.20637.4254770915971046067.idtracker@ietfa.amsl.com> Date: Thu, 05 Jan 2017 03:29:32 -0800 Archived-At: Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, rjsparks@nostrum.com, idr-chairs@ietf.org Subject: [Idr] Jari Arkko's Yes on draft-ietf-idr-large-community-11: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 11:29:32 -0000 Jari Arkko has entered the following ballot position for draft-ietf-idr-large-community-11: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Of course we shall approve this document and make it an RFC! Thanks for the work. However, I do agree with Robert Spark's Gen-ART comments re: the first sentence of the Security Considerations section. I'd either remove the sentence, add pointers to other RFCs with actual security implications content, or reformulate to ".... has similar security properties as RFC 1997 (even if those were not documented in that RFC)". From nobody Thu Jan 5 03:31:56 2017 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 3484612948F; Thu, 5 Jan 2017 03:31:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5 X-Spam-Level: X-Spam-Status: No, score=-5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1] autolearn=ham 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 LdReWBQP7YWv; Thu, 5 Jan 2017 03:31:48 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CF63312946E; Thu, 5 Jan 2017 03:31:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EA64D2D291; Thu, 5 Jan 2017 13:31:46 +0200 (EET) (envelope-from jari.arkko@piuha.net) X-Virus-Scanned: amavisd-new at piuha.net Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ArpROzwebIOp; Thu, 5 Jan 2017 13:31:46 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7E7BF2D290; Thu, 5 Jan 2017 13:31:46 +0200 (EET) (envelope-from jari.arkko@piuha.net) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_FE6FC1A0-0133-49C6-86E2-2492C17C0D04"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail From: Jari Arkko In-Reply-To: Date: Thu, 5 Jan 2017 13:31:45 +0200 Message-Id: <8D3FF1C3-7ED6-49F6-95CE-37153B77CC1C@piuha.net> References: <07906876-6e21-2df9-c7a0-1270e76fea4e@nostrum.com> <20161212191159.GF75593@Vurt.local> <8dc27460-a500-3948-0a61-da4dd2baf66b@nostrum.com> To: Robert Sparks , Job Snijders X-Mailer: Apple Mail (2.1878.6) Archived-At: Cc: "idr@ietf.org" , General Area Review Team , "draft-ietf-idr-large-community.all@ietf.org" , "ietf@ietf.org" Subject: Re: [Idr] Genart LC review: draft-ietf-idr-large-community-11 X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 11:31:49 -0000 --Apple-Mail=_FE6FC1A0-0133-49C6-86E2-2492C17C0D04 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Thanks for the review, Robert. And thank you WG/authors for this much needed document. I think the document is ready to move forward (although I agree with = Robert re: the first sentence of the Security considerations section =97 = IMHO, the authors should remove, reformulate, or add other references to = that sentence). Jari --Apple-Mail=_FE6FC1A0-0133-49C6-86E2-2492C17C0D04 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJYbi6iAAoJEM80gCTQU46qFbkP/ixnha3j06JD7/u3ISudDkat wnWB6GZt9pku9F7cV+rCWs4MtcrUS+uc7WbvLQ8jgBDzVna+9X43N3cohsRqIUjH zWShB8rkc2/uUXL/tf2vnleIk5l/7golom5f1LvfgKIz0R5jwUqBU/px+Px6Uhe8 u82L43a217BOARdqji65nfOtmGYDEQCztFFHehN0PwYpx2G05qmKXr/NJfGSO/lR Wt1srkzokLXTsAdUYG2fEWaB/9W9ia+8/bT98oCz2RyJBDY/qHP273Sq/ClHJppT c2iz082D5n+c1VHncYs/7+LVWgT1X8dS6eKaTGry62dxORwiK1P2Hhq7aK00aNyD BEcQtEj1wqa+allQ0Vw5Qxkqo2UGawO0w7llLMeMTKt73KOirSQjf3e7sI+Z73R2 ij/Y2PXFi3jqmbC0Wfad5hbCLUT+BvgApNWrqrC9NqczjgoVFhIvpANR7Na1USws /Jbn8PBpSHLokt0KVfKGBEcugziAxCAT9FIZsjRqrrOWhcezrkxx8QpBvtE6NQwP 7NlyuvhgTvLlxANvMTcUr830R6QKXVBUoBfuRWWsiJUdx832npAl/xPZD3siWyFP GNAheOu2PMdTzXmE6Q+9wLCsuvuejzxIbNv0tCdkk/rlxFNntBbNsrNFm8mVenkB zZLZkLrqezQwVQfuHiJ/ =c4c3 -----END PGP SIGNATURE----- --Apple-Mail=_FE6FC1A0-0133-49C6-86E2-2492C17C0D04-- From nobody Thu Jan 5 05:04:48 2017 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 F3F8D129AE2; Thu, 5 Jan 2017 00:19:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.621 X-Spam-Level: X-Spam-Status: No, score=-17.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, 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 38D_61E_ltp4; Thu, 5 Jan 2017 00:19:57 -0800 (PST) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66E9D1294C5; Thu, 5 Jan 2017 00:19:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10496; q=dns/txt; s=iport; t=1483604396; x=1484813996; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=SxMeK8apFUJNMcDQwCNr57iw9E6OUQdnGK0ZcDN1NyU=; b=EY+6dn6Ow00mNjz1kREqBJfzTnVCKursGDWBNkfz27PnzNLb2P0z3NDt aV8QkuphJynWpViY2J+akOsh5ey0A9NfGq9VUI7hDPn05WoKI+IW3/ewb Xl2Auj+LiGW98X61D8ynf3fYET0Xv4hR/lRb1g+BLU+5Fqd+ob5x3vgpG U=; X-IronPort-AV: E=Sophos;i="5.33,320,1477958400"; d="scan'208,217";a="648514821" Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Jan 2017 08:19:54 +0000 Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v058JrRg020670; Thu, 5 Jan 2017 08:19:54 GMT To: "Jakob Heitz (jheitz)" , "John G. Scudder" References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com> <748483d7-df5c-e961-15f5-5aa76b784a7e@gmail.com> <20170104161329.GD53926@Vurt.local> <503f746a-7530-388f-4ed7-6868e53b7ff4@cisco.com> <5ED073F1-7EB7-438F-81DE-7287D48831EB@juniper.net> From: Benoit Claise Message-ID: Date: Thu, 5 Jan 2017 09:19:54 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------645259ED910EAF3265705E51" Archived-At: X-Mailman-Approved-At: Thu, 05 Jan 2017 05:04:46 -0800 Cc: "idr@ietf.org" , "idr-chairs@ietf.org" , The IESG , "draft-ietf-idr-large-community@ietf.org" , "rick.casarez@gmail.com" Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 08:19:59 -0000 This is a multi-part message in MIME format. --------------645259ED910EAF3265705E51 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Jakob, > There is no need to change the text. > > The attribute is in fact suitable for use with four-octet ASNs. > Since all ASNs can be represented in 4 octets, there is no problem. And the document lacks this link to RFC6793 as I mentioned in my initial DISCUSS, most probably because it's so obvious to you guys in your community. My reasoning has been: either you mention that two-octet ASN can be represented in four-octets (RFC6793) or you mention: suitable for all ASNs (2 or 4) Ok, it seems that we're going in circle here. You guys understood my issue. It was DISCUSSed. I believe the draft should be clearer, but this is not DISCUSS-level point any longer. Moving to a COMMENT, and trusting the responsible shepherd and AD. For the record, John's proposal solved the issue. OLD: The attribute is suitable for use with four-octet Autonomous System Numbers NEW: The attribute is suitable for use with all Autonomous System Numbers including four-octet Autonomous System Numbers Regards, Benoit > > Thanks, > Jakob. > >> -----Original Message----- >> From: John G. Scudder [mailto:jgs@juniper.net] >> Sent: Wednesday, January 04, 2017 11:51 AM >> To: Benoit Claise (bclaise) >> Cc: Job Snijders ; Ignas Bagdonas ; The IESG ; draft-ietf-idr- >> large-community@ietf.org; idr-chairs@ietf.org; idr@ietf.org; rick.casarez@gmail.com >> Subject: Re: Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT) >> >> Benoit, >> >> I think the wording is accurate as written, but I see your point. I think your suggested wording is terse to a fault >> since it abandons the important "this will work with your four-byte ASN" information. IMO a change is not strictly >> needed, but if one is desired how about something like this? >> >> OLD: >> The attribute is suitable for use with four-octet >> Autonomous System Numbers >> >> NEW: >> The attribute is suitable for use with all Autonomous System Numbers including four-octet >> Autonomous System Numbers >> >> Or a lawyer would probably say :-) >> The attribute is suitable for use with, inter alia, four-octet >> Autonomous System Numbers >> >> Regards, >> >> -John >> >>> On Jan 4, 2017, at 1:43 PM, Benoit Claise wrote: >>> >>> Hi Job, >>> >>> So basically, you're telling me: "The attribute is suitable for use with ASNs.", right? >>> Is this what needs to be in the abstract? >>> >>> Regards, B. >>>> Hi Benoit, >>>> >>>> On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote: >>>>>> Global Administrator field is a 4 octet integer that is used to carry AS >>>>>> number but it is not mandatory to interpret it as an AS number only >>>>>> (while a typical use case is for carrying AS number) - two peers can >>>>>> agree on any value that has meaning between those peers. Representation >>>>>> on the wire is in network byte order, and 2 byte AS number will get >>>>>> naturally padded with two zero bytes in front. Virtually all deployments >>>>>> today are AS4 capable and use AS4 encoding even for AS number values >>>>>> that fit into 16 bit value range therefore AS number is a 4 octet entity >>>>>> already. >>>>> Then this sentence in the abstract "The attribute is suitable for use >>>>> with four-octet ASNs." is misleading, right? At least to me. The >>>>> attribute is suitable for four-octets ASNs and two-octets ASNs encoded >>>>> in four-octets. This would be more in line with "This field SHOULD be >>>>> an Autonomous System Number (ASN)" later on. >>>> I am under the impression that nowadays the IETF community considers all >>>> ASNs to be four-octet ASNs, however, some of those ASNs can be encoded >>>> as a two octet value. The Large Communities specification is suitable >>>> for usage in Autonomous Systems from all walks of life, where as rfc1997 >>>> communities are unsuitable for all ASNs, specifically those ASNs which >>>> cannot be encoded as two-octet values. >>>> >>>> Kind regards, >>>> >>>> Job >>>> . >>>> > . > --------------645259ED910EAF3265705E51 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit
Hi Jakob,
There is no need to change the text.

The attribute is in fact suitable for use with four-octet ASNs.
Since all ASNs can be represented in 4 octets, there is no problem.
And the document lacks this link to RFC6793 as I mentioned in my initial DISCUSS, most probably because it's so obvious to you guys in your community.
My reasoning has been:
    either you mention that two-octet ASN can be represented in four-octets (RFC6793)
    or you mention: suitable for all ASNs (2 or 4)

Ok, it seems that we're going in circle here.
You guys understood my issue. It was DISCUSSed. I believe the draft should be clearer, but this is not DISCUSS-level point any longer.
Moving to a COMMENT, and trusting the responsible shepherd and AD.

For the record, John's proposal solved the issue.
OLD:
   The attribute is suitable for use with four-octet
   Autonomous System Numbers

NEW:
   The attribute is suitable for use with all Autonomous System Numbers including four-octet
   Autonomous System Numbers

Regards, Benoit

Thanks,
Jakob.


-----Original Message-----
From: John G. Scudder [mailto:jgs@juniper.net]
Sent: Wednesday, January 04, 2017 11:51 AM
To: Benoit Claise (bclaise) <bclaise@cisco.com>
Cc: Job Snijders <job@ntt.net>; Ignas Bagdonas <ibagdona.ietf@gmail.com>; The IESG <iesg@ietf.org>; draft-ietf-idr-
large-community@ietf.org; idr-chairs@ietf.org; idr@ietf.org; rick.casarez@gmail.com
Subject: Re: Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT)

Benoit,

I think the wording is accurate as written, but I see your point. I think your suggested wording is terse to a fault
since it abandons the important "this will work with your four-byte ASN" information. IMO a change is not strictly
needed, but if one is desired how about something like this?

OLD:
   The attribute is suitable for use with four-octet
   Autonomous System Numbers

NEW:
   The attribute is suitable for use with all Autonomous System Numbers including four-octet
   Autonomous System Numbers

Or a lawyer would probably say :-)
   The attribute is suitable for use with, inter alia, four-octet
   Autonomous System Numbers

Regards,

-John


On Jan 4, 2017, at 1:43 PM, Benoit Claise <bclaise@cisco.com> wrote:

Hi Job,

So basically, you're telling me: "The attribute is suitable for use with ASNs.", right?
Is this what needs to be in the abstract?

Regards, B.

Hi Benoit,

On Wed, Jan 04, 2017 at 04:39:25PM +0100, Benoit Claise wrote:

Global Administrator field is a 4 octet integer that is used to carry AS
number but it is not mandatory to interpret it as an AS number only
(while a typical use case is for carrying AS number) - two peers can
agree on any value that has meaning between those peers. Representation
on the wire is in network byte order, and 2 byte AS number will get
naturally padded with two zero bytes in front. Virtually all deployments
today are AS4 capable and use AS4 encoding even for AS number values
that fit into 16 bit value range therefore AS number is a 4 octet entity
already.

Then this sentence in the abstract "The attribute is suitable for use
with four-octet ASNs." is misleading, right? At least to me. The
attribute is suitable for four-octets ASNs and two-octets ASNs encoded
in four-octets. This would be more in line with "This field SHOULD be
an Autonomous System Number (ASN)" later on.

I am under the impression that nowadays the IETF community considers all
ASNs to be four-octet ASNs, however, some of those ASNs can be encoded
as a two octet value. The Large Communities specification is suitable
for usage in Autonomous Systems from all walks of life, where as rfc1997
communities are unsuitable for all ASNs, specifically those ASNs which
cannot be encoded as two-octet values.

Kind regards,

Job
.



        

      

      
.



    

    

  


--------------645259ED910EAF3265705E51--


From nobody Thu Jan  5 05:55:45 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 90E85129552; Thu,  5 Jan 2017 05:55:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148362453058.20637.17274296187645790075.idtracker@ietfa.amsl.com>
Date: Thu, 05 Jan 2017 05:55:30 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-large-community-12.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 05 Jan 2017 13:55:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : BGP Large Communities
        Authors         : Jakob Heitz
                          Job Snijders
                          Keyur Patel
                          Ignas Bagdonas
                          Nick Hilliard
	Filename        : draft-ietf-idr-large-community-12.txt
	Pages           : 9
	Date            : 2017-01-05

Abstract:
   This document describes the BGP Large Communities attribute, an
   extension to BGP-4.  This attribute provides a mechanism to signal
   opaque information within separate namespaces to aid in routing
   management.  The attribute is suitable for use with all Autonomous
   System Numbers including four-octet Autonomous System Numbers.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-large-community-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-large-community-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jan  5 08:25:53 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B550512941C; Thu,  5 Jan 2017 08:25:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148363354773.20720.4919468933951558353.idtracker@ietfa.amsl.com>
Date: Thu, 05 Jan 2017 08:25:47 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-optimal-route-reflection-13.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 05 Jan 2017 16:25:48 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : BGP Optimal Route Reflection (BGP-ORR)
        Authors         : Robert Raszuk
                          Christian Cassar
                          Erik Aman
                          Bruno Decraene
                          Stephane Litkowski
                          Kevin Wang
	Filename        : draft-ietf-idr-bgp-optimal-route-reflection-13.txt
	Pages           : 12
	Date            : 2017-01-05

Abstract:
   This document proposes a solution for BGP route reflectors to allow
   them to choose the best path their clients would have chosen under
   the same conditions, without requiring further state or any new
   features to be placed on the clients.  This facilitates, for example,
   best exit point policy (hot potato routing).  This solution is
   primarily applicable in deployments using centralized route
   reflectors.

   The solution relies upon all route reflectors learning all paths
   which are eligible for consideration.  Best path selection is
   performed in each route reflector based on a configured virtual
   location in the IGP.  The location can be the same for all clients or
   different per peer/update group or per peer.  Best path selection can
   also be performed based on user configured policies in each route
   reflector.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-optimal-route-reflection/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-bgp-optimal-route-reflection-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-optimal-route-reflection-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Jan  6 10:40:33 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 27CEA129D82; Fri,  6 Jan 2017 10:40:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148372802915.17430.14350887721792799482.idtracker@ietfa.amsl.com>
Date: Fri, 06 Jan 2017 10:40:29 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-te-lsp-distribution-06.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 06 Jan 2017 18:40:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : Distribution of Traffic Engineering (TE) Policies and State using BGP-LS
        Authors         : Stefano Previdi
                          Jie Dong
                          Mach(Guoyi) Chen
                          Hannes Gredler
                          Jeff Tantsura
	Filename        : draft-ietf-idr-te-lsp-distribution-06.txt
	Pages           : 26
	Date            : 2017-01-06

Abstract:
   This document describes a mechanism to collect the Traffic
   Engineering and Policy information that is locally available in a
   router and advertise it into BGP-LS updates.  Such information can be
   used by external components for path computation, re-optimization,
   service placement, network visualization, etc.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-te-lsp-distribution/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-te-lsp-distribution-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-te-lsp-distribution-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jan  9 08:00:02 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C48129689; Mon,  9 Jan 2017 07:59:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148397758768.25002.13315615234296240117.idtracker@ietfa.amsl.com>
Date: Mon, 09 Jan 2017 07:59:47 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-route-leak-detection-mitigation-05.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 09 Jan 2017 15:59:48 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : Methods for Detection and Mitigation of BGP Route Leaks
        Authors         : Kotikalapudi Sriram
                          Doug Montgomery
                          Brian Dickson
                          Keyur Patel
                          Andrei Robachevsky
	Filename        : draft-ietf-idr-route-leak-detection-mitigation-05.txt
	Pages           : 22
	Date            : 2017-01-09

Abstract:
   [I-D.ietf-grow-route-leak-problem-definition] provides a definition
   of the route leak problem, and also enumerates several types of route
   leaks.  This document first examines which of those route-leak types
   are detected and mitigated by the existing origin validation (OV)
   [RFC 6811].  It is recognized that OV offers a limited detection and
   mitigation capability against route leaks.  This document specifies
   enhancements that significantly extend the route-leak prevention,
   detection, and mitigation capabilities of BGP.  One solution
   component involves carrying a per-hop route-leak protection (RLP)
   field in BGP updates.  The RLP field is proposed to be carried in a
   new optional transitive attribute, called BGP RLP attribute.  The
   solution is meant to be initially implemented as an enhancement of
   BGP without requiring BGPsec [I-D.ietf-sidr-bgpsec-protocol].
   However, when BGPsec is deployed in the future, the solution can be
   incorporated in BGPsec, enabling cryptographic protection for the RLP
   field.  That would be one way of implementing the proposed solution
   in a secure way.  The document also includes a stopgap method for
   detection and mitigation of route leaks for an intermediate phase
   when OV is deployed but BGP protocol on the wire is unchanged.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-route-leak-detection-mitigation/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-route-leak-detection-mitigation-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-route-leak-detection-mitigation-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jan  9 08:01:02 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AB6BB129620; Mon,  9 Jan 2017 08:00:54 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG 
To: "IETF-Announce" 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148397765469.24904.13335963786276516609.idtracker@ietfa.amsl.com>
Date: Mon, 09 Jan 2017 08:00:54 -0800
Archived-At: 
Cc: idr@ietf.org, idr-chairs@ietf.org, The IESG , draft-ietf-idr-large-community@ietf.org, rfc-editor@rfc-editor.org
Subject: [Idr] Protocol Action: 'BGP Large Communities' to Proposed Standard (draft-ietf-idr-large-community-12.txt)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 09 Jan 2017 16:00:55 -0000

The IESG has approved the following document:
- 'BGP Large Communities'
  (draft-ietf-idr-large-community-12.txt) as Proposed Standard

This document is the product of the Inter-Domain Routing Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-large-community/





Technical Summary

   This document describes the BGP Large Communities attribute, an
   extension to BGP-4.  This attribute provides a mechanism to signal
   opaque information within separate namespaces to aid in routing
   management.  The attribute is suitable for use with four-octet
   Autonomous System Numbers.

Working Group Summary

  There is good consensus to move forward with this draft. Details about 
  points of debate (all of which have been resolved to the level of "rough 
  consensus" with good engagement from the WG) can be found in the 
  Shepherd's write-up.

Document Quality

   There are numerous existing implementations. They are summarized 
   both in the document and in the relevant IDR wiki: 
   https://trac.tools.ietf.org/wg/idr/trac/wiki/draft-ietf-idr-large-community%20implementations

Personnel

   The Document Shepherd is John Scudder.
   The Responsible Area Director is Alvaro Retana.


From nobody Tue Jan 10 08:06:12 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0511294B1; Mon,  9 Jan 2017 07:59:41 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG 
To: "IETF-Announce" 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148397758123.24884.11267004242772881782.idtracker@ietfa.amsl.com>
Date: Mon, 09 Jan 2017 07:59:41 -0800
Archived-At: 
X-Mailman-Approved-At: Tue, 10 Jan 2017 08:06:10 -0800
Cc: idr@ietf.org, idr-chairs@ietf.org, draft-ietf-idr-deprecate-30-31-129@ietf.org, The IESG , shares@ndzh.com, rfc-editor@rfc-editor.org
Subject: [Idr] Protocol Action: 'Deprecation of BGP Path Attribute values 30, 31, 129, 241, 242, and 243' to Proposed Standard (draft-ietf-idr-deprecate-30-31-129-02.txt)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 09 Jan 2017 15:59:41 -0000

The IESG has approved the following document:
- 'Deprecation of BGP Path Attribute values 30, 31, 129, 241, 242, and
   243'
  (draft-ietf-idr-deprecate-30-31-129-02.txt) as Proposed Standard

This document is the product of the Inter-Domain Routing Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-30-31-129/





Technical Summary

   This document requests IANA to mark BGP path attribute values 30, 31,
   129, 241, 242, and 243 as "deprecated". These values were found to be
   in use in the Internet, despite not having been allocated by IANA.

Working Group Summary

   This document arises because as part of the development of the large 
   communities specification, values 30 and 31 were discovered to be "squatted" 
   on by fielded implementations. Subsequently, two other implementations were 
   found to be "squatting" on the other values. There was some debate in the working 
   group as to whether it was better to deprecate the code points or to somehow "punish" 
   the offending implementers. One of the arguments in favor of deprecation was that 
   pragmatically speaking, no implementer would reasonably want to use one of the 
   tainted code points and if forced to do so, no operator would be excited to deploy the 
   resulting feature. The deprecation process was identified as the appropriate one to allow 
   IANA to flag them as unfit for use. There was good working group consensus for this 
   position.

Document Quality

   This is a trivial process document. It has received good WG attention including review 
   by people associated with all parties "squatting" on the affected path attribute values.

Personnel

Document Shepherd: John Scudder
Responsible Area Director: Alvaro Retana


From nobody Sat Jan 14 00:43:03 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C7D12948B; Sat, 14 Jan 2017 00:43:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148438338098.24064.663985563281742744.idtracker@ietfa.amsl.com>
Date: Sat, 14 Jan 2017 00:43:00 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-shutdown-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 14 Jan 2017 08:43:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : BGP Administrative Shutdown Communication
        Authors         : Job Snijders
                          Jakob Heitz
                          John Scudder
	Filename        : draft-ietf-idr-shutdown-02.txt
	Pages           : 6
	Date            : 2017-01-14

Abstract:
   This document enhances the BGP Cease NOTIFICATION message
   "Administrative Shutdown" subcode for operators to transmit a short
   freeform message to describe why a BGP session was shutdown.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-shutdown-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Jan 14 01:05:39 2017
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 7CEFA12946E for ; Sat, 14 Jan 2017 01:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.134
X-Spam-Level: 
X-Spam-Status: No, score=-5.134 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_SOFTFAIL=0.665] autolearn=ham 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 eM_5dEgR9zDi for ; Sat, 14 Jan 2017 01:05:36 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 C04AA12946C for ; Sat, 14 Jan 2017 01:05:36 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cSKHH-000AGa-FZ (job@us.ntt.net); Sat, 14 Jan 2017 09:05:36 +0000
Date: Sat, 14 Jan 2017 10:05:32 +0100
From: Job Snijders 
To: idr@ietf.org
Message-ID: <20170114090532.GH1055@Vurt.local>
References: <148438338098.24064.663985563281742744.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148438338098.24064.663985563281742744.idtracker@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: 
Subject: Re: [Idr] I-D Action: draft-ietf-idr-shutdown-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 14 Jan 2017 09:05:38 -0000

Hi all,

Changelog for -01 -> -02:

    o shorten the title
    o remove redundant remark about "shortest form" in section 2
    o add paragraph about transport confidentiality
    o update implementation overview, added:
        - pmacct
        - OpenBGPD
        - Wireshark, tcpdump

Kind regards,

Job

On Sat, Jan 14, 2017 at 12:43:00AM -0800, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Inter-Domain Routing of the IETF.
> 
>         Title           : BGP Administrative Shutdown Communication
>         Authors         : Job Snijders
>                           Jakob Heitz
>                           John Scudder
> 	Filename        : draft-ietf-idr-shutdown-02.txt
> 	Pages           : 6
> 	Date            : 2017-01-14
> 
> Abstract:
>    This document enhances the BGP Cease NOTIFICATION message
>    "Administrative Shutdown" subcode for operators to transmit a short
>    freeform message to describe why a BGP session was shutdown.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-idr-shutdown-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


From nobody Tue Jan 17 12:46:10 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB54129504; Tue, 17 Jan 2017 12:46:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat 
To: , , 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148468596957.32058.8601634758998246164.idtracker@ietfa.amsl.com>
Date: Tue, 17 Jan 2017 12:46:09 -0800
Archived-At: 
Subject: [Idr] The IDR WG has placed draft-hr-idr-rfc5575bis in state "Candidate for WG Adoption"
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 17 Jan 2017 20:46:09 -0000

The IDR WG has placed draft-hr-idr-rfc5575bis in state 
Candidate for WG Adoption (entered by Susan Hares)

The document is available at
https://datatracker.ietf.org/doc/draft-hr-idr-rfc5575bis/


From nobody Tue Jan 17 13:01:48 2017
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 256881294FA; Tue, 17 Jan 2017 13:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.845
X-Spam-Level: **
X-Spam-Status: No, score=2.845 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no 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 gdB80mNvYcSz; Tue, 17 Jan 2017 13:01:45 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FFE71294A1; Tue, 17 Jan 2017 13:01:45 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.90.185; 
From: "Susan Hares" 
To: "'idr wg'" 
Date: Tue, 17 Jan 2017 15:57:11 -0500
Message-ID: <01ab01d27104$561cedb0$0256c910$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AC_01D270DA.6D475AE0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdJxAtLSjVagmTouT12myqaMdi4qbA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: 
Cc: idr-chairs@ietf.org
Subject: [Idr] Shepherd review of draft-ietf-idr-showdown-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 17 Jan 2017 21:01:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01AC_01D270DA.6D475AE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

As shepherd, I have given this document an early review prior to WG LC.  

 

Status: Ready for WG LC, editorial change requested for IANA clarity. 

 

Section 5: 

 

Old:/ Per this document, IANA is requested to reference this document at the
subcode 

"Administrative Shutdown" in the "Cease NOTIFICATION message subcodes"
registry under the 

"Border Gateway Protocol (BGP) Parameters" group/

 

New:/ Per this document, IANA is requested to reference this document at the
subcode 

"Administrative Shutdown" in the "Cease NOTIFICATION message subcodes"
registry under the 

"Border Gateway Protocol (BGP) Parameters" group in addition to 

RFC4486. /

 

 

 

Sue Hares 

Shepherd 


------=_NextPart_000_01AC_01D270DA.6D475AE0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


As =
shepherd, I have given this document an early review prior to WG =
LC.  
 
Status: Ready for WG LC, editorial change requested =
for IANA clarity. 
 
Section 5: =

 
Old:/ Per this document, IANA is requested to =
reference this document at the subcode 
“Administrative Shutdown” in the =
“Cease NOTIFICATION message subcodes” registry under the =

“Border Gateway Protocol (BGP) =
Parameters” group/
 
New:/ Per =
this document, IANA is requested to reference this document at the =
subcode 
“Administrative =
Shutdown” in the “Cease NOTIFICATION message subcodes” =
registry under the 
“Border =
Gateway Protocol (BGP) Parameters” group in addition to =

RFC4486. /
 
 
 
Sue Hares =

Shepherd =


------=_NextPart_000_01AC_01D270DA.6D475AE0--


From nobody Tue Jan 17 13:08:30 2017
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 E4A541294D3; Tue, 17 Jan 2017 13:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.346
X-Spam-Level: **
X-Spam-Status: No, score=2.346 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no 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 FZfE_iaBFuzN; Tue, 17 Jan 2017 13:08:28 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B13191294A3; Tue, 17 Jan 2017 13:08:27 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.90.185; 
From: "Susan Hares" 
To: 
Date: Tue, 17 Jan 2017 16:04:18 -0500
Message-ID: <01b801d27105$45702bc0$d0508340$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B9_01D270DB.5C9AC000"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdJxBUSYlwAykEovTW6bWx9yuL15Uw==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: 
Cc: draft-ietf-idr-shutdown@ietf.org
Subject: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 17 Jan 2017 21:08:29 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01B9_01D270DB.5C9AC000
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
(1/17/2017 to 1/31/2017).  Section 7 of this document lists the
implementations that have been created for this BGP functionality.   These
include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and tcpdump

 
   o  ExaBGP [1
 ]
   o  pmacct [2
 ]
   o  OpenBGPD [3
 ]
   o  Wireshark [4
 ] (packet
analyser)
.         tcpdump [5
 ], (alt) [6
 ] (packet
analyser)

 

Operators should examine if freeform UTF-8 encoded string as described meets
their operational needs.  

 

Sue Hares

WG Co-chair 


------=_NextPart_000_01B9_01D270DB.5C9AC000
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


This =
begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt =
(1/17/2017 to 1/31/2017).  Section 7 of this document lists the =
implementations that have been created for this BGP =
functionality.   These include: ExaBGP, pmacct, OpenBGPD, =
Wireshark (packet analyzer), and tcpdump
 
   o  ExaBGP [1]
   =
o  pmacct [2]
   =
o  OpenBGPD [3]
   =
o  Wireshark [4] (packet analyser)
·         =
tcpdump [5], (alt) [6] (packet analyser)
 
Operators =
should examine if freeform UTF-8 encoded string as described meets their =
operational needs.  
 
Sue =
Hares
WG Co-chair =


------=_NextPart_000_01B9_01D270DB.5C9AC000--


From nobody Tue Jan 17 13:29:52 2017
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 B3DA5129495; Tue, 17 Jan 2017 13:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.133
X-Spam-Level: 
X-Spam-Status: No, score=-5.133 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_SOFTFAIL=0.665] autolearn=ham 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 GFPieWX4GuNb; Tue, 17 Jan 2017 13:29:49 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 5DFD8129422; Tue, 17 Jan 2017 13:29:49 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cTbK7-0000Bf-Lx (job@us.ntt.net); Tue, 17 Jan 2017 21:29:48 +0000
Date: Tue, 17 Jan 2017 22:29:28 +0100
From: job@ntt.net
To: 'idr wg' , Susan Hares 
Message-ID: <4ca7c77e-12fa-4edf-9c1b-3c729e022546@Spark>
In-Reply-To: <01ab01d27104$561cedb0$0256c910$@ndzh.com>
References: <01ab01d27104$561cedb0$0256c910$@ndzh.com>
X-Readdle-Message-ID: 4ca7c77e-12fa-4edf-9c1b-3c729e022546@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="587e8cc8_643c9869_aed"
Archived-At: 
Cc: idr-chairs@ietf.org
Subject: Re: [Idr] Shepherd review of draft-ietf-idr-shutdown-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 17 Jan 2017 21:29:51 -0000

--587e8cc8_643c9869_aed
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Subject should reference =22draft-ietf-idr-shutdown=22.

Kind regards,

Job

On 17 Jan 2017, 22:01 +0100, Susan Hares , wrote:
>
> As shepherd, I have given this document an early review prior to WG LC.=

>
>
>
>
>
> Status: Ready for WG LC, editorial change requested for IANA clarity.
>
>
>
>
>
> Section 5:
>
>
>
>
>
> Old:/ Per this document, IANA is requested to reference this document a=
t the subcode
>
>
> =E2=80=9CAdministrative Shutdown=E2=80=9D in the =E2=80=9CCease NOTI=46=
ICATION message subcodes=E2=80=9D registry under the
>
>
> =E2=80=9CBorder Gateway Protocol (BGP) Parameters=E2=80=9D group/
>
>
>
>
>
> New:/ Per this document, IANA is requested to reference this document a=
t the subcode
>
>
> =E2=80=9CAdministrative Shutdown=E2=80=9D in the =E2=80=9CCease NOTI=46=
ICATION message subcodes=E2=80=9D registry under the
>
>
> =E2=80=9CBorder Gateway Protocol (BGP) Parameters=E2=80=9D group in add=
ition to
>
>
> R=46C4486. /
>
>
>
>
>
>
>
>
>
>
>
> Sue Hares
>
>
> Shepherd
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Idr mailing list
> Idr=40ietf.org
> https://www.ietf.org/mailman/listinfo/idr

--587e8cc8_643c9869_aed
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline







Subject should reference =22draft-ie=
tf-idr-shutdown=22.



Kind regards,



Job







On 17 Jan 2017, 22:01 +0100, Susan Hares <shares=40ndzh.com>, wrote=
:






As shepherd, I have given this document an ear=
ly review prior to WG LC.&=23160;


&=23160;


Status: Ready for WG LC, editorial change requ=
ested for IANA clarity.


&=23160;


Section 5:


&=23160;


Old:/ Per this document, IANA is requested to =
reference this document at the subcode


=E2=80=9CAdministrative Shutdown=E2=80=9D in t=
he =E2=80=9CCease NOTI=46ICATION message subcodes=E2=80=9D registry under=
 the


=E2=80=9CBorder Gateway Protocol (BGP) Paramet=
ers=E2=80=9D group/


&=23160;


New:/ Per this document, IANA is requested to =
reference this document at the subcode


=E2=80=9CAdministrative Shutdown=E2=80=9D in t=
he =E2=80=9CCease NOTI=46ICATION message subcodes=E2=80=9D registry under=
 the


=E2=80=9CBorder Gateway Protocol (BGP) Paramet=
ers=E2=80=9D group in addition to


R=46C4486. /


&=23160;


&=23160;


&=23160;


Sue Hares


Shepherd



=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F

Idr mailing list

Idr=40ietf.org

https://www.ietf.org/mailman/listinfo/idr






--587e8cc8_643c9869_aed--


From nobody Tue Jan 17 14:27:40 2017
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 D5F6F1293F3; Tue, 17 Jan 2017 14:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
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 UqrmY88ssSRv; Tue, 17 Jan 2017 14:27:38 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) (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 025C4129410; Tue, 17 Jan 2017 14:27:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 3EDD45A; Tue, 17 Jan 2017 23:27:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:date:date:in-reply-to:from:from :subject:subject:mime-version:content-type:content-type:received :received; s=mail; t=1484692053; bh=+Q90L4TXHKFRw8zziSJTwW//aalx 4TfzpbvOFuEz7S0=; b=ergFDW1OiVvNrhIa8fBIi+hoIjdJ34BAoM4QXeCjlcRp s9FA3KeJzy8oxVD9mDTiUYcq4ibzEQ40r7CagBPo0yeJUodZskp5ucfS+MgeZiV/ tP+JTZLKIY1ZCHGwLqxRHzRod7XYyVQM6/EH3ZyT29Cwf+HyJF1JxLdYbXTXVz0=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TI6i6PFHu-Hq; Tue, 17 Jan 2017 23:27:33 +0100 (CET)
Received: from [IPv6:2a02:a213:a300:9300:d9b7:bcd2:8366:18c] (unknown [IPv6:2a02:a213:a300:9300:d9b7:bcd2:8366:18c]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 79A1258; Tue, 17 Jan 2017 23:27:33 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_9013C261-3D5C-43CE-9CD3-7CAF901A2935"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann 
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
Date: Tue, 17 Jan 2017 23:27:34 +0100
Message-Id: <63987445-7DFC-4956-9BD9-C94A0A5726F3@steffann.nl>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
To: Susan Hares 
X-Mailer: Apple Mail (2.3124)
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 17 Jan 2017 22:27:40 -0000

--Apple-Mail=_9013C261-3D5C-43CE-9CD3-7CAF901A2935
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

> Op 17 jan. 2017, om 22:04 heeft Susan Hares  het =
volgende geschreven:
>=20
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt =
(1/17/2017 to 1/31/2017).  Section 7 of this document lists the =
implementations that have been created for this BGP functionality.   =
These include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), =
and tcpdump
>=20
>    o  ExaBGP [1]
>    o  pmacct [2]
>    o  OpenBGPD [3]
>    o  Wireshark [4] (packet analyser)
> =C2=B7         tcpdump [5], (alt) [6] (packet analyser)
>=20
> Operators should examine if freeform UTF-8 encoded string as described =
meets their operational needs.

Speaking as an operator: it does. Adding freeform text to NOTIFICATION =
messages with code "Cease" with subcode "Administrative Shutdown" would =
be very useful to tell the operator on the other end of the connection =
what is going on. Trying to define all the possible values would be =
impossible because of the huge variety of ways operators work together, =
and limiting the possible values would limit the usefulness. Freeform =
text is therefore appropriate at this time, and UTF-8 encoding will =
allow us to write messages in a language appropriate to the situation.

Cheers,
Sander


--Apple-Mail=_9013C261-3D5C-43CE-9CD3-7CAF901A2935
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYfppWAAoJEKAtA7D+JBO5RykH/RWVQ/zffYs3G66w40aEYp0c
/X7x9Nufc8PcQLogX7rCwUg/xaC8xIrZagcSI9rItdLLyLAsDZN5sUHUF+r28JZH
iYT9+tTqPUmEBTjqZlkgheiaAHX9Qvc+RGZNzyHwHVESoKn45+BpmsEVyLtzWPBj
DO/7DBmi1fpIYVBSaj12OTESK/vNDaTThrU3UZLi3pJFaJVZM19VEQpFSu+eXSO4
RT6JG/5o3ZuIUGiyr59ahNbqEEPIpm1KXXHw2Ok01hixf29JUAz4kLE8ccqhpNXv
61svp1/vZk9dCccV+WpwyBd2ggge8xWMTzihQRx/IaE1DnS9v42z3GBU4HzOpCk=
=FQMs
-----END PGP SIGNATURE-----

--Apple-Mail=_9013C261-3D5C-43CE-9CD3-7CAF901A2935--


From nobody Wed Jan 18 01:08:26 2017
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 783E8129411; Wed, 18 Jan 2017 01:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.133
X-Spam-Level: 
X-Spam-Status: No, score=-5.133 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_SOFTFAIL=0.665] autolearn=ham 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 ADUylgzaflDc; Wed, 18 Jan 2017 01:08:24 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 753D7120727; Wed, 18 Jan 2017 01:08:24 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cTmEB-0003DW-6u (job@us.ntt.net); Wed, 18 Jan 2017 09:08:24 +0000
Date: Wed, 18 Jan 2017 10:08:09 +0100
From: job@ntt.net
To: 'idr wg' , Susan Hares 
Message-ID: <5e6b1fcd-124b-4a42-8932-9e50ef92453a@Spark>
In-Reply-To: <01ab01d27104$561cedb0$0256c910$@ndzh.com>
References: <01ab01d27104$561cedb0$0256c910$@ndzh.com>
X-Readdle-Message-ID: 5e6b1fcd-124b-4a42-8932-9e50ef92453a@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="587f307e_6b8b4567_e93"
Archived-At: 
Cc: idr-chairs@ietf.org
Subject: Re: [Idr] Shepherd review of draft-ietf-idr-shutdown-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 18 Jan 2017 09:08:25 -0000

--587f307e_6b8b4567_e93
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Dear Susan,

Your suggestion is a good one, this is indeed what we meant. I will inclu=
de it in the next version.

Thank you for the review=21

Kind regards,

Job

On 17 Jan 2017, 22:01 +0100, Susan Hares , wrote:
>
> As shepherd, I have given this document an early review prior to WG LC.=

>
>
>
>
>
> Status: Ready for WG LC, editorial change requested for IANA clarity.
>
>
>
>
>
> Section 5:
>
>
>
>
>
> Old:/ Per this document, IANA is requested to reference this document a=
t the subcode
>
>
> =E2=80=9CAdministrative Shutdown=E2=80=9D in the =E2=80=9CCease NOTI=46=
ICATION message subcodes=E2=80=9D registry under the
>
>
> =E2=80=9CBorder Gateway Protocol (BGP) Parameters=E2=80=9D group/
>
>
>
>
>
> New:/ Per this document, IANA is requested to reference this document a=
t the subcode
>
>
> =E2=80=9CAdministrative Shutdown=E2=80=9D in the =E2=80=9CCease NOTI=46=
ICATION message subcodes=E2=80=9D registry under the
>
>
> =E2=80=9CBorder Gateway Protocol (BGP) Parameters=E2=80=9D group in add=
ition to
>
>
> R=46C4486. /
>
>
>
>
>
>
>
>
>
>
>
> Sue Hares
>
>
> Shepherd
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Idr mailing list
> Idr=40ietf.org
> https://www.ietf.org/mailman/listinfo/idr

--587f307e_6b8b4567_e93
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline







Dear Susan,



Your suggestion is a good one, this is indeed what we meant. I will inclu=
de it in the next version.



Thank you for the review=21




Kind regards,



Job




On 17 Jan 2017, 22:01 +0100, Susan Hares <shares=40ndzh.com>, wrote=
:






As shepherd, I have given this document an ear=
ly review prior to WG LC.&=23160;


&=23160;


Status: Ready for WG LC, editorial change requ=
ested for IANA clarity.


&=23160;


Section 5:


&=23160;


Old:/ Per this document, IANA is requested to =
reference this document at the subcode


=E2=80=9CAdministrative Shutdown=E2=80=9D in t=
he =E2=80=9CCease NOTI=46ICATION message subcodes=E2=80=9D registry under=
 the


=E2=80=9CBorder Gateway Protocol (BGP) Paramet=
ers=E2=80=9D group/


&=23160;


New:/ Per this document, IANA is requested to =
reference this document at the subcode


=E2=80=9CAdministrative Shutdown=E2=80=9D in t=
he =E2=80=9CCease NOTI=46ICATION message subcodes=E2=80=9D registry under=
 the


=E2=80=9CBorder Gateway Protocol (BGP) Paramet=
ers=E2=80=9D group in addition to


R=46C4486. /


&=23160;


&=23160;


&=23160;


Sue Hares


Shepherd



=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F

Idr mailing list

Idr=40ietf.org

https://www.ietf.org/mailman/listinfo/idr






--587f307e_6b8b4567_e93--


From nobody Wed Jan 18 02:11:56 2017
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 09AC9129466 for ; Wed, 18 Jan 2017 02:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.058
X-Spam-Level: 
X-Spam-Status: No, score=-3.058 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.156, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 kH01lX-lbnFq for ; Wed, 18 Jan 2017 02:11:47 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.139]) by ietfa.amsl.com (Postfix) with ESMTP id 453B41289C4 for ; Wed, 18 Jan 2017 02:11:46 -0800 (PST)
Received: from [85.158.136.83] by server-3.bemta-5.messagelabs.com id 2B/42-31966-26F3F785; Wed, 18 Jan 2017 10:11:46 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJIsWRWlGSWpSXmKPExsUSsELzi268fX2 Ewd/95havbj9jcmD0WLLkJ1MAYxRrZl5SfkUCa8aUtzuYCrpZKhoadjE1MLawdDFycQgJHGSS WDThP5SzllFi8tpW5i5GTg42ASOJCev2AyU4OEQEFCVWfkoGCQsLBEusPf6cHcQWEQiRaJn7m hHC1pOYd/YLO0g5i4CqxJrXyiBhXgF7iYnt/5lAbEYBWYkvjavBpjMLiEvcejIfLC4hICCxZM 95ZghbVOLl43+sILYo0MiNF6axQ8QVJC4u6GIDGc8soCmxfpc+hGkr8a6xBGKiosSU7ofsEFs FJU7OfMIygVF4FpJlsxCaZyE0z0LSPAtJ8wJG1lWMGsWpRWWpRbpGFnpJRZnpGSW5iZk5uoYG pnq5qcXFiempOYlJxXrJ+bmbGIHRUM/AwLiDsW+V3yFGSQ4mJVHe5Vb1EUJ8SfkplRmJxRnxR aU5qcWHGGU4OJQkeKXtgHKCRanpqRVpmTnAuIRJS3DwKInwdoKkeYsLEnOLM9MhUqcYdTlOfb rwkkmIJS8/L1VKnHc1SJEASFFGaR7cCFiKuMQoKyXMy8jAwCDEU5BalJtZgir/ilGcg1FJmDc ZZApPZl4J3KZXQEcwAR1hpQx2REkiQkqqgdFip1u3iZli/6RLTipSSZ8bDixO5OSX9O5SPrDm a/4jnagF67TqonzTL+kLnrgv//+b2sXLslcerz33cVHd8zWVK0zrUpnteBfK2FQ+yb9lu7Ggf CG7xOLGPCm/WSIupm/YzptZcKV/u7x/q2pw23Oe02yZiurXL/K9byxjW/epp2+K/Yk4cyWW4o xEQy3mouJEAPesStQMAwAA
X-Env-Sender: david.freedman@uk.clara.net
X-Msg-Ref: server-11.tower-36.messagelabs.com!1484734303!82687301!1
X-Originating-IP: [80.168.41.244]
X-StarScan-Received: 
X-StarScan-Version: 9.1.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7576 invoked from network); 18 Jan 2017 10:11:43 -0000
Received: from staff02.mail.eu.clara.net (HELO staff02.mail.eu.clara.net) (80.168.41.244) by server-11.tower-36.messagelabs.com with SMTP; 18 Jan 2017 10:11:43 -0000
Received: from [80.168.41.252] (port=12006 helo=SRVGREXCAS02.claranet.local) by staff02.mail.eu.clara.net (staff02.mail.eu.clara.net [80.168.41.244]:25) with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1cTnDT-0006JH-8z  for idr@ietf.org (return-path ); Wed, 18 Jan 2017 10:11:43 +0000
Received: from SRVGREXMB01.claranet.local ([fe80::64bc:5d10:5203:a830]) by SRVGREXCAS02.claranet.local ([::1]) with mapi id 14.03.0319.002; Wed, 18 Jan 2017 10:05:30 +0000
From: David Freedman 
To: "idr@ietf.org" 
Thread-Topic: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
Thread-Index: AQHScXJl3V8T7TeeEUy3BnJjuTuoAA==
Date: Wed, 18 Jan 2017 10:05:29 +0000
Message-ID: <79F83DD9-9EB0-4060-AB2E-1694F9A77AA4@uk.clara.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1e.0.170107
x-originating-ip: [172.26.6.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <27E3A4B2D6A5924E87E77E0B95A3FDA5@claranet.local>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 18 Jan 2017 10:11:52 -0000

PiBUaGlzIGJlZ2lucyBhIDIgd2VlayBXRyBMYXN0IENhbGwgZm9yIGRyYWZ0LWlldGYtaWRyLXNo
dXRkb3duLTAyLnR4dA0KDQpTdXBwb3J0Lg0KDQo+IE9wZXJhdG9ycyBzaG91bGQgZXhhbWluZSBp
ZiBmcmVlZm9ybSBVVEYtOCBlbmNvZGVkIHN0cmluZyBhcyBkZXNjcmliZWQgbWVldHMgdGhlaXIg
b3BlcmF0aW9uYWwgbmVlZHMuDQoNCkRvbm5pbmcgbXkgb3BlcmF0b3IgaGF0LCBJIGJlbGlldmUg
c28sIHRvIHJlLWl0ZXJhdGUgU2FuZGVyJ3MgY29tbWVudCwgd2UgbmVlZCB0byBiZSBhYmxlIHRv
IGRlc2NyaWJlIHdoYXQgaXMgZ29pbmcgb24sIGFuZCB3ZSBtb3N0IGNlcnRhaW5seSBuZWVkIHRv
IGRvIHNvIHdpdGggVVRGLTggZW5jb2RpbmcuDQoNCkRhdmUuDQoNCg0KDQo=


From nobody Wed Jan 18 02:17:48 2017
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 524C11293FB for ; Wed, 18 Jan 2017 02:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lamehost-it.20150623.gappssmtp.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 6Ajv_PZlSgvM for ; Wed, 18 Jan 2017 02:17:45 -0800 (PST)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496AB126BF7 for ; Wed, 18 Jan 2017 02:17:45 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id x75so5107797vke.2 for ; Wed, 18 Jan 2017 02:17:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lamehost-it.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lqx+xoxTlbEJtmPwolNr6OTN6DfwHo27krnbkr9T/Qk=; b=gypgH71mSIMFgw6WThXOy5usOmtB2/1YlzjLk7zcBDZhkee84pZxF4XdLyYOYqSjPg BaTqZHE10beeb0pag0pRIZlte68GuDsOraiXvjTWew0zhpaYAvoDjb8mHVYRTnUPxQpD vdE+KvSMihc6bQzXoWWff/JjWFzGtfD70Bl31v6bXr3NSqIrDNEHVPqLzftrNLQpuXMe LGu781bjRa2tDCgFNppbul4b5QF4uxXuwWSfRntzUkBcfYV0Af5THLCmeUdF4VVMQbTH jPY1bt7bVbTRrKaExnOfxRQLflu80AnrRaNFSSmc3eU4OSL3L0CTIlRzmMBdOF74a/l7 hiwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lqx+xoxTlbEJtmPwolNr6OTN6DfwHo27krnbkr9T/Qk=; b=cjXduvYVmldIJ4xbqaotJFhsErH3GRlx28wOtF/vuOuInJqNu+fpHAsbyhFUD8wnW0 F8vOPX1L6EeBvCHLWRYlQRh12fKnz0mFjbKeTOeVhkJQnTY8d29pXuJEwLkTs1WaUzwS sP2MuUBfd+Edc03OE4sAJsq54FRkWpXlL1pB5F1yiL8bltB21wUiJu7sXm0exgQxJNNs lHjc+78p1q4DYOMa4I/3ltSRKL8HzOw3QCYX+Q2QPX86R4j9/e57m6eVB1mz6DBQJASh BLx4o/KzOtmgrVOaVPFHvSarSI40sHtsaEMIlVS93Vl7NCoBlXHvzSKDbVZkgusqDtWl N22A==
X-Gm-Message-State: AIkVDXLenaBnHtqnqKM34PJdd3zr+KvGpvxgsgjS1sFWnNQaeEBLUhTsWCN2qYyhVlTF25yXJJ9p4Y7/QNFJbw==
X-Received: by 10.31.183.136 with SMTP id h130mr801724vkf.131.1484734664297; Wed, 18 Jan 2017 02:17:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.52.214 with HTTP; Wed, 18 Jan 2017 02:17:43 -0800 (PST)
X-Originating-IP: [95.252.41.226]
In-Reply-To: <79F83DD9-9EB0-4060-AB2E-1694F9A77AA4@uk.clara.net>
References: <79F83DD9-9EB0-4060-AB2E-1694F9A77AA4@uk.clara.net>
From: Marco Marzetti 
Date: Wed, 18 Jan 2017 11:17:43 +0100
Message-ID: 
To: David Freedman 
Content-Type: text/plain; charset=UTF-8
Archived-At: 
Cc: "idr@ietf.org" 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 18 Jan 2017 10:17:47 -0000

Support

On Wed, Jan 18, 2017 at 11:05 AM, David Freedman
 wrote:
>> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
>
> Support.
>
>> Operators should examine if freeform UTF-8 encoded string as described meets their operational needs.
>
> Donning my operator hat, I believe so, to re-iterate Sander's comment, we need to be able to describe what is going on, and we most certainly need to do so with UTF-8 encoding.
>
> Dave.
>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr



-- 
Marco


From nobody Wed Jan 18 03:36:52 2017
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 A03D0129439; Wed, 18 Jan 2017 03:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 FO6C3g6mYDZU; Wed, 18 Jan 2017 03:36:49 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC30B12941E; Wed, 18 Jan 2017 03:36:48 -0800 (PST)
X-Envelope-To: draft-ietf-idr-shutdown@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v0IBai7Y068365 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Jan 2017 11:36:45 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <587F534B.4000200@foobar.org>
Date: Wed, 18 Jan 2017 11:36:43 +0000
From: Nick Hilliard 
User-Agent: Postbox 5.0.9 (Macintosh/20161202)
MIME-Version: 1.0
To: Susan Hares 
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 18 Jan 2017 11:36:50 -0000

Susan Hares wrote:
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> (1/17/2017 to 1/31/2017).  Section 7 of this document lists the
> implementations that have been created for this BGP functionality.  
> These include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer),
> and tcpdump

definitely support.  This is really useful from an operational point of
view.

> Operators should examine if freeform UTF-8 encoded string as described
> meets their operational needs.  

yes, UTF8 is a sensible choice here.

Nick


From nobody Wed Jan 18 11:38:57 2017
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 33E22129881; Wed, 18 Jan 2017 11:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nordu.net
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 stfBm7jR34Nx; Wed, 18 Jan 2017 11:38:50 -0800 (PST)
Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [IPv6:2001:6b0:8:2::202]) (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 BEB05129871; Wed, 18 Jan 2017 11:38:49 -0800 (PST)
Received: from smtp1.nordu.net (smtp1.nordu.net [IPv6:2001:948:4:6::32]) by e-mailfilter02.sunet.se (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id v0IJckJB008372 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Jan 2017 20:38:46 +0100
Received: from kerio.nordu.net (kerio.nordu.net [109.105.113.41]) by smtp1.nordu.net (8.14.7/8.14.7) with ESMTP id v0IJcgAO027055 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Jan 2017 19:38:45 GMT
VBR-Info: md=nordu.net; mc=all; mv=swamid.se
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nordu.net; s=default; t=1484768326; bh=NryGbSIDw/nM7iPn8i6YawGwr+uZTx+E/g3TRozX4JA=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=E16sdGtE2yU2VDrQOhJGrl3iRDHnAw6pO2+7ZgUGKh3SJDu4Rarw9wi2zl0DoLhvR x+N5iJ7RQldPGNlvb8ZE3QzrWRuBsfWVWVS50xlpGNkQPAhhXggYW0EWx1ePwgyu4h CqWBEUeHsrRtOxDm9PHaTx9j3q+9hcMZqhMVK7AU=
X-Footer: bm9yZHUubmV0
Received: from MacBook-Pro-4.local ([82.117.107.36]) (authenticated user hugge@nordu.net) by kerio.nordu.net with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128 bits)); Wed, 18 Jan 2017 20:38:42 +0100
To: Susan Hares 
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
From: =?UTF-8?Q?Fredrik_Korsb=c3=a4ck?= 
Message-ID: 
Date: Wed, 18 Jan 2017 20:38:28 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bT46kTQvHIchtOq9NagcILV0RTOhpAdrP"
X-Scanned-By: CanIt (www . roaringpenguin . com)
X-Scanned-By: MIMEDefang 2.74 on 109.105.111.32
X-p0f-Info: os=unknown unknown, link=Ethernet or modem
X-CanIt-Geo: ip=109.105.113.41; country=SE; latitude=59.3247; longitude=18.0560; http://maps.google.com/maps?q=59.3247,18.0560&z=6
X-CanItPRO-Stream: outbound-nordu-net:outbound (inherits from outbound-nordu-net:default, nordu-net:default, base:default)
X-Canit-Stats-ID: 0aSxTCKt8 - 5d62df1174d2 - 20170118
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
Received-SPF: neutral (e-mailfilter02.sunet.se: 109.105.113.41 is neither permitted nor denied by domain hugge@nordu.net) receiver=e-mailfilter02.sunet.se; client-ip=109.105.113.41; envelope-from=; helo=smtp1.nordu.net; identity=mailfrom
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 18 Jan 2017 19:38:55 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bT46kTQvHIchtOq9NagcILV0RTOhpAdrP
Content-Type: multipart/mixed; boundary="DGHgp0snk06kQjFOfeG30flOgwb48bHkN";
 protected-headers="v1"
From: =?UTF-8?Q?Fredrik_Korsb=c3=a4ck?= 
To: Susan Hares 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Message-ID: 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to
 1/31/2017)
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>

--DGHgp0snk06kQjFOfeG30flOgwb48bHkN
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 17/01/17 22:04, Susan Hares wrote:
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt (1=
/17/2017 to 1/31/2017).  Section 7 of this document lists the implementat=
ions that have been created for this BGP functionality.   These include: =
ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and tcpdump
>=20
> =20
>=20
>    o  ExaBGP [1 ]
>=20
>    o  pmacct [2 ]
>=20
>    o  OpenBGPD [3 ]
>=20
>    o  Wireshark [4 ] (packet analyser)
>=20
> =B7         tcpdump [5 ], (alt) [6 ] (packet analyser)
>=20
> =20
>=20
> Operators should examine if freeform UTF-8 encoded string as described =
meets their operational needs. =20
>=20
> =20
>=20
> Sue Hares
>=20
> WG Co-chair
>=20
>=20
>=20
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

Full support from my corner aswell (as2603 / as1653). This would greatly =
benefit us when doing a planned maintenance for example and be able to se=
nd out notifications to all connected partners with our public ticketnumb=
er, a describing text and a end-time. Freeform UTF-8 is a perfect fit for=
 this aswell so please keep that in.

A big kudos aswell to the opensource community to get this in quickly. No=
w i need to go back and convince both Juniper and Arista which is my weap=
ons of choice that this should get in there aswell so we can have a firm =
implementation of this across the board within the year.

--=20
Fredrik "hugge" Korsb=E4ck


--DGHgp0snk06kQjFOfeG30flOgwb48bHkN--

--bT46kTQvHIchtOq9NagcILV0RTOhpAdrP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYf8Q4AAoJEESmVfUlgciTkDQIAIKh1aIHk5k4wZmaBHbmaeOF
v+EcBjnBswjLFtr4nngOmH/eeMsSLpAeibs42gQLqZvaYr20G4qw1+33+mqrejTo
YTJwPsNM25X2M5bWbiFDfKeGXWo3dAk1KlxWWG4b/2BZGy8zLJNQcc1rC4/IXGkX
5m/PqEY4LvIG90PtzyPwxV6FbpTcuLKHpGaZ8wkKtFZh236UnVXUURWNgvKI2+T0
NGzBybNOkqyHkRiue8yR34sgSfF4KPENJTARr4PXL3jFesL7SUzRMDGWQH1m2wjb
BNYSnTpa/6sGpR4GWMQUly+nQ/dDaT2xIsCGDzjUWlGUSyKrZGFjuSu/vlkvncU=
=HXvs
-----END PGP SIGNATURE-----

--bT46kTQvHIchtOq9NagcILV0RTOhpAdrP--


From nobody Wed Jan 18 13:54:18 2017
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 5B1211294E6; Wed, 18 Jan 2017 13:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 R4nZ203Tmz5m; Wed, 18 Jan 2017 13:54:15 -0800 (PST)
Received: from shannon.7bits.nl (shannon.7bits.nl [89.188.0.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57A0D129437; Wed, 18 Jan 2017 13:54:15 -0800 (PST)
Received: from [192.168.137.1] (unknown [92.110.143.62]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: peter) by shannon.7bits.nl (Postfix) with ESMTPSA id 19848C1B96; Wed, 18 Jan 2017 22:54:12 +0100 (CET)
From: "Peter van Dijk" 
To: "Susan Hares" 
Date: Wed, 18 Jan 2017 22:54:19 +0100
Message-ID: <98933514-362A-42A0-A803-236033B5131A@powerdns.com>
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5319)
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 18 Jan 2017 21:54:17 -0000

Hello,

On 17 Jan 2017, at 22:04, Susan Hares wrote:

> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> (1/17/2017 to 1/31/2017).  Section 7 of this document lists the
> implementations that have been created for this BGP functionality.   
> These
> include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and 
> tcpdump
>    o  OpenBGPD [3

I did the openbgpd implementation of draft-ietf-idr-shutdown. Please 
find my
implementation report below.

A functional description of the implementation can be found at
http://marc.info/?l=openbsd-tech&m=148390348126153&w=2 . Note that the 
final
version of the patch is a few mails down in that thread (and phessler@ 
did some
last whitespace fixes before committing it to OpenBSD CVS). In short, 
the
openbgpd implementation is complete; it can send shutdown communications 
from
the config file and from the command line; it logs received 
communications to
syslog and exposes them in various forms of 'bgpctl .. show'.

During implementation, I have found the draft very clear to read, and 
there were
no ambiguities in how an implementation was supposed to work. In every 
one of
the few situations I had doubts arising from interoperability testing 
with other
fresh implementations, it turned out there was a bug in the other 
implementation
and each time this was quickly corrected on the other side after a 
closer
reading of the draft or the involved code.

Implementation took a few evenings, spread out over weeks, showing that 
the
cognitive load involved with understanding this draft is quite low.

Development was done on OpenBSD 6.0 (as openbgpd has not been ported to 
other
platforms). The work was divided in logical pieces (log incoming 
messages;
remember them for bgpctl show; send them from bgpctl neighbor X down 
REASON;
send them from the configuration file on a reload+refresh).

Interoperability was continuously tested against the then-current
implementations of -shutdown in exabgp and pmacct pmbgpd, running on a 
nearby
Linux VM, as at that time pmacct only had support for sending a shutdown
message, and exabgp was only able to receive shutdown messages. Various 
minor
bugs in the exabgp and pmacct implementations surfaced and were fixed 
during
this process.

Unprintable characters (both of the 'control' and the 'UTF-8' nature) 
were
easily dealt with via the vis(3) (http://man.openbsd.org/vis.3) facility
available on all BSDs, in octal mode as is also used in C string 
constants.
Incidentally Debian has a 'libbsd' that provides it. A standalone 
implementation
would not be hard to do either. vis-encoded strings can be decoded by 
'unvis' on
the commandline, or by simply pasting them into a Python interpreter. 
This way
full Unicode support is achieved without having to worry about 'what 
encoding is
syslog actually in'.

As an example, the Unicode unicorn (U+1F984), encoded on the wire in 
UTF-8 (as
the draft specifies), yields a syslog message such as

     neighbor 165.254.255.26: received shutdown reason: 
"\360\237\246\204"

Running

     echo "\360\237\246\204" | unvis

on an UTF-8 capable terminal, or typing

     print("\360\237\246\204".decode('utf-8'))

into a Python2 prompt, will recover said unicorn. 🦄

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/


From nobody Wed Jan 18 14:28:59 2017
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 A288B1295B8 for ; Wed, 18 Jan 2017 14:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 yJpV3ZpUWbPw for ; Wed, 18 Jan 2017 14:28:55 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FB971295B5 for ; Wed, 18 Jan 2017 14:28:55 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id c206so48901812wme.0 for ; Wed, 18 Jan 2017 14:28:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=7dzebiMnudpietRribmW/mCAYC1pbjFOXPjut77n6S8=; b=LonuCvEn57ixvvufrZ1Y4PvjSXS1uHsJ9QRtJPuage94M8sSHULqSxXWVT3A7twmMp xhX6v3z4NdYpr+kHb5YvIfQt/RD4EdjmiVtVVtd8gLjdhnu9FtKpR87A1u2H9b71VffP +sIGv1LC2OGtZhxhh5Ny59CqJdfJ1ByiBcb6vQ48yX7EtK1oHbtNGZeuGyIkUdo7YSFl y9WRIqvEwDUnQvFH8fNTWW0Y61q/fev0AXOPGrBpBCA63qiJxLjrWArsOV6aN8KPQwqz QOHpSuZYigKoAyvqI0o6L9Bz7vLZBsTrjiaRS8SFtUCmGj4wFu2qxts3ZRRcgmBpyLCB Vd3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=7dzebiMnudpietRribmW/mCAYC1pbjFOXPjut77n6S8=; b=S3H6Auq/51X51wSAsnQDOdSh/4njLwLC58Truem9QMfP6W5a1Px0o8FN7YkN+l8aQZ Up6soSnlyTJ3m6sWQVjGoCLopIacV0PaBcZxvyxsW/w6hHUbRP1paFfQa9oT5j80VU+a tyxtyVRSzj/PWJcTrM56cvJxeePbJ+fP6uCRX6/cj74M+r/N/efgFSFbPz26Bni1sLRM qCd1GZ9FRiEyvl7JN67vrdiusKanCo+gf+HJyp+RL39no11HN9XsIjF1YpoBdZl38T2R qb9f4s9kZ01+8Mrlcrvx3S3HU3zloUX6fMuV9hQYN64cPgzC1hZm5v9Ughee6m8Ypi+A Qe+w==
X-Gm-Message-State: AIkVDXIsTzyNBPPmATyZuSCt2KVUNqiZUPadTEUPSupBFKmxUFDtF/UHd/zcxyAaoV8HiQ==
X-Received: by 10.223.128.77 with SMTP id 71mr4642222wrk.48.1484778533531; Wed, 18 Jan 2017 14:28:53 -0800 (PST)
Received: from localhost ([188.206.110.238]) by smtp.gmail.com with ESMTPSA id y65sm44966162wmb.5.2017.01.18.14.28.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Jan 2017 14:28:52 -0800 (PST)
Date: Wed, 18 Jan 2017 23:28:49 +0100
From: Job Snijders 
To: Peter van Dijk 
Message-ID: <20170118222849.GX1062@Vurt.local>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <98933514-362A-42A0-A803-236033B5131A@powerdns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <98933514-362A-42A0-A803-236033B5131A@powerdns.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org, Susan Hares 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 18 Jan 2017 22:28:57 -0000

Dear Peter,

On Wed, Jan 18, 2017 at 10:54:19PM +0100, Peter van Dijk wrote:
> On 17 Jan 2017, at 22:04, Susan Hares wrote:
> > This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> > (1/17/2017 to 1/31/2017).  Section 7 of this document lists the
> > implementations that have been created for this BGP functionality. These
> > include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and tcpdump
> 
> I did the openbgpd implementation of draft-ietf-idr-shutdown. Please find my
> implementation report below.
> 
> A functional description of the implementation can be found at
> http://marc.info/?l=openbsd-tech&m=148390348126153&w=2 . Note that the final
> version of the patch is a few mails down in that thread (and phessler@ did
> some last whitespace fixes before committing it to OpenBSD CVS). In short, the
> openbgpd implementation is complete; it can send shutdown communications from
> the config file and from the command line; it logs received communications to
> syslog and exposes them in various forms of 'bgpctl .. show'.
> 
> During implementation, I have found the draft very clear to read, and there
> were no ambiguities in how an implementation was supposed to work. In every
> one of the few situations I had doubts arising from interoperability testing
> with other fresh implementations, it turned out there was a bug in the other
> implementation and each time this was quickly corrected on the other side
> after a closer reading of the draft or the involved code.
> 
> Implementation took a few evenings, spread out over weeks, showing that the
> cognitive load involved with understanding this draft is quite low.
> 
> Development was done on OpenBSD 6.0 (as openbgpd has not been ported to other
> platforms). The work was divided in logical pieces (log incoming messages;
> remember them for bgpctl show; send them from bgpctl neighbor X down REASON;
> send them from the configuration file on a reload+refresh).
> 
> Interoperability was continuously tested against the then-current
> implementations of -shutdown in exabgp and pmacct pmbgpd, running on a nearby
> Linux VM, as at that time pmacct only had support for sending a shutdown
> message, and exabgp was only able to receive shutdown messages. Various minor
> bugs in the exabgp and pmacct implementations surfaced and were fixed during
> this process.
> 
> Unprintable characters (both of the 'control' and the 'UTF-8' nature) were
> easily dealt with via the vis(3) (http://man.openbsd.org/vis.3) facility
> available on all BSDs, in octal mode as is also used in C string constants.
> Incidentally Debian has a 'libbsd' that provides it. A standalone
> implementation would not be hard to do either. vis-encoded strings can be
> decoded by 'unvis' on the commandline, or by simply pasting them into a Python
> interpreter. This way full Unicode support is achieved without having to worry
> about 'what encoding is syslog actually in'.
> 
> As an example, the Unicode unicorn (U+1F984), encoded on the wire in UTF-8 (as
> the draft specifies), yields a syslog message such as
> 
>     neighbor 165.254.255.26: received shutdown reason: "\360\237\246\204"
> 
> Running
> 
>     echo "\360\237\246\204" | unvis
> 
> on an UTF-8 capable terminal, or typing
> 
>     print("\360\237\246\204".decode('utf-8'))
> 
> into a Python2 prompt, will recover said unicorn. 🦄

Thank you for this write-up!

Kind regards,

Job


From nobody Thu Jan 19 00:15:30 2017
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 E6D7312940F; Thu, 19 Jan 2017 00:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 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_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bit.nl
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 JHGMkBW_J0vk; Thu, 19 Jan 2017 00:15:26 -0800 (PST)
Received: from smtp.bit.nl (smtp.bit.nl [IPv6:2001:7b8:3:5::25:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6FD11293F9; Thu, 19 Jan 2017 00:15:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bit.nl; s=smtp01; h=Content-Transfer-Encoding:Mime-Version:Content-Type:References: In-Reply-To:Date:To:From:Subject:Message-ID; bh=aIRHT5nojZS1V0ivWBhOpToRb/ebw30oLsijpWkpTAE=; b=d0AV8s3+v0yHbvkeOh+SCrGlQg PEAol9eEPMGD3AZC/UqpmXC4MUgW+0f7gzJD2oTqCTRD/QllTd23e1gbHtrgR0IpFhyf10JEq0BmQ QWLv+PJusk8GMppchSFZo8I8RHleV1/hqROrCt7l+Hvm+HfTo2FVBPk4NYy8iqy2nN+c9cUTMAeMm lUP0KNVITyhsPNuAujPUkaC7Aa1KN2JOj2sh5CJL2OF6bBntAlKIYouwVDBjvG9Lpl5eb//GTE0n+ VHP18aT19sJA5cuJtwsgAY119A9hw02WMpPJnyAAWbzNmydOaczMMAwLgG7rsbaatuw1xD0QIf9sZ +0JlEQgA==;
Received: from [2001:7b8:3:1000:921b:eff:fe8a:4cb1] (port=38422) by smtp2.smtp.dmz.bit.nl with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1cU7sS-0000Cb-3r; Thu, 19 Jan 2017 09:15:24 +0100
Message-ID: <1484813714.8565.74.camel@moridin>
From: Teun Vink 
To: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Date: Thu, 19 Jan 2017 09:15:14 +0100
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
Organization: BIT BV
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4-0ubuntu2 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 19 Jan 2017 08:15:29 -0000

On Tue, 2017-01-17 at 16:04 -0500, Susan Hares wrote:
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> (1/17/2017 to 1/31/2017).  Section 7 of this document lists the
> implementations that have been created for this BGP functionality.
> These include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer),
> and tcpdump
> 
>  
>    o  ExaBGP [1]
>    o  pmacct [2]
>    o  OpenBGPD [3]
>    o  Wireshark [4] (packet analyser)
> ·         tcpdump [5], (alt) [6] (packet analyser)
> 
>  
> 
> Operators should examine if freeform UTF-8 encoded string as described
> meets their operational needs.  


Full support here, I really hope this will become a truly accepted and
implemented operational standard and that it will reduce the number of
"hey I see a peering session drop" mails and calls we have to deal with
after every maintenance. 

UTF-8 sounds like a sane choice for string encoding.

Best regards,
-- 
Teun Vink
BIT           | teun@bit.nl     | +31 318 648 688
KvK: 09090351 | GPG: 0x5A04F4E2 | RIPE: TEUN-RIPE



From nobody Thu Jan 19 01:46:27 2017
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 74C9B120727; Thu, 19 Jan 2017 01:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 8XUZ5VIticj9; Thu, 19 Jan 2017 01:46:25 -0800 (PST)
Received: from mail.i3d.net (mail.i3d.nl [213.163.77.240]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BF7A127ABE; Thu, 19 Jan 2017 01:39:40 -0800 (PST)
X-Footer: aTNkLm5s
Received: from localhost ([127.0.0.1]) by mail.i3d.net with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128 bits)); Thu, 19 Jan 2017 10:39:38 +0100
To: Susan Hares , idr@ietf.org
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
From: "i3D.net - Martijn Schmidt" 
Organization: i3D.net
Message-ID: <01fb141e-fc5b-338e-6f90-70cfb90f4527@i3d.net>
Date: Thu, 19 Jan 2017 10:39:38 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
Content-Type: multipart/alternative; boundary="------------81DA8A4F7A9F41F052692231"
Archived-At: 
Cc: draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 19 Jan 2017 09:46:26 -0000

This is a multi-part message in MIME format.
--------------81DA8A4F7A9F41F052692231
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

Hello,

On 01/17/2017 10:04 PM, Susan Hares wrote:
>
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> (1/17/2017 to 1/31/2017).  Section 7 of this document lists the
> implementations that have been created for this BGP functionality.  
> These include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer),
> and tcpdump
>
>  
>    o  ExaBGP [1
> ]
>    o  pmacct [2
> ]
>    o  OpenBGPD [3
> ]
>    o  Wireshark [4
> ]
> (packet analyser)
> ·         tcpdump [5
> ], (alt)
> [6 ]
> (packet analyser)
>
>  
>
> Operators should examine if freeform UTF-8 encoded string as described
> meets their operational needs.  
>
>  
>
> Sue Hares
>
> WG Co-chair
>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

I hope this will help to significantly reduce the amount of unnecessary
e-mails about missed maintenance tickets coming up on the various IXP
mailing lists over the next couple of years. UTF-8 freeform will allow
operators to change the format to whatever is needed for the use-case,
future-proofing the standard.

Best regards,
Martijn Schmidt
i3D.net / AS49544

--------------81DA8A4F7A9F41F052692231
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit


  
    
  
  
    Hello,

    

    On 01/17/2017 10:04 PM, Susan Hares wrote:

    

      
      
      
      

        
This begins a 2 week WG Last Call for
          draft-ietf-idr-shutdown-02.txt (1/17/2017 to 1/31/2017).
           Section 7 of this document lists the implementations that
          have been created for this BGP functionality.   These include:
          ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and
          tcpdump

        
 

        
   o  ExaBGP [1]

        
   o  pmacct [2]

        
   o  OpenBGPD [3]

        
   o  Wireshark [4] (packet analyser)

        
·         tcpdump [5], (alt) [6] (packet analyser)

        
 

        
Operators should examine if freeform UTF-8
          encoded string as described meets their operational needs.  

        
 

        
Sue Hares

        
WG Co-chair 

      

      

      

      

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


    

    

    I hope this will help to significantly reduce the amount of
    unnecessary e-mails about missed maintenance tickets coming up on
    the various IXP mailing lists over the next couple of years. UTF-8
    freeform will allow operators to change the format to whatever is
    needed for the use-case, future-proofing the standard.

    

    Best regards,

    Martijn Schmidt

    i3D.net / AS49544

  


--------------81DA8A4F7A9F41F052692231--


From nobody Thu Jan 19 09:00:35 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF545129810; Thu, 19 Jan 2017 09:00:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148484523397.10336.16221440109637630927.idtracker@ietfa.amsl.com>
Date: Thu, 19 Jan 2017 09:00:33 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-shutdown-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 19 Jan 2017 17:00:34 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : BGP Administrative Shutdown Communication
        Authors         : Job Snijders
                          Jakob Heitz
                          John Scudder
	Filename        : draft-ietf-idr-shutdown-03.txt
	Pages           : 7
	Date            : 2017-01-19

Abstract:
   This document enhances the BGP Cease NOTIFICATION message
   "Administrative Shutdown" subcode for operators to transmit a short
   freeform message to describe why a BGP session was shutdown.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-shutdown-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jan 19 09:15:26 2017
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 51ABD12947D for ; Thu, 19 Jan 2017 09:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.134
X-Spam-Level: 
X-Spam-Status: No, score=-5.134 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_SOFTFAIL=0.665] autolearn=ham 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 tJMIn_nEd1Jt for ; Thu, 19 Jan 2017 09:15:22 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 A67B4129461 for ; Thu, 19 Jan 2017 09:15:22 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cUGIz-000Bak-El (job@us.ntt.net); Thu, 19 Jan 2017 17:15:22 +0000
Date: Thu, 19 Jan 2017 18:15:18 +0100
From: Job Snijders 
To: idr@ietf.org
Message-ID: <20170119171518.GS1055@Vurt.local>
References: <148484523397.10336.16221440109637630927.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148484523397.10336.16221440109637630927.idtracker@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: 
Subject: Re: [Idr] I-D Action: draft-ietf-idr-shutdown-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 19 Jan 2017 17:15:24 -0000

Dear IDR,

Changelog from -02 to -03:

    o Incorporate feedback from the shepherd review
    o Improve wording regarding the Length field
    o Point out that length value and character count will not
      nessecarily be the same

No functional changes to normative constructs were made.

Kind regards,

Job

On Thu, Jan 19, 2017 at 09:00:33AM -0800, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Inter-Domain Routing of the IETF.
> 
>         Title           : BGP Administrative Shutdown Communication
>         Authors         : Job Snijders
>                           Jakob Heitz
>                           John Scudder
> 	Filename        : draft-ietf-idr-shutdown-03.txt
> 	Pages           : 7
> 	Date            : 2017-01-19
> 
> Abstract:
>    This document enhances the BGP Cease NOTIFICATION message
>    "Administrative Shutdown" subcode for operators to transmit a short
>    freeform message to describe why a BGP session was shutdown.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-idr-shutdown-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-03
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


From nobody Thu Jan 19 09:20:33 2017
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 9AFDC129447; Thu, 19 Jan 2017 09:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham 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 f-wOS7alCYsB; Thu, 19 Jan 2017 09:20:30 -0800 (PST)
Received: from argon.someaddress.net (argon.someaddress.net [194.117.226.142]) by ietfa.amsl.com (Postfix) with ESMTP id 94E4012942F; Thu, 19 Jan 2017 09:20:30 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by argon.someaddress.net (Postfix) with ESMTP id B2B82BCA27E; Thu, 19 Jan 2017 17:20:29 +0000 (UTC)
Received: from argon.someaddress.net ([127.0.0.1]) by localhost (argon.someaddress.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JFQVUSy9hIqF; Thu, 19 Jan 2017 17:20:29 +0000 (UTC)
Received: from ukltp01119.6dg.local (office.noc.uksolutions.net [217.10.128.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by argon.someaddress.net (Postfix) with ESMTPS id 8C3D8BCA274; Thu, 19 Jan 2017 17:20:29 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Tom Hodgson 
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
Date: Thu, 19 Jan 2017 17:20:28 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <301D46C1-6C95-458E-B33D-C5AFEA3112D3@someaddress.net>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
To: idr@ietf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: 
Cc: draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 19 Jan 2017 17:20:31 -0000

Hi,

> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt =
(1/17/2017 to 1/31/2017).  Section 7 of this document lists the =
implementations that have been created for this BGP functionality.   =
These include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), =
and tcpdump
>  [snip]=20
> Operators should examine if freeform UTF-8 encoded string as described =
meets their operational needs. =20

Support this as a useful tool, especially for networks who have not =
progressed fully down the full automation path yet and have to rely on =
manual view and intervention of session events. With operator hat on =
UTF8 seems sensible.=


From nobody Thu Jan 19 10:20:56 2017
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 BCC6D129499 for ; Thu, 19 Jan 2017 10:20:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no 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 OUORQyBlvjGB for ; Thu, 19 Jan 2017 10:20:55 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDE481293DB for ; Thu, 19 Jan 2017 10:20:54 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.36.89.227; 
From: "Susan Hares" 
To: "'Job Snijders'" , 
References: <148484523397.10336.16221440109637630927.idtracker@ietfa.amsl.com> <20170119171518.GS1055@Vurt.local>
In-Reply-To: <20170119171518.GS1055@Vurt.local>
Date: Thu, 19 Jan 2017 13:16:43 -0500
Message-ID: <036601d27280$3059d660$910d8320$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFZKZo/Yj0u6I2VY56p4CciGf0lcQKqiWAuoh1YvbA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: 
Subject: Re: [Idr] I-D Action: draft-ietf-idr-shutdown-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 19 Jan 2017 18:20:55 -0000

Job: 

Thank you for this revision.  It addresses the concerns this shepherd had. 

Sue Hares 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Job Snijders
Sent: Thursday, January 19, 2017 12:15 PM
To: idr@ietf.org
Subject: Re: [Idr] I-D Action: draft-ietf-idr-shutdown-03.txt

Dear IDR,

Changelog from -02 to -03:

    o Incorporate feedback from the shepherd review
    o Improve wording regarding the Length field
    o Point out that length value and character count will not
      nessecarily be the same

No functional changes to normative constructs were made.

Kind regards,

Job

On Thu, Jan 19, 2017 at 09:00:33AM -0800, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Inter-Domain Routing of the IETF.
> 
>         Title           : BGP Administrative Shutdown Communication
>         Authors         : Job Snijders
>                           Jakob Heitz
>                           John Scudder
> 	Filename        : draft-ietf-idr-shutdown-03.txt
> 	Pages           : 7
> 	Date            : 2017-01-19
> 
> Abstract:
>    This document enhances the BGP Cease NOTIFICATION message
>    "Administrative Shutdown" subcode for operators to transmit a short
>    freeform message to describe why a BGP session was shutdown.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-idr-shutdown-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-03
> 
> 
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at
tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

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


From nobody Fri Jan 20 01:16:31 2017
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 DC444129ABF for ; Fri, 20 Jan 2017 01:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level: 
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham 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 H8bgn8M_bJ5p for ; Fri, 20 Jan 2017 01:16:28 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CBF3129408 for ; Fri, 20 Jan 2017 01:16:27 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CZE21643; Fri, 20 Jan 2017 09:16:23 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 20 Jan 2017 09:16:22 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Fri, 20 Jan 2017 17:16:11 +0800
From: Zhuangshunwan 
To: "idr@ietf.org" 
Thread-Topic: Regarding encoding examples from draft-ietf-idr-flow-spec-v6-07
Thread-Index: AdJy/dXJyloMBDxrS82oXMQyTXl0Hg==
Date: Fri, 20 Jan 2017 09:16:47 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858C883017C@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.86.254]
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858C883017CNKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5881D567.02E2, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8504ed7f750a29f93e540d494d6ce296
Archived-At: 
Subject: [Idr] Regarding encoding examples from draft-ietf-idr-flow-spec-v6-07
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 20 Jan 2017 09:16:30 -0000

--_000_19AB2A007F56DB4E8257F949A2FB9858C883017CNKGEML515MBXchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Authors and WG,

I have some confusion and hope to get your help.

The following examples come from draft-ietf-idr-flow-spec-v6-07:
"
   The following example demonstrates the new prefix encoding for: "all
   packets to ::1234:5678:9A00:0/64-104 from 192::/8 and port {range
   [137, 139] or 8080}".  In the destination prefix, "80-" represents
   the prefix offset of 80 bits.  In this exmaple, the 0 offset is
   omitted from the printed source prefix.

    +---------------------------+-------------+-------------------------+
    | destination               | source      | port                    |
    +---------------------------+-------------+-------------------------+
    | 0x01 68 50 12 34 56 78 9A | 02 00 08 c0 | 04 03 89 45 8b 91 1f 90 |
    +---------------------------+-------------+-------------------------+
"
I have two questions:

1)  For destination filter example, the given offset value is 0x50, should

it be 0x40 ?



2)  For source filter example, per my understanding, the prefix length valu=
e

is 0x08, the offset value is 0x00, so the source filter should be encoded

as 0x02 08 00 C0, not 0x02 00 08 c0 ?




Thanks,

Shunwan


--_000_19AB2A007F56DB4E8257F949A2FB9858C883017CNKGEML515MBXchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable











H=
i Authors and WG,


<=
o:p> 


I=
 have some confusion and hope to get your help.


<=
o:p> 


T=
he following examples come from dr=
aft-ietf-idr-flow-spec-v6-07:


&=
#8220;


&=
nbsp;  The following example demonstrates the new prefix encoding for:=
 "all


&=
nbsp;  packets to ::1234:5678:9A00:0/64-104 from 192::/8 and port {ran=
ge


&=
nbsp;  [137, 139] or 8080}".  In the destination prefix, &qu=
ot;80-" represents


&=
nbsp;  the prefix offset of 80 bits.  In this exmaple, the 0 offs=
et is


&=
nbsp;  omitted from the printed source prefix.


<=
o:p> 


&=
nbsp;   +---------------------------+-------------+--=
-----------------------+


&=
nbsp;   | destination       &n=
bsp;       | source    &n=
bsp; | port          &nbs=
p;         |


&=
nbsp;   +---------------------------+-------------+--=
-----------------------+


&=
nbsp;   | 0x01 68 50 12 34 56 78 9A | 02 00 08 c0 | 04 03 89 45 8=
b 91 1f 90 |


&=
nbsp;   +---------------------------+-------------+--=
-----------------------+


&=
#8220;


I=
 have two questions:



1) 
For destination filter example, the given offset value is 0x50, shou=
ld



=
it be 0x40
?


=
 =




2) 
For source filter example, per my understanding, the prefix length v=
alue



=
is 0x08, the offset valu=
e is 0x00, so the source filter should be encoded



=
as 0x02 08 00 C0, not 0x=
02 00 08 c0 ?


=
 =



<=
o:p> 


Thanks,


Shunwan


<=
o:p> 






--_000_19AB2A007F56DB4E8257F949A2FB9858C883017CNKGEML515MBXchi_--


From nobody Sat Jan 21 07:03:34 2017
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 13899129ACD for ; Sat, 21 Jan 2017 07:03:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.058
X-Spam-Level: 
X-Spam-Status: No, score=-3.058 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.156, 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=junipernetworks.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 pqSfMT0-gv1H for ; Sat, 21 Jan 2017 07:03:31 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0139.outbound.protection.outlook.com [104.47.37.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B9D3129A97 for ; Sat, 21 Jan 2017 07:03:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=jh27ac5e1yciZ2AEMH8NWSbfEK1ufxMdtSR1n0C8K+8=; b=EEOA4nr3af7+bBw4rBf0P5J2FHqDKDFAtc5h42OA+ACDNZvAVT3VCTZXG7emcVRYMtN8oUIs3beKTs0p/QsiSTUdTWRebSFaCQA+1eQfQK8Idk5n9UxE9m+aD2Z23rJatO4XcruXDGkv7QcvwWqBYaRMKgxSOGRKpH1J644AEKg=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=jgs@juniper.net; 
Received: from [172.29.97.95] (66.129.239.13) by BN3PR05MB2500.namprd05.prod.outlook.com (10.167.3.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.6; Sat, 21 Jan 2017 15:03:27 +0000
From: "John G. Scudder" 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID: <36E285C0-C716-437A-806D-A453273146DD@juniper.net>
Date: Sat, 21 Jan 2017 10:03:20 -0500
To: 
MIME-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Originating-IP: [66.129.239.13]
X-ClientProxiedBy: BY2PR08CA0082.namprd08.prod.outlook.com (10.163.62.178) To BN3PR05MB2500.namprd05.prod.outlook.com (10.167.3.135)
X-MS-Office365-Filtering-Correlation-Id: d720f74b-5c70-4609-77dd-08d4420ea8da
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN3PR05MB2500;
X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2500; 3:Y0c87wrrEvL7dgYyewEkHmrlw10jzl9fwCsN3asOWVPIZxjp87Hhz66QFg6VxznsCyWTs6LKTEdUpFb6lvahweo0ljKf4r01sk8FYmmO7Gzzo3OxwEu6BUFkLFCAfgTxMm9AGTj1HYhq19LlF+doXZ6QZcANZIAGDLzcAKK7Pkw6EvGsuQ4V85NeNkpGGeY5I+7OaflrC9jqeb8wmJoRWU+Eeh5i2Ynq4BGrE9Rsl+2MFV+tuC0pxKrhYVOoW3D5blWcMYH/TFPV2iIpxNh+dg==
X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2500; 25:cwrX47Qt0zqdfhj+hnKbcx/qoJEicinzh3ZHIVJnX8tKxValIj7WCkTstExgbPunchq0apTVKnObeISnVTAjrmWAlcg2Kkhg2SJD/Ty7FYDzENuqEtkhKusOt3cvSVfSsgW6iqpyEflvKCnEHgSkkL0drYxOuR2g7zf/RB+U34pXpOo0H4mnXwCPSYYEB5i/ILodqgUDLZ4piElINzyHqa6V7ZI10Qm+Bbiwn/0vk2UZClqUQFinmLtec37A4+UwueD4QRT4lqbvm900tocO13PZ3WPxUgWeL0xOSB2XB04b2CcpDeC3v3mv1v4rhxT4LUzwOpkVDzxiguhAR5Ij/Q+C5hvwWD4HOqh+kC08Ef+60LCYqtb29iS64kttvjYvTWe0QXwvA2xdC9B+hkR4DCAzQIVAlhEogmFOkEhjDJyRIcuRgujWvUIkQYsueAv57IUoUinxYvUUPgZWS2gm/7pWRLPceZOw6ZZ6c4V6/QmOJQZ4rinMMRbQaEsjaK3LrmsTblp1cu+1j/ZXTJLGJou+TPnqwHvs5x0vVJdfTB33zQgGH8fi5Ox8yg61o/X2LakNxIgGBDJxRL127frezjofPbXXnBdtjAhl/vnr+5bc++R/+T1txVw0ezk0G7k4JMT/ARiaoqW+YvdkCmuPilLnJbCmrXmdZYZl/vCwKSf3mMn3fyFH1kK/Oqk+MjxLwq4HoIkv0BPDRFkLz/S0U3YTtgyJH2c3OkJkzyi4jhHrlpAIRTF1+iyKOaC653O+
X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2500; 31:0i8fINxcC6NvIEm6qXaiVmWPFrp1i2znQq1lTcbFpJkhI8T22wOXGeJAsc1A+wkYFTigqfdSCXF/EixHh5iPJBvB+sGDtPg2OxidFAo/qAXJaz5/h7wH0t5qYHFuLgS7FYYZ1+/0t+dZHXb/4WXvbt9ZpS49ydQHfttUMDgEjn2v6gkiKKcCrC3wbJ3/EKXBgANv1UcFD6PJ+TvBO0CSjzHcVTas2riHLln3kMobxMEJCZ/D3nM7ie/daMQ7ktdqA7SWd8kj23OvNQnHd6zKEg==; 20:2AyNazjaTc81tumybEr9Ocezu7IWJAqvoaUqiMQ5CBFvmvJzlHIGnx2F+D7854lc/NHzcgk1CqZDGXQ79VuPp1fdQt1Nm8Vsff3DJ881RvWRVwdEKO6LwOq4ucsERMg5tUWJ1zMZQ2Gg0F4XDYpdUzwVfptRB7Cz8ckqcnJpx6V+jpoRqWB9+J1TZP0vmRsIF1b9DwFGhPEQ2Ov8EpxbE3kjIpArOtR5SteRu/3BVEJZMhCDaLgbp3d37c974cLK27tF0SWA0/i4YJBHrQIpR1zG6VHIeHxZdQ03YATOKNFox4yryI9RiXiJ4IW5yS6rVAkWfPwK6A3G5gS7GQgVPzYZml+C5zXyFPf2W3Hy3qcpy/KVjVpr1PDI6rNHRPX/4mJ5fJ2004W/FHyfwhRpc87/DM3xeRzMuPSN3qyhAI29wSJHNdkjWMtM7KsmZ4j10QgEQghRw5hladek4gmpt3s41/t/8ycDmSnOpOfrTtAAmRYREjZj2abHAW80fr5c
X-Microsoft-Antispam-PRVS: 
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123555025)(20161123562025)(20161123560025)(20161123564025)(6072148); SRVR:BN3PR05MB2500; BCL:0; PCL:0; RULEID:; SRVR:BN3PR05MB2500; 
X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2500; 4:tRlfBaGW2RgoOZ6Wnzlh8WC2NbDt8lE51BjeE5BKDWfQUuNYk7+eZ4NMA5cTYCNLx/GLEmNWnV9pwEu9Gw5Ek8ifSxSj5SAb49GqvsY4neX9gb2un1v09XOe5wNfzmHaDGcHZcdr45jM7cYYXmAo+aAHmoz51+vNnkEhNXLXLM26nQVXv9gKt/xAcDEdFgs+7fKAqtge05dFf121jrivD19xJFErNJs46XtjzFjBCFBn5wsOytU7zQkEVy9WEUilNVlrdI+U0DmmHQEkFmMCZLim7Wi0hDduwPeFFt9v6sfNNnW7eaGADipRKBdV2pTXGqyrwGcc1KTh0q78eNAvqebzCHNkqVeJLo2SsN8+D0IfiXW52eBH8ApBx8OQ42GDnHcvCDVCuKS6Ug6ggR8Aq5fm5VpRzuld2kpItdPBdkWXNjsEoxJpKSgiCFV7MG5bOXBGGZFOAqbFjxpi710YsmEA4L6UEi7kwoBETAugMmT7CclnrEpgBH+CnTFr/4CsDWUDDey/Z2fdc1pqVi1mdiVvHU6L6Mw1q6KV0pj9PVstw9oO98pBuXT+GJnMrNZqAQEbfyRwC70H4S4Jtuai7Q==
X-Forefront-PRVS: 01949FE337
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(6049001)(7916002)(39840400002)(39450400003)(39410400002)(39860400002)(39850400002)(189002)(53754006)(199003)(189998001)(106356001)(101416001)(107886002)(68736007)(5660300001)(92566002)(110136003)(2906002)(6916009)(6666003)(50986999)(7736002)(305945005)(23676002)(6116002)(42186005)(230783001)(3846002)(558084003)(36756003)(105586002)(57306001)(2351001)(450100001)(8676002)(66066001)(97736004)(53936002)(8746002)(47776003)(81166006)(33656002)(82746002)(6486002)(77096006)(81156014)(86362001)(50466002)(83716003)(50226002)(90366009)(25786008)(38730400001)(104396002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2500; H:[172.29.97.95]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTjNQUjA1TUIyNTAwOzIzOkY1bEtaS0wyRVNhLzRWNUlIQUVBNkxZSU1j?= =?utf-8?B?U2EyU2tOcnpkaE1BcVAxc3hTZlc3SUdWV3Q1YmU0blpYaEdsb0s0bitGMTBL?= =?utf-8?B?U0Rqa0xJNGhFZzZPSTJpMTNqeWlvODd0WXVSY0VubG93TG1lOUhJWlRqRC82?= =?utf-8?B?a0M3YVBCNTlWdTlWdVJ6ai9JZmdYclNBRWJGZlp3YXVUUFdSa0lkblEwbHJO?= =?utf-8?B?QlFZMkg2L0pMZk96dHQyQWNMWFAzQnFkWTdJbExpb3J2VnhpZ2lJc21BMVd2?= =?utf-8?B?WXBmSDVSZCtFWXBvSVZoQWhGcnBGeWNZSXJ1eFYrOTkvWFFLaE9xZXRkVlJS?= =?utf-8?B?L2IvZmV3NFZVUUFVc1N3V2dUa3RaRUltOWtNUGs0Tmx6L0VsWjhZMmVWRHpt?= =?utf-8?B?K1BYM2I2Yk9rZEd1RUN2bk1ieHlXQUdRajRlWGFldi9laFF1VSt6NFN0eVVY?= =?utf-8?B?ZTNCWFJZYTZZWVJuRFFSR2lEdHp1aFVxRFdNMEZQcFdySDNyNm52MFQ1V01Q?= =?utf-8?B?MDdXRmkxbWpKMzRQYWxFVHFHdWlJd3lFZ1BnR0I2Y3JLRGRiRXluV2QzbFRt?= =?utf-8?B?YXQ3QW5SWWxITi9jWXJaN0tSTWdCR05aY3gxeVM3MEhrbFlMaVdSMWtPMHBG?= =?utf-8?B?TTBoWStyTCs4TVE2ZVRNL1paMC9CVnZFSWZMaFJZRkRXRURMZ0xOL3dic1JW?= =?utf-8?B?WS9kZUxrNFluRDlPczRnWGE0WDhxOXJFSzhEcnZKajZkdkd5Uk9VNnp4Q3ps?= =?utf-8?B?dkRQd05BQWNkYit5VFNtY1l3WnNqT3ZxUmFGa1lGUGtOc2hRQ3NCUk1wT1dt?= =?utf-8?B?Y2pjeUtzOW5vVml2NndrQzI4eng4WjUyNHZ1YWk2bko3eWlOeWF3YjlZM1hh?= =?utf-8?B?cnNFdzNOWWxxaC9FdWozNTdKem11b1R3QVZsYmd1bnpCei9TSTE2Vjd6cUFn?= =?utf-8?B?NGZLd3VrN1JwZ2d0SWNLUEU2eWxUTHcxbWtYQ2puSUhWdTU4bzluUmtsMXpJ?= =?utf-8?B?QXNnMm9xNXpaRDdDemJCbDhJQXFHWlN5aWo1ZjVJL1RKWWRYQTF1Y21GM04r?= =?utf-8?B?MXdkczVaME53ZU1EQUswRXlLems2dG1QTmtYS2ZTWDZiNkxJNTRzTFJGckdj?= =?utf-8?B?ZnlORWN2UGVPQlhYUlJqOGlGTEl0dk42RE95RHVWQjBHQ2ZuQjNQL0NqQ2pJ?= =?utf-8?B?bE1XVWdXT1BUZG9zN1AvV0RicURWY3hYVjMyRWRMN2tjTU1GWjBvUndvaXJw?= =?utf-8?B?K2k1amJJNTQ4aFk3NEZQVFNWMUV5VzEwbVpFK01IZFd3MCtlR2M0Q3daS1N6?= =?utf-8?B?cUFoa1pzbE5RejBpRWJyb0xoWHBLclZkNmJrUkJyb054Vzc4NVpCbjh5Q0Nr?= =?utf-8?B?VGg3S1pDbG5mLzhNc0RLT0FNcFNqTVNzL3JqdG8rSmlya2VwN29BQXNSWEw1?= =?utf-8?B?SGxpL2VmekMrUThCVjlyUjVIU3ZUZHNDK1UxRzlSbzA3aGdkaTdwcmZGS2pC?= =?utf-8?B?UjF5RXhlNUxMeFhhVEhNdXBiU24rdzRwMkdNUGlNczVYZityUjBKVlgxbEoy?= =?utf-8?B?VHpCV3haeEwxeDVoRGc2ZnVpSnNpMTY1Y2dqaFdyZnpiTk43OFJlOFROZy9k?= =?utf-8?B?MmdNL05IK29IdlQ0T2dBZVl6MFM1MHE1WWNSa2RWUWxGRnBmYm1Wa0JiRFZm?= =?utf-8?B?K3pYMysxWVF5OXRpOUFDbUd3R0VXaXpJanZEck04eTFOZFZIWGhTSmROSU0y?= =?utf-8?B?dFhDeXp2NVEvTzgxTGRlNGtHN21RSDhmZzAwZkVrQUZiSng3K2wxY0trR3NH?= =?utf-8?B?eVdQTm14bGU1dEJpK2tXdXJzVk9OTStVeW1lTk5GMk5JSDNhZWpKOElPMzUz?= =?utf-8?Q?IllLnk4CVZ8GRhr+HBrnJM/P6UahXftq?=
X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2500; 6:3rwQMDkK+mv7lbMBOGEznBymLQHMJH7k7q7Z7sP5FXiWHyQuWpz5u7IfXGnlTIUd8JsV2AglxQwFlVPrH7VvBiu7RKhwPpd7L2wJld53CN76MvKlp6wUTlrSCS1Q0W2zLk/84KlMhW0sTjTqIQ0dONERI/kYj2nNoAp7PaCHCYciWTGx5X2JL642+MqVYSa33LVlZTJnZeJzHOrLPizoPJqkgvoVkKNgF5DznBs44UOH+SvjkUno9Gk5Wo/aYTgic7USkvsHPzTiOzgrlc+xw1ugcE/Q1Td8S6X3BZnT1DNLUt9m9zVbSrjRtFWn5+Q1W8E6r23nOeStid9cTXTDdr9FtrMqSKkCVbg/ydGjWfAXJr323VQPRm4bo81sOOITfXOktZIZgD2t68jvtbrej/kA/C17IEaZdnOJopUZTGUjIVV7tYThu3pXcCyvkj9twaYjiaOSDURTxQeLiGD80g==; 5:bRyRrSTlz2BeV7LliAghW3fZwEYpwTFxD8jsjQQK7kQMwvjVPlpmqgkjTlgrtykG0S+1aeNMPjeHZ0P2ALrI2j8LqpR6iOvaaaNLczJe7/qZTwzUf9Ijb0quYH+nounu1wwKxc06esr75AziC0GNkw==; 24:G+zdLWk+2tr/2tz5RX4tvtyUqaFX3bkyLga/+MFMOLtsSJOnyI89k+fJSaWr4ItlD7zCZMTtbRNUhE+mUdN0IcMh0rrhRmcKWuR/0v02lr4=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BN3PR05MB2500; 7:SnGz5ynuddpq20h3D0aSffWxOmVKIAVJnA3wm8S0t79of7w+0oec7qy4cYlPbHggLdo6fPCW4Vvmlqlc+ZSiu9V3CsglmgK2wXXXmYpcK0g15//OCB75aH+EyquDVhB2Qsb684mzkKIs+SmUdHGLptLo/p40w2Q+S2pizzj05csAVftRe0FCPK3NyW0epl12f6fv/CGJ5oUCAlKTB+tYors5U8VaG0v0la9F3VCQsCEHNoDaGrQi6cCRBs6hjsvIPXig1B2U91mKOyAmQsBewCADwKlNEkRmu4BO7tMBzg+kLaSC07PWxoyVDiZvdu/iOAqlhOuQGXlYTH9xKTI7RGZVFrobP5P7g6+PURVPMfnbhi81EjcW9eOAUQhN5MhROMcbCARXIpNTgEUd0tL2rOkigQNgVPIbo1xY5ZhmVBKOpLa2eosQjN3t4rpXwUnLqegcBfORD0wrzmOFuYOAfQ==
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Jan 2017 15:03:27.5530 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2500
Archived-At: 
Subject: [Idr] WG adoption call for draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules"
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 21 Jan 2017 15:03:33 -0000

Hi All,

The authors have requested IDR working group adoption of =
draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules". =
Please send your comments to the list.

This adoption call will conclude on Monday, February 6.

Thanks,

=E2=80=94John=


From nobody Tue Jan 24 11:26:51 2017
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 4A2B312967A for ; Tue, 24 Jan 2017 11:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.346
X-Spam-Level: **
X-Spam-Status: No, score=2.346 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no 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 N92cUOcmj-D4 for ; Tue, 24 Jan 2017 11:26:48 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 216C5129679 for ; Tue, 24 Jan 2017 11:26:48 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.161.15; 
From: "Susan Hares" 
To: 
Date: Tue, 24 Jan 2017 14:22:42 -0500
Message-ID: <01fa01d27677$3c54c560$b4fe5020$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01FB_01D2764D.53801CF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdJ2dvg6ElOJGZpDSQ22Mk7sLh8hKg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: 
Subject: [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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 24 Jan 2017 19:26:49 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01FB_01D2764D.53801CF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The document draft-ietf-idr-bgp-extended-messages has past WG LC, but it is
awaiting implementations.  Do you know of any implementations - partial or
full?  If so, please respond with an note to this email or send the chairs a
note privately.   This draft is a normative reference for the bgpsec
protocol (draft-ietf-sidr-bgpsec-protocol-22.txt) so if you know of a bgpsec
protocol implementation, please also send that information to the chairs. 

 

Sue Hares 


------=_NextPart_000_01FB_01D2764D.53801CF0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


The =
document draft-ietf-idr-bgp-extended-messages has past WG LC, but it is =
awaiting implementations.  Do you know of any implementations =
– partial or full?  If so, please respond with an note to =
this email or send the chairs a note privately.   This draft =
is a normative reference for the bgpsec protocol =
(draft-ietf-sidr-bgpsec-protocol-22.txt) so if you know of a bgpsec =
protocol implementation, please also send that information to the =
chairs. 
 
Sue Hares 

------=_NextPart_000_01FB_01D2764D.53801CF0--


From nobody Fri Jan 27 01:38:35 2017
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 97BD612948F for ; Fri, 27 Jan 2017 01:38:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.199
X-Spam-Level: 
X-Spam-Status: No, score=-5.199 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_NONE=-0.0001, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
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 grf1rJ1rM4cb for ; Fri, 27 Jan 2017 01:38:32 -0800 (PST)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA17D1293D9 for ; Fri, 27 Jan 2017 01:38:31 -0800 (PST)
Received: from [10.137.2.13] (46.229.239.158.host.vnet.sk [46.229.239.158]) by mail.hq.sk (Postfix) with ESMTPSA id A128E2400E9; Fri, 27 Jan 2017 10:38:27 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1485509907; bh=TDls0XTXpSn0a3yZFQTkxZswPWoYZh/4mDyVQtKolmU=; h=Subject:To:References:From:Date:In-Reply-To; b=RgYRTSmhkYKmRg4VG29SBY0noQbon2mZGjnFKGpP2A7p2bHbjZVwBvdB5QD2jfzvC MOMgzCKk77kw8Jomu7baryXrfz7DxT9AAErV2Jjzmh5oIOou6cc/EQp8660Y9SLTAs rrSWkQDc4YVJV6CFUww4L0oFPWJhiLjor6BRpGFc=
To: Susan Hares , idr@ietf.org
References: <01fa01d27677$3c54c560$b4fe5020$@ndzh.com>
From: Robert Varga 
Message-ID: 
Date: Fri, 27 Jan 2017 10:38:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <01fa01d27677$3c54c560$b4fe5020$@ndzh.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NuNFTC7MEktHqsMJQQ6I93SA2i6Pm8kO2"
Archived-At: 
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 27 Jan 2017 09:38:33 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--NuNFTC7MEktHqsMJQQ6I93SA2i6Pm8kO2
Content-Type: multipart/mixed; boundary="5a1Mj91VKoITUEP1TSR8DRO0XIwx0cVKj";
 protected-headers="v1"
From: Robert Varga 
To: Susan Hares , idr@ietf.org
Message-ID: 
Subject: Re: [Idr] Implementation call for
 draft-ietf-idr-bgp-extended-messages (1/24/2017 to 1/31/2017)
References: <01fa01d27677$3c54c560$b4fe5020$@ndzh.com>
In-Reply-To: <01fa01d27677$3c54c560$b4fe5020$@ndzh.com>

--5a1Mj91VKoITUEP1TSR8DRO0XIwx0cVKj
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 01/24/2017 08:22 PM, Susan Hares wrote:
> The document draft-ietf-idr-bgp-extended-messages has past WG LC, but i=
t
> is awaiting implementations.  Do you know of any implementations =96
> partial or full?  If so, please respond with an note to this email or
> send the chairs a note privately.

Hello,

OpenDaylight implements this draft since its Boron release.

Regards,
Robert


--5a1Mj91VKoITUEP1TSR8DRO0XIwx0cVKj--

--NuNFTC7MEktHqsMJQQ6I93SA2i6Pm8kO2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIoBAEBCgASBQJYixUKCxxuaXRlQGhxLnNrAAoJECsDwSqgzwDTsFMP/jumnyUn
BIa/AsSA26VgRV7qMLX5bfdInIqrDIVHa+bpskyt+EQ+1VBqQBRq+8Cyy+ccJjDk
yqODsDu1en6DDhefRdZvmmWQp0mJiI+rmPHQDtQkFz2CuutLAvEcEoR2C7N8HNXQ
Kfn/RKa2zz3CFzPiLFdu2K7ydX7tzWw69GyChy9Wtp+DV+K3ikvw1pElevoCNAU/
RYss9tBqTMh6H/rU51DmIFT8DwjhrfbnkTwLCMRE6hkM6Me4Onaiw5gHdqvaw5vL
L6j7LZhWkui3DGd3uOJeYhWJJ/5Eehm+Mt9ZtJvlGsJo8l7pwQiFxf3JZT3tNe9T
RkpkgV7DqekgnJ8ISEM/3mEUn6YJ/oOaUdbuFAV+O8yLY3y4fF1px57sEAIYc6kU
tq5gkV6pZKcDFSu59C/5+7ZRS+UZd3LLNp+H/Ly5/CkDQGVpE+/OHr0BsHtQbtnh
OMJorRWftiZfu2jpEmu4jK4wojcjoYuXHuOslAH/TkV9uhjdfqd1IvlcAx0iHuip
d5b7JfLbae1MGKV68aaFul2HP0sF2P4d7TWQQhLMkyH5tGfMNWYlaBXdJZj7K6in
9HIvKQBOTmXHOO590w4VjtOU5f+Q8zZVo11Uhx4VhWblh3IDDfbkrWU+8/vSWNfm
/1NgHrC+H8XmYnLwqIfxffL8hnGeiIZy1oZS
=nKK3
-----END PGP SIGNATURE-----

--NuNFTC7MEktHqsMJQQ6I93SA2i6Pm8kO2--


From nobody Fri Jan 27 13:33:41 2017
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 40BCC129983; Fri, 27 Jan 2017 13:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.101
X-Spam-Level: 
X-Spam-Status: No, score=-5.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 iSmpB7jUop-r; Fri, 27 Jan 2017 13:33:38 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 6B664129985; Fri, 27 Jan 2017 13:33:38 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 65D141E32B; Fri, 27 Jan 2017 16:38:33 -0500 (EST)
Date: Fri, 27 Jan 2017 16:38:33 -0500
From: Jeffrey Haas 
To: Susan Hares 
Message-ID: <20170127213832.GA20988@pfrc.org>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 27 Jan 2017 21:33:39 -0000

Sue and authors,

On Tue, Jan 17, 2017 at 04:04:18PM -0500, Susan Hares wrote:
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> (1/17/2017 to 1/31/2017).  Section 7 of this document lists the
> implementations that have been created for this BGP functionality.   These
> include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and tcpdump

While working through the likely changes in our BGP implementation, the
following thought occurred while looking at the relevant RFC 4486 sub-codes
and triggers.

RFC 4486 defines two administrative actions that seem applicable to this
draft:

         2        Administrative Shutdown
         4        Administrative Reset

The draft covers code point 2.

I believe the draft should cover both administrative sub-codes.  It also
permits two slightly different work flows:

run clear bgp neighbor 192.0.2.1 reason "You have a bgp wedgie and I'm trying to clear it"

set protocols bgp group external neighbor 192.0.2.1 shutdown reason "De-peered with prejudice"

The first allows a reset reason to be passed along that may be transient.

The second permits a reason to persist in subsequent attempts when that BGP
speaker tries to re-connect.

Beyond the above point, I find the document to be of good quality.

-- Jeff


From nobody Fri Jan 27 13:48:54 2017
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 E895F1299A1 for ; Fri, 27 Jan 2017 13:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 5m_yhVF-w9n5 for ; Fri, 27 Jan 2017 13:48:52 -0800 (PST)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A6C2129971 for ; Fri, 27 Jan 2017 13:48:52 -0800 (PST)
Received: by mail-qt0-x22c.google.com with SMTP id v23so158210169qtb.0 for ; Fri, 27 Jan 2017 13:48:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=HuvRLczl7LIOWpq71d3F98FmAi3UgF5PDwVGbeHvgHE=; b=odR7fzszhD51nXUjI0R4sz2JMriVbX23zfnBIDsMRPKhhRuf3gI5BbuyIS3gRkhYT2 khI97T6LV2mMilChOXbJvvXlO6amf+Mm6PESv25Sodk0vakXXxatxaWeH5zGNpezkIfF zMo/zHIhV4mAOWrKUZWS74yZC3f1XIE/TlL5w1Ss9cuqjTdk9xaRbvONdx4QvB4cVKRD hPqGab9UAZT1nZ18w/fLGPJJW5APe+aeKSqw8BujXjBUvoBHRLPPfipcYrzB/MbxIb/y TlS3PfGIBhONgZrMBSIgD5fdwd1Fz5DzQNmyrqk53BJdqW3GHkqLnMXKn7h8TTkIE+Rn zRcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=HuvRLczl7LIOWpq71d3F98FmAi3UgF5PDwVGbeHvgHE=; b=iZn17ymVL+LyTxcy2/ovWv7OZjGgNSg73/YghZe3Zr9tFF4ZsnihywIkMIb12p6unl G3Io1qb6Vf9ZPtXy14scmg8YrjgspBp08NmjR24Xwwfjwfdz/AouObdAIcHhlOqIBHzT US9JmAsw2LvuJfG0Oy7m0S2Ac8vWA0hLU6K32WcimbxInAfkcNbq1DxBCk6ISVXJFIub X2f1Y26CueLMk01iBal5gDMRRoLSbiNyrAqdtngJ1sq5H+ECCQkNA8T1tbDaZ5qp1/0o KrsmApPIow8FIf/wWHMJgD8YfiKTK1HxjkctA2wbjfXIVf6+3IR9y80zt5GBsC1Z6VK+ 3Jaw==
X-Gm-Message-State: AIkVDXK2ecFRD2hc8rIx1kv34nquWKtmjt+d1qec4p10FIRonZ0yG+cv9sWSAg7NF2dBrLCmXnY2a1pxX5Gn4nTi
X-Received: by 10.55.132.4 with SMTP id g4mr9974722qkd.2.1485553731369; Fri, 27 Jan 2017 13:48:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.179.19 with HTTP; Fri, 27 Jan 2017 13:48:20 -0800 (PST)
In-Reply-To: <01b801d27105$45702bc0$d0508340$@ndzh.com>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com>
From: Warren Kumari 
Date: Fri, 27 Jan 2017 16:48:20 -0500
Message-ID: 
To: Susan Hares 
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: 
Cc: "idr@ietf. org" , draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 27 Jan 2017 21:48:54 -0000

On Tue, Jan 17, 2017 at 4:04 PM, Susan Hares  wrote:
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> (1/17/2017 to 1/31/2017).

Support -- willing to edit, review, comment, fold, spindle or mutilate.


> Section 7 of this document lists the
> implementations that have been created for this BGP functionality.   Thes=
e
> include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and tcpdu=
mp
>
>
>
>    o  ExaBGP [1]
>
>    o  pmacct [2]
>
>    o  OpenBGPD [3]
>
>    o  Wireshark [4] (packet analyser)
>
> =C2=B7         tcpdump [5], (alt) [6] (packet analyser)
>
>
>
> Operators should examine if freeform UTF-8 encoded string as described me=
ets
> their operational needs.
>

Yup. I'd prefer freeform straight ASCII, but I understand (and am ok
with) the UTF-8 rationale.

W

>
>
> Sue Hares
>
> WG Co-chair
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>



--=20
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Fri Jan 27 15:21:46 2017
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 DE0A0129AB1; Fri, 27 Jan 2017 15:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no 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 UGd2TnpZ3vI5; Fri, 27 Jan 2017 15:21:43 -0800 (PST)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21101129AB0; Fri, 27 Jan 2017 15:21:42 -0800 (PST)
Received: from mail-wm0-f43.google.com ([74.125.82.43]:34901) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:matthew@walster.org) (TLS1.0:RSA_AES_128_CBC_SHA1:16) id 1cXFpo-0000Np-RX (Exim 4.72) (return-path ); Fri, 27 Jan 2017 23:21:36 +0000
Received: by mail-wm0-f43.google.com with SMTP id r126so138120076wmr.0; Fri, 27 Jan 2017 15:21:40 -0800 (PST)
X-Gm-Message-State: AIkVDXIEC9hEhmPQRjqQyviSNZyn+ycKoVH6s8CloSX0rThgtagDaXKJqeXxyJmsshbxZO8AqjSOCLJTmm0ILA==
X-Received: by 10.223.130.46 with SMTP id 43mr9351754wrb.41.1485559300632; Fri, 27 Jan 2017 15:21:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.164.9 with HTTP; Fri, 27 Jan 2017 15:21:19 -0800 (PST)
In-Reply-To: <20170127213832.GA20988@pfrc.org>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <20170127213832.GA20988@pfrc.org>
From: Matthew Walster 
Date: Fri, 27 Jan 2017 15:21:19 -0800
X-Gmail-Original-Message-ID: 
Message-ID: 
To: Jeffrey Haas 
Content-Type: multipart/alternative; boundary=001a114b3774683aba05471bba65
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org, Susan Hares 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 27 Jan 2017 23:21:45 -0000

--001a114b3774683aba05471bba65
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 27 January 2017 at 13:38, Jeffrey Haas  wrote:

> I believe the draft should cover both administrative sub-codes.


=E2=80=8BWhile I'm hesitant to consider this a perfect idea due to the fact=
 that
there are mechanisms within BGP to make this a non-disrupting event not in
such explicit need of notification=E2=80=8B similar to a shut down event, s=
uch as
graceful restart, end-of-rib markers etc, there is the possibility of a
reset occurring and the BGP session not restoring as intended with a
notification from the remote side or indeed a TCP reset should the speaker
not be willing/ready to accept the new connection. At which point, it would
be good to have the shut down communication message to reference the
intended action, reference a contact point etc.

I'd support a widening of the draft to include the additional code point
(Cease/Administrative Shutdown and Cease/Administrative Reset).

Indeed, could not all Cease sub-codes use this method? For instance:

         1        Maximum Number of Prefixes Reached


The notification could provide a link to a filter update site, or an email
address for the NOC to take further actions... Or to indicate whether or
not the connection is moved into an error state with no future connections
allowed until the error is cleared by an operator.

         3        Peer De-configured


Likewise, this could be supplemented with a message when the session is
being deconfigured and moved to another router.

         6        Other Configuration Change


This has always been difficult to interpret, and has very recently been
something I've been butting up against. A vendor supplied string detailing
the exact change mechanism that caused this would be welcome.

There is obvious scope-creep at this point, I would like to suggest either
the draft considered as-is or to allow all Cease sub-codes to have shutdown
communication possible.

The rest of the draft itself seems well written, easy to understand, and
even unamended would be a welcome addition to the internet operators
toolkit.

Matthew Walster

--001a114b3774683aba05471bba65
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


On 27 Janu=
ary 2017 at 13:38, Jeffrey Haas <jhaas@pfrc.org> wrote:

I believe the draft should cover both administrative sub-codes.=C2=A0

=E2=80=8BWhile I'm hesitant to consider this a=
 perfect idea due to the fact that there are mechanisms within BGP to make =
this a non-disrupting event not in such explicit need of notification=E2=80=
=8B similar to a shut down event, such as graceful restart, end-of-rib mark=
ers etc, there is the possibility of a reset occurring and the BGP session =
not restoring as intended with a notification from the remote side or indee=
d a TCP reset should the speaker not be willing/ready to accept the new con=
nection. At which point, it would be good to have the shut down communicati=
on message to reference the intended action, reference a contact point etc.=


I'd support a widening of the draft to include th=
e additional code point (Cease/Administrative Shutdown and Cease/Administra=
tive Reset).

Indeed, could not all Cease sub-codes use=
 this method? For instance:

         1        Maximum Number of Prefixes Reached


The notification could provide a link to a filter=
 update site, or an email address for the NOC to take further actions... Or=
 to indicate whether or not the connection is moved into an error state wit=
h no future connections allowed until the error is cleared by an operator.<=
/div>

         3      =
  Peer De-configured


Likewise, this could be supplemented with a=
 message when the session is being deconfigured and moved to another router=
.

         6    =
    Other Configuration Change


This has always been difficult to interpret=
, and has very recently been something I've been butting up against. A =
vendor supplied string detailing the exact change mechanism that caused thi=
s would be welcome.

There is obvious scope-creep a=
t this point, I would like to suggest either the draft considered as-is or =
to allow all Cease sub-codes to have shutdown communication possible.
=


The rest of the draft itself seems well written, easy=
 to understand, and even unamended would be a welcome addition to the inter=
net operators toolkit.

Matthew Walster


--001a114b3774683aba05471bba65--


From nobody Fri Jan 27 17:57:12 2017
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 7948B129421; Fri, 27 Jan 2017 17:57:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.1
X-Spam-Level: 
X-Spam-Status: No, score=-5.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 1uvc-UNJ0sVE; Fri, 27 Jan 2017 17:57:10 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 1019D12941E; Fri, 27 Jan 2017 17:57:10 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 6A2781E32C; Fri, 27 Jan 2017 21:02:05 -0500 (EST)
Date: Fri, 27 Jan 2017 21:02:05 -0500
From: Jeffrey Haas 
To: Matthew Walster 
Message-ID: <20170128020205.GA3201@pfrc.org>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <20170127213832.GA20988@pfrc.org> 
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org, Susan Hares 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 01:57:11 -0000

On Fri, Jan 27, 2017 at 03:21:19PM -0800, Matthew Walster wrote:
> On 27 January 2017 at 13:38, Jeffrey Haas  wrote:
> 
> > I believe the draft should cover both administrative sub-codes.
[...] Suggestions of other cases to expand the text-form of the notification
to other sub-codes.

> There is obvious scope-creep at this point, I would like to suggest either
> the draft considered as-is or to allow all Cease sub-codes to have shutdown
> communication possible.

I certainly hadn't intended to try to push for a more general widening of
the scope; just point out something under the existing use case.

While you give three other examples of places that could benefit from
additional data regarding why the session has been sent a CEASE, I don't
think all of them are equally clear with respect to that data being text.

As an example, the max prefixes might benefit from a simple tuple.  E.g.
AFI,SAFI,.  Although keeping this within even a light-weight TLV
would permit space for the machine-readable portion along with a human
readable one.

I would suggest in the absence of a strong case for text strings in the
other sub-codes that for now the draft stay restricted to the administrative
reset cases.  As this draft proves, if there's consenus to add additional
DATA to one of the code points, it can move fast.

-- Jeff


From nobody Sat Jan 28 04:02:26 2017
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 E0B63129486 for ; Sat, 28 Jan 2017 04:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 w8TtOTRLUzzA for ; Sat, 28 Jan 2017 04:02:21 -0800 (PST)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4163612948E for ; Sat, 28 Jan 2017 04:02:21 -0800 (PST)
Received: by mail-wm0-x244.google.com with SMTP id v77so3271808wmv.0 for ; Sat, 28 Jan 2017 04:02:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=yHdWcI0+DtvwDnPgN59U73+VJl4uBnKXjxdAct5zCO0=; b=IDlnQ/ojEoeRu780TdOOuNHkIZ4OjfSKzvpfoHHoPNv/rJlafI+NwIZyIPlFYKJ+w5 T+PMIGw2a45vJePtsUTX1ZxpEEqcnethVizdSgC6Ve7mbT4pi3eGxrfEw7JP/WKfMxKN EL1q4hf0BPlTM9+aeOwms2WsE/rrAQdkf6lMamrpqMu8h82zRmahOvQrhued7dX+PgMe v4NmZ+lM1WuloF8sHkvJ8AMG0zZx30FPEhyzOY8aq3pjBPoEa70vc2kSVaxN2QcrVcBO GGWAAn5DhGqHdSCCD6onVl/xoR5HGJK7v+UXBTB9ZjGiUaQaOSWrtc1Me3loqsWjpeKU 4F+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=yHdWcI0+DtvwDnPgN59U73+VJl4uBnKXjxdAct5zCO0=; b=ksD23mSKbJugMMUQgjGe1PFGU/dXTIScSXyR/oFXvVvir+D6dgglXBwX2RrvOP/BAk cPc5RMgy6fVX2zN3ucmabPsW9LHJzcQ35xAjVINNZoRJr/BKDAgqbwGF/NpTtpAcY+nx sbP1POcBQeO3eyGqS83gxHes4HAB52iEhXa0e9xXclPMc1mDvEB/tiTXLO7fDDY9eRHl d1wv0wQRK5+Ip424cBiD2B8NOKWw60/fUc45Rx2+347ocHwsv7Xiu6xHzkNBLlYHxKG/ 8QmjObWUIc/JOPfZhv1IVnfPuarJx0nyG+ght6OdXiGI6rK/FCtr7FydBkw8ZtwK6e4c /KmA==
X-Gm-Message-State: AIkVDXKcgRtuM9rypenWHo5HmAN2Yf6io80v9k+kPoVMuz2rWiaUhU1jSVzMGepzPDKpcw==
X-Received: by 10.223.164.10 with SMTP id d10mr10890259wra.90.1485604939529; Sat, 28 Jan 2017 04:02:19 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:5878:ee0d:a48e:58d2]) by smtp.gmail.com with ESMTPSA id s26sm12504864wra.26.2017.01.28.04.02.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Jan 2017 04:02:18 -0800 (PST)
Date: Sat, 28 Jan 2017 13:02:17 +0100
From: Job Snijders 
To: Jeffrey Haas 
Message-ID: <20170128120217.GA91223@Vurt.local>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <20170127213832.GA20988@pfrc.org>  <20170128020205.GA3201@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170128020205.GA3201@pfrc.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org, Susan Hares 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 12:02:24 -0000

Hi group,

On Fri, Jan 27, 2017 at 09:02:05PM -0500, Jeffrey Haas wrote:
> On Fri, Jan 27, 2017 at 03:21:19PM -0800, Matthew Walster wrote:
> > On 27 January 2017 at 13:38, Jeffrey Haas  wrote:
> > 
> > > I believe the draft should cover both administrative sub-codes.
> > > [...] Suggestions of other cases to expand the text-form of the
> > > notification to other sub-codes.
> 
> > There is obvious scope-creep at this point, I would like to suggest
> > either the draft considered as-is or to allow all Cease sub-codes to
> > have shutdown communication possible.
> 
> I certainly hadn't intended to try to push for a more general widening
> of the scope; just point out something under the existing use case.
> 
> While you give three other examples of places that could benefit from
> additional data regarding why the session has been sent a CEASE, I
> don't think all of them are equally clear with respect to that data
> being text.
> 
> As an example, the max prefixes might benefit from a simple tuple.
> E.g. AFI,SAFI,. Although keeping this within even a
> light-weight TLV would permit space for the machine-readable portion
> along with a human readable one.
> 
> I would suggest in the absence of a strong case for text strings in
> the other sub-codes that for now the draft stay restricted to the
> administrative reset cases. As this draft proves, if there's consenus
> to add additional DATA to one of the code points, it can move fast.

I think Jeff's suggestion to add the Administrative Reset (subcode 4)
case is a good one. There can be value in attachting contact information
or a case identifier to BGP resets. Matthew mentioned (outside of this
mailing list) that this information would especially be useful if after
the reset, the BGP session does not re-establish. Also, conceptually the
'reset' and 'shutdown' are close to each other as they are initiated by
the Administrator.

However, I consider the other subcodes out of scope for what
draft-ietf-idr-shutdown tries to accomplish, and as such would belong in
their own Internet-Draft.

Kind regards,

Job


From nobody Sat Jan 28 04:10:33 2017
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 B4FD6129492 for ; Sat, 28 Jan 2017 04:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 suCruhGrrA6C for ; Sat, 28 Jan 2017 04:10:29 -0800 (PST)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47F41129491 for ; Sat, 28 Jan 2017 04:10:29 -0800 (PST)
Received: by mail-wm0-x243.google.com with SMTP id r126so64474240wmr.3 for ; Sat, 28 Jan 2017 04:10:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=3T2ZWv/EVvnXuNsuAq0PUn7yjuKrfP3lB93VdqbHlBI=; b=ZBaF9owGzp5eE/vYNSx6KmfWKeoAbUCR8v4RoIeJl4aLr1F6ozr0HuE9OeTlUNlZRb KIoASaJjvq6ZvRNEXRY/Ja6bJX0D+msN9qfmgYm07MmEZXcC+IQIm6eA95hpnA1JGVOw uqC+Pqf3mMut4Hmw0VQ6wS16Z9Sw+YDnJ9V0VqkzC/Gf8WSBSD0p3wq+0JS1EGqtc8GN 0jskghhjNJPVrfh3XXJyFMiqu23JYL4gAtqnOsrFolPtHtELHbysmmYy7qA/i3GgRzAo 4rPEBKuvbiAPn/t8WxQ2R3WFytCI+JGyxwxAZy7L/p9WE1ZdavMykG0RNbWsNFjJQGqh MHSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=3T2ZWv/EVvnXuNsuAq0PUn7yjuKrfP3lB93VdqbHlBI=; b=cHARtU6ruZ9Ws3Vv887UpHtYSZiblX4ziT6sEJ9GRJGa1Wvn9Z1sFXd62wCnCYUFQN n9agIS94RefucsEZYaSuQeMkP6tGYtMJTYZvrG4NJCEBm7OCFoTS2zmiS7fGIYj7lw/c dSukAzu4t3EcIUAf+5n/DL2jvGwTJPS0aFYadTlyRnKmrAuxHom8Gk82U2EhgB1Q1mXC +l2sbdb57kk8u32K905qtd+bQwdGiLhR0DxfODFCTlgGdW897APGaO+z4Wh54YhZJmeJ tt00Cf4w8yTGI/kVH+OjAy+B0lI4Z1SWP0Myg4JDVkCyan2L7O5xwIvCMcg6/Erfg/RE xeDA==
X-Gm-Message-State: AIkVDXIbWO/INKD5ljBT/CqGNLrfZ5UFDKHWpsrl+A54+eCoPMjvpqucaks7BE700U3zFw==
X-Received: by 10.28.4.216 with SMTP id 207mr6525508wme.45.1485605427483; Sat, 28 Jan 2017 04:10:27 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:5878:ee0d:a48e:58d2]) by smtp.gmail.com with ESMTPSA id l10sm12687852wrb.44.2017.01.28.04.10.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Jan 2017 04:10:26 -0800 (PST)
Date: Sat, 28 Jan 2017 13:10:25 +0100
From: Job Snijders 
To: Jeffrey Haas 
Message-ID: <20170128121025.GB91223@Vurt.local>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <20170127213832.GA20988@pfrc.org>  <20170128020205.GA3201@pfrc.org> <20170128120217.GA91223@Vurt.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170128120217.GA91223@Vurt.local>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org, Susan Hares 
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 12:10:30 -0000

BTW, regarding last call & IDR implementation requirements, i can
immediately deliver at least two implementations that also accomodate
the 'reset' case so from that perspective there will be no blocker to
proceed.

Kind regards,

Job

On Sat, Jan 28, 2017 at 01:02:17PM +0100, Job Snijders wrote:
> Hi group,
> 
> On Fri, Jan 27, 2017 at 09:02:05PM -0500, Jeffrey Haas wrote:
> > On Fri, Jan 27, 2017 at 03:21:19PM -0800, Matthew Walster wrote:
> > > On 27 January 2017 at 13:38, Jeffrey Haas  wrote:
> > > 
> > > > I believe the draft should cover both administrative sub-codes.
> > > > [...] Suggestions of other cases to expand the text-form of the
> > > > notification to other sub-codes.
> > 
> > > There is obvious scope-creep at this point, I would like to suggest
> > > either the draft considered as-is or to allow all Cease sub-codes to
> > > have shutdown communication possible.
> > 
> > I certainly hadn't intended to try to push for a more general widening
> > of the scope; just point out something under the existing use case.
> > 
> > While you give three other examples of places that could benefit from
> > additional data regarding why the session has been sent a CEASE, I
> > don't think all of them are equally clear with respect to that data
> > being text.
> > 
> > As an example, the max prefixes might benefit from a simple tuple.
> > E.g. AFI,SAFI,. Although keeping this within even a
> > light-weight TLV would permit space for the machine-readable portion
> > along with a human readable one.
> > 
> > I would suggest in the absence of a strong case for text strings in
> > the other sub-codes that for now the draft stay restricted to the
> > administrative reset cases. As this draft proves, if there's consenus
> > to add additional DATA to one of the code points, it can move fast.
> 
> I think Jeff's suggestion to add the Administrative Reset (subcode 4)
> case is a good one. There can be value in attachting contact information
> or a case identifier to BGP resets. Matthew mentioned (outside of this
> mailing list) that this information would especially be useful if after
> the reset, the BGP session does not re-establish. Also, conceptually the
> 'reset' and 'shutdown' are close to each other as they are initiated by
> the Administrator.
> 
> However, I consider the other subcodes out of scope for what
> draft-ietf-idr-shutdown tries to accomplish, and as such would belong in
> their own Internet-Draft.
> 
> Kind regards,
> 
> Job


From nobody Sat Jan 28 07:39:41 2017
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 83AC3129570; Sat, 28 Jan 2017 07:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no 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 tu0ignJY4bvi; Sat, 28 Jan 2017 07:39:38 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2960A129571; Sat, 28 Jan 2017 07:39:38 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.161.15; 
From: "Susan Hares" 
To: "'Job Snijders'" , "'Jeffrey Haas'" 
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <20170127213832.GA20988@pfrc.org>  <20170128020205.GA3201@pfrc.org> <20170128120217.GA91223@Vurt.local> <20170128121025.GB91223@Vurt.local>
In-Reply-To: <20170128121025.GB91223@Vurt.local>
Date: Sat, 28 Jan 2017 10:35:17 -0500
Message-ID: <018601d2797c$21320ec0$63962c40$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIhUUJZA+cIT4/8zl2Sev/afC8NdAJB2HE6AUlHwPsCoauwKwGZAsXWAaYzxQygZPVe4A==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: 
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 15:39:39 -0000

Job: 

Thanks for letting me know.  Please put up the implementation changes once
you have the reset in a draft.  Without out it, we'd will be blocked to send
this to the IESG.

Sue 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Job Snijders
Sent: Saturday, January 28, 2017 7:10 AM
To: Jeffrey Haas
Cc: idr@ietf.org; draft-ietf-idr-shutdown@ietf.org; Susan Hares
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to
1/31/2017)

BTW, regarding last call & IDR implementation requirements, i can
immediately deliver at least two implementations that also accomodate the
'reset' case so from that perspective there will be no blocker to proceed.

Kind regards,

Job

On Sat, Jan 28, 2017 at 01:02:17PM +0100, Job Snijders wrote:
> Hi group,
> 
> On Fri, Jan 27, 2017 at 09:02:05PM -0500, Jeffrey Haas wrote:
> > On Fri, Jan 27, 2017 at 03:21:19PM -0800, Matthew Walster wrote:
> > > On 27 January 2017 at 13:38, Jeffrey Haas  wrote:
> > > 
> > > > I believe the draft should cover both administrative sub-codes.
> > > > [...] Suggestions of other cases to expand the text-form of the 
> > > > notification to other sub-codes.
> > 
> > > There is obvious scope-creep at this point, I would like to 
> > > suggest either the draft considered as-is or to allow all Cease 
> > > sub-codes to have shutdown communication possible.
> > 
> > I certainly hadn't intended to try to push for a more general 
> > widening of the scope; just point out something under the existing use
case.
> > 
> > While you give three other examples of places that could benefit 
> > from additional data regarding why the session has been sent a 
> > CEASE, I don't think all of them are equally clear with respect to 
> > that data being text.
> > 
> > As an example, the max prefixes might benefit from a simple tuple.
> > E.g. AFI,SAFI,. Although keeping this within even a 
> > light-weight TLV would permit space for the machine-readable portion 
> > along with a human readable one.
> > 
> > I would suggest in the absence of a strong case for text strings in 
> > the other sub-codes that for now the draft stay restricted to the 
> > administrative reset cases. As this draft proves, if there's 
> > consenus to add additional DATA to one of the code points, it can move
fast.
> 
> I think Jeff's suggestion to add the Administrative Reset (subcode 4) 
> case is a good one. There can be value in attachting contact 
> information or a case identifier to BGP resets. Matthew mentioned 
> (outside of this mailing list) that this information would especially 
> be useful if after the reset, the BGP session does not re-establish. 
> Also, conceptually the 'reset' and 'shutdown' are close to each other 
> as they are initiated by the Administrator.
> 
> However, I consider the other subcodes out of scope for what 
> draft-ietf-idr-shutdown tries to accomplish, and as such would belong 
> in their own Internet-Draft.
> 
> Kind regards,
> 
> Job

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


From nobody Sat Jan 28 11:41:49 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2BC61296E4; Sat, 28 Jan 2017 11:41:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148563250292.17952.3195772749534320982.idtracker@ietfa.amsl.com>
Date: Sat, 28 Jan 2017 11:41:42 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-shutdown-04.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 19:41:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : BGP Administrative Shutdown Communication
        Authors         : Job Snijders
                          Jakob Heitz
                          John Scudder
	Filename        : draft-ietf-idr-shutdown-04.txt
	Pages           : 6
	Date            : 2017-01-28

Abstract:
   This document enhances the BGP Cease NOTIFICATION message
   "Administrative Shutdown" and "Administrative Reset" subcodes for
   operators to transmit a short freeform message to describe why a BGP
   session was shutdown or reset.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-shutdown-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Jan 28 11:57:02 2017
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 78937129784 for ; Sat, 28 Jan 2017 11:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.133
X-Spam-Level: 
X-Spam-Status: No, score=-5.133 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham 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 iCIoOctI3EPr for ; Sat, 28 Jan 2017 11:57:00 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 5921C129793 for ; Sat, 28 Jan 2017 11:56:58 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cXZ7J-0002XO-4v (job@us.ntt.net); Sat, 28 Jan 2017 19:56:58 +0000
Date: Sat, 28 Jan 2017 20:56:54 +0100
From: Job Snijders 
To: idr@ietf.org
Message-ID: <20170128195654.GA1053@Vurt.local>
References: <148563250292.17952.3195772749534320982.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148563250292.17952.3195772749534320982.idtracker@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: 
Subject: Re: [Idr] I-D Action: draft-ietf-idr-shutdown-04.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 19:57:01 -0000

Dear group,

Changelog -03 -> -04:

    o The 'Shutdown Communication' can now also be send attached to a
      Cease NOTIFICATION with subcode 'Administrative Reset'.

    o The implementation list has been reset and updated. The listed
      implementations support both 'Administrative Shutdown' (as
      specified in -03) and 'Administrative Shutdown' (specified in this
      version).

Since this version includes a change containing normative language, and
we are in the Working Group Last Call phase, an extension to the Last
Call period is to be expected. 

Kind regards,

Job

On Sat, Jan 28, 2017 at 11:41:42AM -0800, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Inter-Domain Routing of the IETF.
> 
>         Title           : BGP Administrative Shutdown Communication
>         Authors         : Job Snijders
>                           Jakob Heitz
>                           John Scudder
> 	Filename        : draft-ietf-idr-shutdown-04.txt
> 	Pages           : 6
> 	Date            : 2017-01-28
> 
> Abstract:
>    This document enhances the BGP Cease NOTIFICATION message
>    "Administrative Shutdown" and "Administrative Reset" subcodes for
>    operators to transmit a short freeform message to describe why a BGP
>    session was shutdown or reset.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-idr-shutdown-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-04
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


From nobody Sat Jan 28 11:59:26 2017
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 D013C129D82 for ; Sat, 28 Jan 2017 11:59:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.845
X-Spam-Level: **
X-Spam-Status: No, score=2.845 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no 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 zUgIaXfBllHm for ; Sat, 28 Jan 2017 11:59:23 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8094A129D70 for ; Sat, 28 Jan 2017 11:59:23 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=70.194.13.195; 
From: "Susan Hares" 
To: 
Date: Sat, 28 Jan 2017 14:55:13 -0500
Message-ID: <000301d279a0$710e3350$532a99f0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01D27976.88387970"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdJ5n/uUleXIA9F7RkODkuO7lpv1ug==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: 
Subject: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017) - extended 2 weeks (1/31 to 2/14/2016)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 19:59:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0004_01D27976.88387970
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This WG LC is extended 2 weeks to consider the additions in
draft-ietf-idr-shutdown-04.txt so that: 

 

    The 'Shutdown Communication' can now also be send attached to a

      Cease NOTIFICATION with subcode 'Administrative Reset'.

 

 

Sue Hares 

Co-chair 


------=_NextPart_000_0004_01D27976.88387970
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


This WG LC =
is extended 2 weeks to consider the additions in =
draft-ietf-idr-shutdown-04.txt so that: 
 
    The 'Shutdown Communication' can =
now also be send attached to a
      Cease NOTIFICATION =
with subcode 'Administrative Reset'.
 
 
Sue Hares =

Co-chair =


------=_NextPart_000_0004_01D27976.88387970--


From nobody Sat Jan 28 12:04:27 2017
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 688261297AB for ; Sat, 28 Jan 2017 12:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.134
X-Spam-Level: 
X-Spam-Status: No, score=-5.134 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_SOFTFAIL=0.665] autolearn=ham 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 QHDa9IF2gUlo for ; Sat, 28 Jan 2017 12:04:24 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 9EC42129781 for ; Sat, 28 Jan 2017 12:04:24 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cXZEV-0003Fc-Qc (job@us.ntt.net); Sat, 28 Jan 2017 20:04:24 +0000
Date: Sat, 28 Jan 2017 21:04:21 +0100
From: Job Snijders 
To: idr@ietf.org
Message-ID: <20170128200421.GB1053@Vurt.local>
References: <148563250292.17952.3195772749534320982.idtracker@ietfa.amsl.com> <20170128195654.GA1053@Vurt.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170128195654.GA1053@Vurt.local>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: 
Subject: Re: [Idr] I-D Action: draft-ietf-idr-shutdown-04.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 28 Jan 2017 20:04:25 -0000

On Sat, Jan 28, 2017 at 08:56:54PM +0100, Job Snijders wrote:
> Dear group,
> 
> Changelog -03 -> -04:
> 
>     o The 'Shutdown Communication' can now also be send attached to a
>       Cease NOTIFICATION with subcode 'Administrative Reset'.
> 
>     o The implementation list has been reset and updated. The listed
>       implementations support both 'Administrative Shutdown' (as
>       specified in -03) and 'Administrative Shutdown' (specified in this
>       version).

errr... I meant to type:

    o The implementation list has been reset and updated. The listed
      implementations support both 'Administrative Shutdown' (as
      specified in -03) and 'Administrative Reset' (specified in this
      version).

Kind regards,

Job


From nobody Sun Jan 29 12:04:09 2017
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 8B93B1295DC for ; Sun, 29 Jan 2017 12:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham 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 yLu6H6vcDF4O for ; Sun, 29 Jan 2017 12:04:06 -0800 (PST)
Received: from mail.hated.at (mail.hated.at [IPv6:2001:858:2:8::235]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C4811295DB for ; Sun, 29 Jan 2017 12:04:05 -0800 (PST)
Received: from 62-47-157-145.adsl.highway.telekom.at ([62.47.157.145] helo=[192.168.88.27]) by mail.hated.at with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1cXvXS-0004T7-KN; Sun, 29 Jan 2017 20:53:27 +0100
From: Christoph Loibl 
Message-Id: <5695B5BA-D452-49BB-974B-172ADDDD1C1E@tix.at>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9DB88788-F639-4166-8E43-1944A0D238B7"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Date: Sun, 29 Jan 2017 21:04:00 +0100
In-Reply-To: <36E285C0-C716-437A-806D-A453273146DD@juniper.net>
To: "John G. Scudder" 
References: <36E285C0-C716-437A-806D-A453273146DD@juniper.net>
X-Mailer: Apple Mail (2.3251)
Archived-At: 
Cc: idr@ietf.org
Subject: Re: [Idr] WG adoption call for draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules"
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sun, 29 Jan 2017 20:04:08 -0000

--Apple-Mail=_9DB88788-F639-4166-8E43-1944A0D238B7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi All,

As an co-author of the draft I support the adoption.=20

However, I noticed that I missed to post our recent paper on Flowspec =
interop to the IDR list. This paper illustrates (based on our lab setup) =
the current state of Flowspec implementations. Because of the =
incompatibilities observed we were inspired to co-author the =
draft-hr-idr-rfc5575bis to improve interoperability and stability.

You may download our paper at:

http://p4.tix.at/~cl/fs/loibl-bacher-bgp-flowspec-interop-012017.pdf =


Regards
Christoph


> On 21 Jan 2017, at 16:03, John G. Scudder  wrote:
>=20
> Hi All,
>=20
> The authors have requested IDR working group adoption of =
draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules". =
Please send your comments to the list.
>=20
> This adoption call will conclude on Monday, February 6.
>=20
> Thanks,
>=20
> =E2=80=94John
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

--=20
Christoph Loibl
c@tix.at  | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | =
http://www.nextlayer.at 

--Apple-Mail=_9DB88788-F639-4166-8E43-1944A0D238B7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

Hi All,

As =
an co-author of the draft I support the adoption. 

However, I noticed that =
I missed to post our recent paper on Flowspec interop to the IDR list. =
This paper illustrates (based on our lab setup) the current state of =
Flowspec implementations. Because of the incompatibilities observed we =
were inspired to co-author the draft-hr-idr-rfc5575bis to improve =
interoperability and stability.

You may download our paper =
at:

http://p4.tix.at/~cl/fs/loibl-bacher-bgp-flowspec-interop-01201=
7.pdf

Regards
Christoph

On 21 Jan 2017, at 16:03, John =
G. Scudder <jgs@juniper.net> wrote:

Hi =
All,

The authors have requested IDR working =
group adoption of draft-hr-idr-rfc5575bis-02 "Dissemination of Flow =
Specification Rules". Please send your comments to the list.

This adoption call will conclude on Monday, =
February 6.

Thanks,

=E2=80=94John
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr



-- 
Christoph Loibl
c@tix.at | CL8-RIPE | =
PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at





=

--Apple-Mail=_9DB88788-F639-4166-8E43-1944A0D238B7--


From nobody Mon Jan 30 04:43:53 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AC462129477; Mon, 30 Jan 2017 04:43:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148578023169.29941.4065688703712181425.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jan 2017 04:43:51 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-sla-exchange-10.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 30 Jan 2017 12:43:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : Inter-domain SLA Exchange Attribute
        Authors         : Shitanshu Shah
                          Keyur Patel
                          Sandeep Bajaj
                          Luis Tomotaki
                          Mohamed Boucadair
	Filename        : draft-ietf-idr-sla-exchange-10.txt
	Pages           : 30
	Date            : 2017-01-28

Abstract:
   Network administrators typically enforce Quality of Service (QoS)
   policies according to Service Level Agreement (SLA) with their
   providers.  The enforcement of such policies often relies upon
   vendor-specific configuration language.  Both learning of SLA, either
   thru SLA documents or via some other out-of-band method, and
   translating them to vendor specific configuration language is a
   complex, often manual, process and prone to errors.

   This document specifies an optional transitive attribute to signal
   SLA parameters in-band, across administrative boundaries (considered
   as Autonomous Systems (AS)), thus simplifying and facilitating some
   of the complex provisioning tasks in situations where BGP is
   available as a routing protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-sla-exchange/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-sla-exchange-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-sla-exchange-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jan 30 08:20:00 2017
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 4FD71129515; Mon, 30 Jan 2017 08:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham 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 xKTWFK0wEx55; Mon, 30 Jan 2017 08:19:41 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0DDF129547; Mon, 30 Jan 2017 08:19:29 -0800 (PST)
Received: from [192.168.1.11] (unknown [122.52.28.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 18CC318013DA; Mon, 30 Jan 2017 17:19:26 +0100 (CET)
References: 
To: idr@ietf.org
From: Loa Andersson 
X-Forwarded-Message-Id: 
Message-ID: 
Date: Tue, 31 Jan 2017 00:19:21 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: 
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
Cc: idr-chairs@ietf.org, "mpls-chairs@ietf.org" 
Subject: [Idr] Working group last call on draft-ietf-mpls-residence-time
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 30 Jan 2017 16:19:51 -0000

IDR working group,

Please note that we are doing a new working group last call on
draft-ietf-mpls-residence-time-13.

/Loa


-------- Forwarded Message --------
Subject: [OSPF] Working group last call on draft-ietf-mpls-residence-time
Date: Tue, 31 Jan 2017 00:01:56 +0800
From: Loa Andersson 
To: mpls@ietf.org , TEAS WG , 
ospf@ietf.org , Isis-wg 
CC: isis-chairs@ietf.org, draft-ietf-mpls-residence-time@tools.ietf.org, 
TEAS WG Chairs , mpls-chairs@ietf.org 
, ospf-chairs@ietf.org

Working Groups,

This is to initiate a two week working group last call in four working
groups on draft-ietf-mpls-residence-time-13.

The MPLS working group has done an earlier working group last call and
a request for publication has been made.

The changes to the document were such that we decided to do a new
working group last call and extend it to MPLS, TEAS, OSPF and IS-IS.

There are three major changes between the version of the document for
which publication was requested are:

(1) that section 7 " One-step Clock and Two-step Clock Modes" has been
     moved up to become section 2.1.
(2) that a sub-TLV for TLV 22 instead of TLV 251 is used to RTM
     Capability when IS-IS used advertise RTM capabilities
(3) BGP-LS has been added as a RTM capability advertisement method

A side-by-side diff between version -12 and -13 is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-residence-time-13

Please send your comments to the mpls wg mailing list (mpls@ietf.org),
if you are not subscribed to the mpls wg list, send to "your own"
working group mailing list, and we'll make sure they are posted to the
MPLS wg list.

There were one IPR disclosure against this document.

All the authors and contributors have stated on the working group
mailing list that they are not aware of any other IPRs that relates
to this document.

This working group last call ends February 13, 2017.


/Loa
MPLS wg co-chairs
-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Tue Jan 31 05:35:11 2017
Return-Path: 
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FE6129EF5; Tue, 31 Jan 2017 05:35:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148586970516.2511.5635692050345208027.idtracker@ietfa.amsl.com>
Date: Tue, 31 Jan 2017 05:35:05 -0800
Archived-At: 
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-shutdown-05.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 31 Jan 2017 13:35:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : BGP Administrative Shutdown Communication
        Authors         : Job Snijders
                          Jakob Heitz
                          John Scudder
	Filename        : draft-ietf-idr-shutdown-05.txt
	Pages           : 6
	Date            : 2017-01-31

Abstract:
   This document enhances the BGP Cease NOTIFICATION message
   "Administrative Shutdown" and "Administrative Reset" subcodes for
   operators to transmit a short freeform message to describe why a BGP
   session was shutdown or reset.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-shutdown-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-shutdown-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Jan 31 09:57:32 2017
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 B8987129513 for ; Tue, 31 Jan 2017 09:57:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.346
X-Spam-Level: **
X-Spam-Status: No, score=2.346 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no 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 ceL5-3yHJH8c for ; Tue, 31 Jan 2017 09:57:29 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A54112948D for ; Tue, 31 Jan 2017 09:57:28 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.124.241.11; 
From: "Susan Hares" 
To: 
Date: Tue, 31 Jan 2017 12:53:19 -0500
Message-ID: <00ce01d27bea$e889bbb0$b99d3310$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00CF_01D27BC0.FFB56160"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdJ76jv688JyV4KVTu+ixD1O+vT0GQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: 
Subject: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017) - 2 week extension (1/31 to 2/14)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 31 Jan 2017 17:57:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00CF_01D27BC0.FFB56160
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The changes to the IDR shutdown to apply it to the "Administrative Shutdown"
and "Administrative Reset" (se draft-ietf-idr-shutdown-05.txt).  Due to this
change, we will extend the WG LC 2 weeks ending 2/14.     In the meantime,
we will be asking for early reviews from the various directorates (Routing
and OPS-DIR), and the grow working group.  

 

At this point, it appears to this WG co-chair that we are approaching
consensus on draft-ietf-idr-shutdown-05.txt.  If you are WG member and wish
to make a comment I encourage you to post to the list within the first week
of this 2 week call.   Given the current comments on the draft, this draft
may move quickly from WG LC to posting to the IESG for publication. 

 

 

Sue Hares  

 

 


------=_NextPart_000_00CF_01D27BC0.FFB56160
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


The =
changes to the IDR shutdown to apply it to the “Administrative =
Shutdown” and “Administrative Reset” (se =
draft-ietf-idr-shutdown-05.txt).  Due to this change, we will =
extend the WG LC 2 weeks ending 2/14.     In the =
meantime, we will be asking for early reviews from the various =
directorates (Routing and OPS-DIR), and the grow working group. =
 
 
At this point, it appears to this WG co-chair that we =
are approaching consensus on draft-ietf-idr-shutdown-05.txt.  If =
you are WG member and wish to make a comment I encourage you to post to =
the list within the first week of this 2 week call.   Given =
the current comments on the draft, this draft may move quickly from WG =
LC to posting to the IESG for publication. 
 
 
Sue Hares =
 
 
 

------=_NextPart_000_00CF_01D27BC0.FFB56160--