Re: Size of CR in CRH
"Zafar Ali (zali)" <zali@cisco.com> Thu, 21 May 2020 20:39 UTC
Return-Path: <zali@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7243E3A0C0A for <ipv6@ietfa.amsl.com>; Thu, 21 May 2020 13:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=ieY/j0io; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=MSZsLwDw
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 Xl8RXq3fNCvv for <ipv6@ietfa.amsl.com>; Thu, 21 May 2020 13:39:22 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0254B3A0C08 for <6man@ietf.org>; Thu, 21 May 2020 13:39:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15807; q=dns/txt; s=iport; t=1590093561; x=1591303161; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Rj8CVOGBzMlE3WWxChEsIOTr/okZL9kwkT60TOfUi2A=; b=ieY/j0io20SendmJxzZYlJJKtnXtrnYGK9J7omeNqyERsJZQIbA0X1CN fbjNx8tLPetkbHaxknQ07cNxcWoW6swtfS3DXa7LtNYB3qQBREVm9w1rf l11i/8UzXk+NoOpUMW/2rAYXo3f6wzukARMUm3gNQrEtYZgIHF2UrS+wR 8=;
IronPort-PHdr: 9a23:+jMZTBJeBD/+DDZEttmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeGv6k/gFrAR46d6v9YhazRqa+zEWAD4JPUtncEfdQMUhIekswZkkQmB9LNEkz0KvPmLklYVMRPXVNo5Te3ZE5SHsuta1jbuHb07DMOFFP4LwUmbujwE5TZ2sKw0e368pbPYgJO0Ty6Z746LBi/oQjL8McMho43IacqwRyPqXxNKOk=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AdBwCe5sZe/5NdJa1bChwBAQEBAQEHAQESAQEEBAEBggeBJS9RB29YLyyEJINGA40aJZNVhGaBQoEQA1ULAQEBDAEBGAEKCgIEAQGERAIXgXskOBMCAwEBCwEBBQEBAQIBBQRthVYMhXEBAQEBAwEBEBEdAQEsCwELBAIBCBEBAgEBASgDAgICJQsUAwYIAQEEAQ0FIoMEAYF+TQMuAQ6mUQKBOYhhdoEygwEBAQWCSYJuGIIOAwaBOIJjiV8agUE/gTgMEIFPfj6CZwEBAoEuAQcLATgJDQmCXjOCLY5GDgSDDIYkmiB9CoJTmFIdgmKIfJIXkEmdXAIEAgQFAg4BAQWBaSJmcHAVOyoBgj5QGA2QQAwXg0+FFIVCdAI1AgYBBwEBAwl8i1ABAQ
X-IronPort-AV: E=Sophos;i="5.73,419,1583193600"; d="scan'208,217";a="770342037"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 May 2020 20:38:57 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 04LKcvao018721 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 21 May 2020 20:38:57 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 21 May 2020 15:38:57 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 21 May 2020 16:38:56 -0400
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 21 May 2020 15:38:56 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AF9ujrqTUlz4ehhwQHSE+6NMIBLUE9bAfF1Rh39rosUIawiEvzosKKTlxdRM0KxnPrw4uX3KLej+MdsEHnYQYlE2rWcK1oXZk2k21CoPhm5MR8zxEqrqS3YhSpR4rKPZxh1bAnZT55L4Sa+RxHg0yQ78chdfPr7ZV96ibNrdsgZVNUvpqIaHEYb8t8F8bOH7e39sdDXMyFU7W5K5w2XA6qgBOchCvNnYka7UvW55zXPky7Y55urP+6mIlcyez5MrAQ/C1LP9plMvdFFfAjuLFeENmt3aS8lsJ+Zzv5IaXR+M5K3dD4vQ7xsS1TueEa0k1hncbyGUCdJzFID90KUF0Q==
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=Rj8CVOGBzMlE3WWxChEsIOTr/okZL9kwkT60TOfUi2A=; b=I59yhwPPoqh2K91OuPlt+TkntFWMu298lbxkhwsCfumWYFHNeCiP0V9yIB9TMvL1weOuAC29ksSkOgnIKcymU9Xc6mugbD+t++nyDuLyS7MBOKJzHGIUgxoMVgaqG0D+PSy/Vxd81QKsGApQUtbzIOXDxJlZplJUwWwzJGhqc4tFQ1ZY0XGkVFBRa+hQ62qL2a+R+09N4cd/lrJCJfPW7dwV8zKJMEJERRuK7kCe6oH8EkVC5sVqQsPSVUzcq3OUr4I8EL34RPZebj5ptsM3oKsBsxR+OHWTRpWOjd3Cfsrp+iL8gwZxRSabww9WcMQQJLrA+7JrFqFDfHOs9UUWEw==
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=Rj8CVOGBzMlE3WWxChEsIOTr/okZL9kwkT60TOfUi2A=; b=MSZsLwDwAHxktlr5jsspBo262EhWiZ2uxTwvMcykhiFHmNDEmzsN+aJzZ7w6FqQIg+IyLagou3G3tf9mAuWJvlaF5bCaDuPyMkatGPWhFb67XC8huczoNsfLLvcglDuEEOJ0ZXNSEOjOUAN8Y4z0v7Nbti9BUCnNec26iNJgOyw=
Received: from DM6PR11MB4692.namprd11.prod.outlook.com (2603:10b6:5:2aa::11) by DM6PR11MB3819.namprd11.prod.outlook.com (2603:10b6:5:13f::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23; Thu, 21 May 2020 20:38:55 +0000
Received: from DM6PR11MB4692.namprd11.prod.outlook.com ([fe80::fcce:4248:b4d5:470b]) by DM6PR11MB4692.namprd11.prod.outlook.com ([fe80::fcce:4248:b4d5:470b%5]) with mapi id 15.20.3021.024; Thu, 21 May 2020 20:38:55 +0000
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Nick Hilliard <nick@foobar.org>
CC: 6man <6man@ietf.org>, "Zafar Ali (zali)" <zali@cisco.com>
Subject: Re: Size of CR in CRH
Thread-Topic: Size of CR in CRH
Thread-Index: AdYvFTreFKnyM7AmR8qG9Oc9YkopMAABO0PwAA/1AwAACJdfgAAEftyA
Date: Thu, 21 May 2020 20:38:55 +0000
Message-ID: <008686B1-3F74-4301-AAA3-6A606F14E93E@cisco.com>
References: <C7C2E1C43D652C4E9E49FE7517C236CB02A2BA5D@dggeml529-mbx.china.huawei.com> <DM6PR05MB634888D7D912D561B7F5F0E8AEB70@DM6PR05MB6348.namprd05.prod.outlook.com> <c7b12240-21dd-bb4c-99b6-d590bc298934@foobar.org> <DM6PR05MB63489BBE50753D518C887908AEB70@DM6PR05MB6348.namprd05.prod.outlook.com>
In-Reply-To: <DM6PR05MB63489BBE50753D518C887908AEB70@DM6PR05MB6348.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.37.20051002
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2001:420:c0cc:1003::10b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1251fd71-1fe4-4860-aea8-08d7fdc6fb0a
x-ms-traffictypediagnostic: DM6PR11MB3819:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM6PR11MB381923BEF527E62603042E44DEB70@DM6PR11MB3819.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 041032FF37
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qj7XL7rKcuM7opWJ9UkiK+K2YGe253q+zou14z60JmgjnTruwajnEuqXVT/4WGUGVHS4++aqUQW1cbYbNePIsjIXuJ9FXh+6ut5xKuCM+BAF1tlrIqM7g1A0GzlpR+Jd3slzCf+u0FY2N6XAFugMEFQs0tXnsf0CrHzfWn2WYCDD/3sokFZnJV9fIYp0fTiJzcgDSGWq/Kd5Au5DD5LycDu+aSCGXyAcwr0ixEYgnd3CnKWILX02sTD0+9BNdpEHNWbQStgJ2Xkwka+5sCYlxRc7QdvOZRBVHgMMn3GEQR5uKBq2QBMt7D3Aq+G/GUsRjckLy84LdGF/d5U0YZ/rFyXk0a7byDLKOFDdEAPr8mHHIVI9xWrFWgQWdRxnLfHTcvsHCRhQRXgOy8kWqxsXug==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR11MB4692.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(346002)(39860400002)(136003)(366004)(376002)(396003)(166002)(107886003)(53546011)(5660300002)(6506007)(966005)(478600001)(186003)(71200400001)(4326008)(6512007)(86362001)(2616005)(316002)(66446008)(76116006)(54906003)(33656002)(6486002)(110136005)(64756008)(2906002)(9326002)(66946007)(66476007)(8676002)(66556008)(8936002)(91956017)(36756003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: mL9p2MKaK67s7fi8/9OWt4Qz93U/jsOMQToyA+hTe0mNXx+iqgHwSXivkOYGbVb11kw5sI+TW9DQofY+Q0g3+1hHbcVlRLDUHoLIOFFEo+R+3kzOe++Bc6j2nB/zudcu1vSywH4FiYvqQuxeburk8SpZLYzFuHyYeXD2N9yoosCM1c2RHFfkbgEWczuKhdHaNc+bhdcQDXMnRdtH9pZSl3TnmirXRiRCt0lI2zZNQ307yz6vd3pN9iR34tesE9eVsf5gNx2m3Bn6RzFHnPUbBoiHmSSCb8LH5wLB8KaZyL+fg2zUPlR1m2JrZQMxkMPf8pZ5q7hR/RoPwUG3F73L4FbYFK4KtRVE279nBezsAF+opQ+/yiU33++u0QnmNIVjc4UXU9Wg+qhguEP51p1gpFhpD/ahUAzMKkDt9CwK0fdCBKxrxv4bc5bfXrZiYJGJ8fu9w1q/7virOATLxNL6cUHCDwLVifV7+1USwGGzrwbd7sq9PR1IxCiwV1tBa/KcTg1o1GafkY8k6Ptwr4gy8Q==
Content-Type: multipart/alternative; boundary="_000_008686B13F744301AAA36A606F14E93Eciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1251fd71-1fe4-4860-aea8-08d7fdc6fb0a
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2020 20:38:55.2342 (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: g09IaRK6P3jGdCeQYF56xt/gpnm6riNiHBdau0no95TF7ED0mzUnLSBy6oqO8qn0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3819
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FFM6hcQl45XQEud686WxVkaKRvs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2020 20:39:25 -0000
Hi Ron, Please include the WG in the discussion. I see there is a lot of “on the fly patching” of an “undercooked” document under adoption poll ☹ This is just another indication why having an architecture document is a must for such a big (data plane) change. Thanks Regards … Zafar From: ipv6 <ipv6-bounces@ietf.org> on behalf of Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> Date: Thursday, May 21, 2020 at 10:35 AM To: Nick Hilliard <nick@foobar.org> Cc: 6man <6man@ietf.org> Subject: RE: Size of CR in CRH Nick, Fair enough. Let's initiate a dialog to identify and mitigate the operational complexity. This may require many messages, so let's do that off-line and come back to the mailing list with a summary. Ron Juniper Business Use Only -----Original Message----- From: Nick Hilliard <nick@foobar.org<mailto:nick@foobar.org>> Sent: Thursday, May 21, 2020 6:24 AM To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>> Cc: 6man <6man@ietf.org<mailto:6man@ietf.org>> Subject: Re: Size of CR in CRH [External Email. Be cautious of content] Ron Bonica wrote on 21/05/2020 03:51: Does having two CRH versions really add operational complexity, given that operators will be advised to run one or another? Why not let the operator choose which version is best for its network? They probably know better than us. yeah, it really does add complexity. I don't see a straightforward way of hiding the implementation details in a configuration grammar, at least not portably across vendors. This means implementing complexity right down the tool chain and creating operational / support awareness about the fact there would be N different varieties of CRH, semantically similar but not the same. If you merge networks with different SID sizes, this will be disruptive because there's no clear migration mechanism between one size and another, so changing SID size would mean a flag day. Probably retooling too. It's not just operational complexity, btw - using multiple SID sizes has a long trail of consequences at a protocol level too. For example, how would you signal this in bgp? Separate afis? Same AFI but different tlvs for each different type? Then how do you handle arbitrage? Tom made some suggestions, but these also have consequences. If the prevailing WG opinion is to make multiple SID size options available, then we need to describe in detail how this is going to work right across the board, and how to minimise the downstream impact. If we don't then this pushes the consequence heap into other peoples' laps and they may not appreciate this. Nick -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org<mailto:ipv6@ietf.org> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- Re: Size of CR in CRH Brian E Carpenter
- Re: Size of CR in CRH Erik Kline
- Re: Size of CR in CRH Joel M. Halpern
- Re: Size of CR in CRH Brian E Carpenter
- CRH and RH0 Darren Dukes (ddukes)
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Darren Dukes (ddukes)
- Re: CRH and RH0 Bob Hinden
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 otroan
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 otroan
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 otroan
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Bob Hinden
- RE: CRH and RH0 Ron Bonica
- RE: CRH and RH0 Pengshuping (Peng Shuping)
- Re: CRH and RH0 Tom Herbert
- Re: CRH and RH0 Robert Raszuk
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Robert Raszuk
- RE: CRH and RH0 Ron Bonica
- RE: CRH and RH0 Ron Bonica
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Robert Raszuk
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Robert Raszuk
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Stewart Bryant
- Re: CRH and RH0 Bob Hinden
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Tom Herbert
- Re: CRH and RH0 Ole Troan
- Re: CRH and RH0 Darren Dukes (ddukes)
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Bob Hinden
- RE: CRH and RH0 Ron Bonica
- RE: CRH and RH0 Ketan Talaulikar (ketant)
- RE: CRH and RH0 Ketan Talaulikar (ketant)
- Re: CRH and RH0 otroan
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Darren Dukes (ddukes)
- Re: CRH and RH0 Tom Herbert
- Re: CRH and RH0 Erik Kline
- RE: CRH and RH0 Ketan Talaulikar (ketant)
- RE: CRH and RH0 Ron Bonica
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Darren Dukes (ddukes)
- RE: CRH and RH0 Ketan Talaulikar (ketant)
- RE: CRH and RH0 Ketan Talaulikar (ketant)
- RE: CRH and RH0 Ron Bonica
- Adoption call criteria for CRH? [was: Re: CRH and… John Scudder
- Re: CRH and RH0 Mark Smith
- Re: Adoption call criteria for CRH? [was: Re: CRH… Robert Raszuk
- Re: CRH and RH0 Robert Raszuk
- RE: CRH and RH0 Ron Bonica
- RE: CRH and RH0 Ron Bonica
- Re: CRH and RH0 Gyan Mishra
- Re: Adoption call criteria for CRH? [was: Re: CRH… S Moonesamy
- Re: Adoption call criteria for CRH? [was: Re: CRH… Brian E Carpenter
- Re: Adoption call criteria for CRH? [was: Re: CRH… Darren Dukes (ddukes)
- Re: Adoption call criteria for CRH? [was: Re: CRH… Joel M. Halpern
- Re: CRH and RH0 Darren Dukes (ddukes)
- Re: Adoption call criteria for CRH? [was: Re: CRH… Brian E Carpenter
- Re: Adoption call criteria for CRH? [was: Re: CRH… John Scudder
- Re: Adoption call criteria for CRH? [was: Re: CRH… Bob Hinden
- Re: Adoption call criteria for CRH? [was: Re: CRH… Bob Hinden
- Re: Adoption call criteria for CRH? [was: Re: CRH… S Moonesamy
- Re: CRH and RH0 Tom Herbert
- RE: CRH and RH0 Ron Bonica
- RE: Adoption call criteria for CRH? [was: Re: CRH… Ketan Talaulikar (ketant)
- RE: Adoption call criteria for CRH? [was: Re: CRH… Pengshuping (Peng Shuping)
- Re: Adoption call criteria for CRH? [was: Re: CRH… Darren Dukes (ddukes)
- RE: CRH and RH0 Chengli (Cheng Li)
- RE: Adoption call criteria for CRH? [was: Re: CRH… Chengli (Cheng Li)
- Re: CRH and RH0 Robert Raszuk
- Re: CRH and RH0 Stewart Bryant
- Re: CRH and RH0 Robert Raszuk
- Re: CRH and RH0 Stewart Bryant
- Re: Adoption call criteria for CRH? [was: Re: CRH… Behcet Sarikaya
- Re: Adoption call criteria for CRH? [was: Re: CRH… Voyer, Daniel
- Re: Adoption call criteria for CRH? [was: Re: CRH… 刘毅松
- 答复: Adoption call criteria for CRH? [was: Re: CRH… qinfengwei
- Re: Adoption call criteria for CRH? [was: Re: CRH… Zafar Ali (zali)
- RE: Adoption call criteria for CRH? [was: Re: CRH… Andrew Alston
- Re: Adoption call criteria for CRH? [was: Re: CRH… Tom Herbert
- RE: Adoption call criteria for CRH? [was: Re: CRH… Ron Bonica
- Re: Adoption call criteria for CRH? [was: Re: CRH… Nick Hilliard
- Re: Adoption call criteria for CRH? [was: Re: CRH… Zafar Ali (zali)
- Re: [spring] Adoption call criteria for CRH? [was… Robert Raszuk
- Re: Adoption call criteria for CRH? [was: Re: CRH… John Scudder
- Re: Adoption call criteria for CRH? [was: Re: CRH… Fernando Gont
- Shorter SIDs in SR over IPv6 (Re: Adoption call c… Greg Mirsky
- Re: Adoption call criteria for CRH? [was: Re: CRH… Zafar Ali (zali)
- Re: Adoption call criteria for CRH? [was: Re: CRH… John Scudder
- Re: Adoption call criteria for CRH? [was: Re: CRH… Tom Herbert
- Re: Adoption call criteria for CRH? [was: Re: CRH… Robert Raszuk
- Re: Adoption call criteria for CRH? [was: Re: CRH… Mark Smith
- Re: Adoption call criteria for CRH? [was: Re: CRH… Tom Herbert
- Re: Adoption call criteria for CRH? [was: Re: CRH… Robert Raszuk
- Size of CR in CRH Bob Hinden
- RE: Size of CR in CRH Templin (US), Fred L
- Re: Size of CR in CRH Bob Hinden
- RE: Size of CR in CRH Templin (US), Fred L
- Re: Size of CR in CRH Tom Herbert
- Re: Size of CR in CRH Nick Hilliard
- RE: Size of CR in CRH Ron Bonica
- RE: Size of CR in CRH Templin (US), Fred L
- Re: Size of CR in CRH Brian E Carpenter
- Re: Size of CR in CRH Nick Hilliard
- Re: Size of CR in CRH Joel M. Halpern
- Re: Size of CR in CRH Bob Hinden
- RE: Size of CR in CRH Wang, Weibin (NSB - CN/Shanghai)
- RE: Size of CR in CRH Andrew Alston
- Re: Size of CR in CRH otroan
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Bob Hinden
- Re: Size of CR in CRH Uma Chunduri
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Tom Herbert
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Tom Herbert
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Ole Troan
- Re: Size of CR in CRH Mark Smith
- Re: Size of CR in CRH Fred Baker
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Tom Herbert
- RE: Size of CR in CRH Robert Raszuk
- Re: Size of CR in CRH Bob Hinden
- On adddress sizing (was: Re: Size of CR in CRH) Toerless Eckert
- Re: Size of CR in CRH Toerless Eckert
- RE: Size of CR in CRH Ron Bonica
- RE: Size of CR in CRH Chengli (Cheng Li)
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Robert Raszuk
- Re: Size of CR in CRH Nick Hilliard
- RE: Size of CR in CRH Ron Bonica
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Zafar Ali (zali)
- Re: Size of CR in CRH Robert Raszuk
- Re: Size of CR in CRH Tom Herbert
- RE: Size of CR in CRH Ron Bonica
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Robert Raszuk
- RE: Size of CR in CRH Ketan Talaulikar (ketant)
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Robert Raszuk
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Tom Herbert
- Re: Size of CR in CRH Robert Raszuk
- Re: Size of CR in CRH Zafar Ali (zali)
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Joel M. Halpern
- Re: Size of CR in CRH Zafar Ali (zali)
- Re: Size of CR in CRH Bob Hinden
- RE: Size of CR in CRH Ron Bonica
- RE: Size of CR in CRH Ron Bonica
- Re: Size of CR in CRH Robert Raszuk
- Re: Size of CR in CRH Robert Raszuk
- Re: Size of CR in CRH Joel M. Halpern
- RE: Size of CR in CRH Pablo Camarillo (pcamaril)
- Re: Size of CR in CRH Joel M. Halpern
- Re: Size of CR in CRH Brian E Carpenter
- Re: Size of CR in CRH Gyan Mishra
- Re: Size of CR in CRH Gyan Mishra
- RE: Size of CR in CRH Wang, Weibin (NSB - CN/Shanghai)
- RE: Size of CR in CRH Ketan Talaulikar (ketant)