Re: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-bgp-extended-messages-33: (with COMMENT)
"Enke Chen (enkechen)" <enkechen@cisco.com> Wed, 31 July 2019 16:51 UTC
Return-Path: <enkechen@cisco.com>
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 1A039120422; Wed, 31 Jul 2019 09:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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 header.b=Z07BhS8V; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=NnaheTiF
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 xIpZC10_91Vp; Wed, 31 Jul 2019 09:51:26 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7867D120451; Wed, 31 Jul 2019 09:51:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13142; q=dns/txt; s=iport; t=1564591886; x=1565801486; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LKKtIPj4cNFdOgL2c+hvJ5XgxMSLfXwe5VfleJsg5O4=; b=Z07BhS8VyNUUnMAGJKAAen5RBELuVldLvaBdjbxqUeAZBYLWNHUILNLX XhexVpSGi/450BHFSu/5+UHyqhwIQkOTZiW/PaK0/L+Ct+frk1mIwI7fI USZ0Mw5XZ1ts35Y60b4uWMOBBHyEbp+7UnfHTg3lGrA9hn4YZGwTS4cLt Q=;
IronPort-PHdr: 9a23:Xr0b9h3qb2GxKYfrsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQBEv4IfXqYioSF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHAACAxkFd/51dJa1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwQBAQEBAQsBgURQA21VIAQLKoQeg0cDhFKGVEyCD36IVo4BgS6BJANUCQEBAQwBARgLCgIBAYRAAheCNyM0CQ4BAwEBBAEBAgEGbYUeDIVKAQEBAQMBARAREQwBASwLAQsEAgEIDgMDAQEBAwIfBAMCAgIfBgsUAQUDCAIEAQ0FIoMAAYFqAx0BDqFwAoE4iGBxgTKCegEBBYUCDQuCEwMGgQwoAYtfF4FAP4ERJx+CFzU+ghpHAQGBOyYXgnQygiaMK4IoMZtPQAkCghqQIgSDcxuCLpVogymKF4EyiBWOHQIEAgQFAg4BAQWBUDiBWHAVOyoBL4ISgkI3gzqFFIU/coEpi0eCUQEB
X-IronPort-AV: E=Sophos;i="5.64,330,1559520000"; d="scan'208";a="603453695"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Jul 2019 16:51:23 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x6VGpNXY025611 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 31 Jul 2019 16:51:23 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 31 Jul 2019 11:51:22 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 31 Jul 2019 11:51:22 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 31 Jul 2019 11:51:21 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KxWBCoRZIknapA9M7GuYG1Kp8rSiitdNuSxy50QNOzCINLCdO3LsYt/L6GnX6EFEorSQD6VBCpRQj3YDQVwdxmEB/9aC23gr+W9FgaVeLNGymrGa5aWTf8GwxIMutjX0PVjGk6NIdnjKYmyhP5f5cM/q4X88C3I/uSTsxLZKiow/d8mJrjzVZLS4VKC6Jr0I+rLZOKedAVxH7NPq9RCJywh+u07Ma06X1FkBFUT6xVx6IrA062BGR95qOgpTOgRSt4AxTfCyTkkci14Frr8GFY6lJRGZj2WsqGRXo1S1TnUopjKijseFomEb/IHSCMvrtVKED7pTfs0NbDUQlmrGUw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LKKtIPj4cNFdOgL2c+hvJ5XgxMSLfXwe5VfleJsg5O4=; b=E9+fVpJ3Ci4b/+eflx/7r08Q7eUVGZm6btPUGnzlKpSaVR9zEt3HdwnBTLHBx7Q4XVzxe8oqjIHpaaA6nV3h0ALK82F5i3xSKrP3ItpK2hy1ULEOq9jq4dXKdiP4gs+3RNbDYOJ4sqjnve38bRzIdCkp5UldACBPgErUbeSupOKRnXDdlevJpA/FtEqUvZmSdR9yV1PBUHnbqLRgYnXJx/QU2r7dvTiwQF7YV6qer1rMFb03vwOC8LvugHkhN9ZEWC6EgDCvqI77j9XIysTfDDzys0ZtGmlKZP8e0eNwymgFcop5O1by3yIHwb5iu+veh82o5p/gchfqWZkx2I4h9Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LKKtIPj4cNFdOgL2c+hvJ5XgxMSLfXwe5VfleJsg5O4=; b=NnaheTiFfHijEyajOZ/iWuTQQl98C2YDKU/LH11BeOV3T7nrjncfCIBnzKMAuwJXjFDXUZiLWLWcM3HFRShmArdnYXNcdYBgQzlMXvqEAp1eYTLtOEU4KWFoHUk30VWr/KzSQh+27DUhuBBfgXMIB6dmdvVNcE+MMCIaeooRytw=
Received: from BY5PR11MB3990.namprd11.prod.outlook.com (10.255.162.95) by BY5PR11MB4195.namprd11.prod.outlook.com (52.132.253.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.14; Wed, 31 Jul 2019 16:51:20 +0000
Received: from BY5PR11MB3990.namprd11.prod.outlook.com ([fe80::7026:24f1:c19f:e2f4]) by BY5PR11MB3990.namprd11.prod.outlook.com ([fe80::7026:24f1:c19f:e2f4%5]) with mapi id 15.20.2115.005; Wed, 31 Jul 2019 16:51:20 +0000
From: "Enke Chen (enkechen)" <enkechen@cisco.com>
To: Susan Hares <shares@ndzh.com>, 'Randy Bush' <randy@psg.com>, 'Alvaro Retana' <aretana.ietf@gmail.com>
CC: "idr@ietf.org" <idr@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "draft-ietf-idr-bgp-extended-messages@ietf.org" <draft-ietf-idr-bgp-extended-messages@ietf.org>, 'The IESG' <iesg@ietf.org>, "'\"Mirja Kühlewind via Datatracker\"'" <noreply@ietf.org>, "Enke Chen (enkechen)" <enkechen@cisco.com>
Thread-Topic: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-bgp-extended-messages-33: (with COMMENT)
Thread-Index: AQHVRxBvuX4ot0XkLEK5yEtH+3jM+Kbjle4AgAANIgCAAEuegP//kzUAgAFiSoD//5i0AA==
Date: Wed, 31 Jul 2019 16:51:20 +0000
Message-ID: <440A6DAF-B715-4DC0-89B5-89BB3E299200@cisco.com>
References: <156449387998.2643.18137174091685834097.idtracker@ietfa.amsl.com> <m27e7zxpv1.wl-randy@psg.com> <CAMMESsxccHKqaXeGKO1sD9jAiEM7McT9_+VUx4G_nqt_2TX3GA@mail.gmail.com> <m2zhkvw8in.wl-randy@psg.com> <m21ry7vvzk.wl-randy@psg.com> <EC487235-A83C-44F5-B51F-C92A05E56BF8@cisco.com> <016b01d547b9$27e07140$77a153c0$@ndzh.com>
In-Reply-To: <016b01d547b9$27e07140$77a153c0$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1b.0.190715
authentication-results: spf=none (sender IP is ) smtp.mailfrom=enkechen@cisco.com;
x-originating-ip: [2001:420:c0c8:1006::75]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2e33caba-f705-463b-0d0d-08d715d75050
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BY5PR11MB4195;
x-ms-traffictypediagnostic: BY5PR11MB4195:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BY5PR11MB41959C19E41C532216BFFFA6C5DF0@BY5PR11MB4195.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 011579F31F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(136003)(376002)(396003)(39860400002)(346002)(189003)(199004)(13464003)(68736007)(316002)(8936002)(66446008)(66476007)(66556008)(66946007)(64756008)(305945005)(107886003)(33656002)(76116006)(53936002)(6246003)(7736002)(229853002)(6436002)(15650500001)(71200400001)(14454004)(224303003)(6486002)(446003)(71190400001)(2616005)(476003)(86362001)(478600001)(46003)(110136005)(25786009)(54906003)(186003)(58126008)(102836004)(99286004)(2906002)(66574012)(5660300002)(76176011)(11346002)(81166006)(966005)(4326008)(14444005)(486006)(53546011)(81156014)(6506007)(256004)(6512007)(6306002)(6116002)(36756003); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB4195; H:BY5PR11MB3990.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 2A9vIq6FmoV/xN+C47G4Z9U65xvo/Lvky3qsz2vJCF1HUTsn1OSRfwMNfn1M7Cd3S0IQxK1YLG1ORL3dfkm2r+mK6L1EHLV8RpDNQ6ZGkidstMZ74XdzyFreq3TpDTxmNXgDl4tyG5IIpmQbVv5oEchztO3evEULArLS9Ig7AEqyfhDlV4WRvUfvNeni+1aufbxwLUU2bTGZAWNRS68A718ASWsVljXOmJwFjHu3zh0vyArUkD8ohNS50+Fg7z+6d8699AbwONncJ84aN3k5Tr9QBnNNZuqnzQltFlw+o+RP9qfMk6QB3ovPYf0xNCGPHFtLNySh24s3BpYKeDLz6dB9iK1wG0ZL9esJEeaW3WVy0o376pP0zkNyU/QzG98LPwfKKlmPYn60tU3+ef5Oxr+NpStNDQWcgHYvzGvO1pE=
Content-Type: text/plain; charset="utf-8"
Content-ID: <0D009C894F91E04A80B0D85CCFFB612A@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2e33caba-f705-463b-0d0d-08d715d75050
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jul 2019 16:51:20.4440 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: enkechen@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4195
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/rFWE_xn0gNPpw94ufcrH-9CPmbw>
Subject: Re: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-bgp-extended-messages-33: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 16:51:29 -0000
Hi, Sue: As I understand, the term "BGP speaker" is more commonly used, as in this draft also. In this draft, there are numerous occurrences of the term "BGP speaker", and two "BGP listener". It would be good to make them consistency if there is no special reason for a distinction. Thanks. -- Enke -----Original Message----- From: Susan Hares <shares@ndzh.com> Date: Wednesday, July 31, 2019 at 9:02 AM To: "Enke Chen (enkechen)" <enkechen@cisco.com>, 'Randy Bush' <randy@psg.com>, 'Alvaro Retana' <aretana.ietf@gmail.com> Cc: "idr@ietf.org" <idr@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "draft-ietf-idr-bgp-extended-messages@ietf.org" <draft-ietf-idr-bgp-extended-messages@ietf.org>, 'The IESG' <iesg@ietf.org>, "'\"Mirja Kühlewind via Datatracker\"'" <noreply@ietf.org> Subject: RE: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-bgp-extended-messages-33: (with COMMENT) Enke: Your point is that a BGP speaker is defined in RFC5492 and a BGP listener is not? Cheerily, Susan Hares -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Enke Chen (enkechen) Sent: Tuesday, July 30, 2019 9:53 PM To: Randy Bush; Alvaro Retana Cc: idr@ietf.org; idr-chairs@ietf.org; draft-ietf-idr-bgp-extended-messages@ietf.org; The IESG; "Mirja Kühlewind via Datatracker" Subject: Re: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-bgp-extended-messages-33: (with COMMENT) Hi, Randy and Alvaro: Here is a patch that would clarify the capability definition, the issue that I brought up before. It also include changing "BGP listener" to "BGP speaker" in two places. Thanks. -- Enke *** bgp-large-msg-34.txt.orig Tue Jul 30 18:24:32 2019 --- bgp-large-msg-34.txt Tue Jul 30 18:34:07 2019 *************** Internet-Draft Extended Message sup *** 120,148 **** defined with Capability code 6 and Capability length 0. To advertise the BGP Extended Message Capability to a peer, a BGP speaker uses BGP Capabilities Advertisement [RFC5492]. By advertising the BGP Extended Message Capability to a peer, a BGP ! speaker conveys that it is able to send, receive, and properly handle, see Section 4, BGP Extended Messages. - A peer which does not advertise this capability MUST NOT send BGP - Extended Messages, and BGP Extended Messages MUST NOT be sent to it. - Peers that wish to use the BGP Extended Message capability MUST support Error Handling for BGP UPDATE Messages per [RFC7606]. 4. Operation The Extended Message Capability applies to all messages except for the OPEN and KEEPALIVE messages. The former exception is to reduce the complexity of providing backward compatibility. ! A BGP speaker that is capable of sending and receiving BGP Extended Messages SHOULD advertise the BGP Extended Message Capability to its peers using BGP Capabilities Advertisement [RFC5492]. A BGP speaker ! MAY send Extended Messages to a peer if the Extended Message Capability was received from that peer. An implementation that advertises the BGP Extended Message capability MUST be capable of receiving a message with a Length up to and including 65,535 octets. --- 120,145 ---- defined with Capability code 6 and Capability length 0. To advertise the BGP Extended Message Capability to a peer, a BGP speaker uses BGP Capabilities Advertisement [RFC5492]. By advertising the BGP Extended Message Capability to a peer, a BGP ! speaker conveys that it is able to receive, and properly handle, see Section 4, BGP Extended Messages. Peers that wish to use the BGP Extended Message capability MUST support Error Handling for BGP UPDATE Messages per [RFC7606]. 4. Operation The Extended Message Capability applies to all messages except for the OPEN and KEEPALIVE messages. The former exception is to reduce the complexity of providing backward compatibility. ! A BGP speaker that is capable of receiving BGP Extended Messages SHOULD advertise the BGP Extended Message Capability to its peers using BGP Capabilities Advertisement [RFC5492]. A BGP speaker ! MAY send Extended Messages to a peer only if the Extended Message Capability was received from that peer. An implementation that advertises the BGP Extended Message capability MUST be capable of receiving a message with a Length up to and including 65,535 octets. *************** Internet-Draft Extended Message sup *** 157,168 **** 4,096 octet pre- Extended Message limit, so as not to require downstream routers to decompose for peers that do not support Extended Messages. See Section 8. If a BGP message with a Length greater than 4,096 octets is received ! by a BGP listener who has not advertised the Extended Message ! Capability, the listener will generate a NOTIFICATION with the Error Subcode set to Bad Message Length ([RFC4271] Sec 6.1). Bush, et al. Expires January 31, 2020 [Page 3] --- 154,165 ---- 4,096 octet pre- Extended Message limit, so as not to require downstream routers to decompose for peers that do not support Extended Messages. See Section 8. If a BGP message with a Length greater than 4,096 octets is received ! by a BGP speaker who has not advertised the Extended Message ! Capability, the speaker will generate a NOTIFICATION with the Error Subcode set to Bad Message Length ([RFC4271] Sec 6.1). Bush, et al. Expires January 31, 2020 [Page 3] *************** Internet-Draft Extended Message sup *** 175,190 **** speakers which may not support Extended Messages. Therefore, an announcement in an Extended Message where the size of the attribute set plus the NLRI is larger than 4,096 octets may cause lack of reachability. ! A BGP speaker with a mixture of peers some of which have advertised ! the BGP Extended Message capability and some which have not, may ! receive an UPDATE from one of its capable peers that produces an ongoing announcement that is larger than 4,096 octets. When propagating that UPDATE onward to a neighbor which has not advertised ! the BGP Extended Message capability, the sender SHOULD try to reduce the outgoing message size by removing attributes eligible under the "attribute discard" approach of [RFC7606]. If the message is still too big, then it must not be sent to the neighbor ([RFC4271], Section 9.2). Additionally, if the NLRI was previously advertised to that peer, it must be withdrawn from service ([RFC4271], --- 172,187 ---- speakers which may not support Extended Messages. Therefore, an announcement in an Extended Message where the size of the attribute set plus the NLRI is larger than 4,096 octets may cause lack of reachability. ! A BGP speaker that has advertised ! the BGP Extended Message capability to its peers, may ! receive an UPDATE from one of its peers that produces an ongoing announcement that is larger than 4,096 octets. When propagating that UPDATE onward to a neighbor which has not advertised ! the BGP Extended Message capability, the speaker SHOULD try to reduce the outgoing message size by removing attributes eligible under the "attribute discard" approach of [RFC7606]. If the message is still too big, then it must not be sent to the neighbor ([RFC4271], Section 9.2). Additionally, if the NLRI was previously advertised to that peer, it must be withdrawn from service ([RFC4271], -----Original Message----- From: Idr <idr-bounces@ietf.org> on behalf of Randy Bush <randy@psg.com> Date: Tuesday, July 30, 2019 at 6:23 PM To: Alvaro Retana <aretana.ietf@gmail.com> Cc: "idr@ietf.org" <idr@ietf.org>, "\"Mirja Kühlewind via Datatracker\"" <noreply@ietf.org>, "draft-ietf-idr-bgp-extended-messages@ietf.org" <draft-ietf-idr-bgp-extended-messages@ietf.org>, The IESG <iesg@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org> Subject: Re: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-bgp-extended-messages-33: (with COMMENT) i have pushed -34, as there have been lots of small changes since -33 and iesg readers should not have to trip over old fixed junk, and instead find new junk. randy _______________________________________________ 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
- [Idr] Mirja Kühlewind's No Objection on draft-iet… Mirja Kühlewind via Datatracker
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Alvaro Retana
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Mirja Kuehlewind
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Susan Hares
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Mirja Kuehlewind
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Susan Hares
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Alvaro Retana
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Randy Bush
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Randy Bush
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Alvaro Retana
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Randy Bush
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Randy Bush
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Randy Bush
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Enke Chen (enkechen)
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Alvaro Retana
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Randy Bush
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Susan Hares
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Susan Hares
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Enke Chen (enkechen)
- Re: [Idr] Mirja Kühlewind's No Objection on draft… John Scudder
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Susan Hares
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Susan Hares
- Re: [Idr] Mirja Kühlewind's No Objection on draft… Alvaro Retana