Re: Size of CR in CRH
"Zafar Ali (zali)" <zali@cisco.com> Thu, 21 May 2020 14:35 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 BB86C3A09D3 for <ipv6@ietfa.amsl.com>; Thu, 21 May 2020 07:35:16 -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=UsKxtZVl; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=h6F7Nw/7
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 3JFgtUj_r7ok for <ipv6@ietfa.amsl.com>; Thu, 21 May 2020 07:35:13 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8F923A0D78 for <6man@ietf.org>; Thu, 21 May 2020 07:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=40353; q=dns/txt; s=iport; t=1590071705; x=1591281305; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=je+xDijx5aMYeHWqjnB7I4fOc+6/vhtvsnd8IAI6Qis=; b=UsKxtZVljGdGG+Bkrb8MHBPpi2/r8aqLjhhJEXHwLNWT2YclUcVfzeLv vSlDV2zZPOrJhwj1y9xtjUtMwqcBDue12gKbtSsYv2eeVlZXXYdn4WNNx Ien9ArQ2fqgai1wOUCaHJLdE1tXyLLYy4EH/ILg9th0LYduwRgIDIZduW g=;
IronPort-PHdr: 9a23:HLs7MxOPFUy1C5j8cAQl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEvKwz3kXARpfG6LRChvaF+6zjWGlV55GHvThCdZFXTBYKhI0QmBBoG8+KD0D3bZuIJyw3FchPThlpqne8N0UGAs/ldUDR5Hu/8W1aFhD2LwEgIOPzF8bbhNi20Obn/ZrVbk1IiTOxbKk0Ig+xqFDat9Idhs1pLaNixw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CfBQC8kMZe/4ENJK1bChwBAQEBAQEHAQESAQEEBAEBggeBJS8jLgdvWC8sCoQag0YDjT6YO4FCgRADVQsBAQEMAQEjCgIEAQGERAIXgXokOBMCAwEBCwEBBQEBAQIBBQRthVYMhXEBAQEBAgESER0BATcBBAsCAQgRAQIBAQEhAQYDAgICMBQDBggCBAENBSKDBAGBfk0DDiABAgynGAKBOYhhdoEygwEBAQWCSYJsGIIOAwaBOIJjiV8agUE/gREnHIJNPoJnAQECAYEtAQcEBwE4CQ0Jgl4zgi2RZIYkin2QIAqCU4gpkCkdnXWQSYltk28CBAIEBQIOAQEFgWkiZnBwFWUBgj5QGA2QQAwFEoNPhRSFQnQ3AgYBBwEBAwl8iXSBNQGBDwEB
X-IronPort-AV: E=Sophos;i="5.73,417,1583193600"; d="scan'208,217";a="482560952"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 May 2020 14:35:04 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id 04LEZ4MK026864 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 21 May 2020 14:35:04 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 21 May 2020 09:35:04 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 21 May 2020 09:35:04 -0500
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 21 May 2020 10:35:03 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ni0lgaSIipOAfVDumR5QlcLcaeC9AFt7zvyU/YBD8/1aAZibjHGK3zRiza8APaxUqU+jOTDQeemto8RkY79U6pklWigkYTzeduTENEK4A5tH4pQCKpTmzVWLxOjEB01T52xcox8KwA36rLxdnqBa6o3KTtx9ThR1+JbIG5RrOACpMcxKZdyWBorbszdhrmVKlHrnlIuAtc7u3ctGRVicF3LilFK+SQU4Av7WFje2VdZ1/ya5VgdAJpxn8srbSa+p72BALaKzJBKEcCqjDYxGOrfOq6KvYC0aNWIkPxWS16EBWKJ0xDR9SoltR2PQps5+e9Vu2Ya8HV1uC0IChQTuUw==
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=je+xDijx5aMYeHWqjnB7I4fOc+6/vhtvsnd8IAI6Qis=; b=STO9BDKhSc+tn9AK4hfKG0ewWvZMhLgo6LZCIrMIlBZMH414p6rFZFi3PzALv4qNCEf3C8wmDyhE/Uc/OO6GTSBpQmZ0CFcGImIN2a3+xCgIGXdoHWfU9CMzPwn38bqStipE7spfAersEqXLzdFmgOBIJhdHsAa3uuVVyD6L75Lo4WnvPjL91/UcbGMNOTj8R16h6xPYXwOpGELWEi8mYNHc6W0KmwcUzIYJ3pTjqfdNMcBjgqDQxQyEJVFuyLj+w9Am66GvNlY79IWORkK1nYPLTjsfuedmJ+TfAKOIx9AKnj4SKM8opSUudRsOOCWohVulpPABdKJVUkkzaleJqA==
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=je+xDijx5aMYeHWqjnB7I4fOc+6/vhtvsnd8IAI6Qis=; b=h6F7Nw/7k+l7Esy5ldrsP2HP4IpgCiyA+IOxDABbFy8Quknsn6wcAE4YlN/e+whRVLwdRDgTdk3yjSy00ZEaqu/gih1JepD3+yAyC2GWMXp1pT/fncwUmz3aE362OTiuOE9FCTkJ4df8d+0fEfOtVdWzttxqzeTACX0oCEyHcjI=
Received: from DM6PR11MB4692.namprd11.prod.outlook.com (2603:10b6:5:2aa::11) by DM6PR11MB4492.namprd11.prod.outlook.com (2603:10b6:5:201::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3000.26; Thu, 21 May 2020 14:35:02 +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 14:35:02 +0000
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Robert Raszuk <robert@raszuk.net>, Ron Bonica <rbonica@juniper.net>
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: AQHWLvTos+L/fvTLz06pL456naDiAaixyYsAgABt0oCAACG3AA==
Date: Thu, 21 May 2020 14:35:02 +0000
Message-ID: <3B7335D8-5A73-461E-8C78-BBD33E214F68@cisco.com>
References: <CAOj+MMFsy=dDciY=TMwSf75CZCr_i1Mfv6oUiPs5U6hT2Bq94w@mail.gmail.com> <DM6PR05MB6348D0DB381145F1A4C53450AEB70@DM6PR05MB6348.namprd05.prod.outlook.com> <CAOj+MMHT=TWqf=A71PhvCcrFggCQ=okRrP=sGaO4hrcbmsCvGw@mail.gmail.com>
In-Reply-To: <CAOj+MMHT=TWqf=A71PhvCcrFggCQ=okRrP=sGaO4hrcbmsCvGw@mail.gmail.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: raszuk.net; dkim=none (message not signed) header.d=none;raszuk.net; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [47.185.212.154]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1f4392c0-1353-4bb8-5e2f-08d7fd9425e0
x-ms-traffictypediagnostic: DM6PR11MB4492:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM6PR11MB449241E4546358C0A1B33F64DEB70@DM6PR11MB4492.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 041032FF37
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: hpC8PIP/gKacNp1+Y21p6a0EgStwiLlyiyKolwDqkJbZj0kiqRw0VILaJp7qTotdpIRjpjYHEhDVWxJ5xXgaYYgfxX1e/ipOki2wpJr76zOxPA6vjenGt3WfKrprgN9IbkUKBlqdpRumWLjgY5KM14tCz7dsWXcZIpoC7i73xwzX46bB4erjFGbiAOn+n2kqPnM2DRCgzZyeYvSRdPdHDgZiI80U7fHif1fF76wyRyfA49WCMSd0VSJXtSLMAxoviYrcXIPUb6uPVA/fpq9+wpSXSYzpyFfbxXTBVW6NliOXuinjT4mRPcTN0f07XqLg+BOIOkCs0tiOc620PaJVQBTGzOAv04ZTuOtczOGr9jsy8UEAG5Sjsm2rKH/7V7lW8drjJFFLymhtP7Y9oHu1GUJaj35x2zszX9OkfmLPVnFJADeniYhh2elKkLsFGt4kmAWH+edAmm+1bvjwM2WLlGUGUJ59Sp1tofWMQPobTHZPjjrK9iZM5pskGjSaisK6seb/g68IRlhyaRcKxLW20A==
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)(39860400002)(136003)(366004)(376002)(396003)(346002)(64756008)(66556008)(66476007)(66574014)(66446008)(107886003)(5660300002)(76116006)(91956017)(66946007)(33656002)(478600001)(316002)(166002)(966005)(110136005)(54906003)(4326008)(2616005)(86362001)(26005)(6486002)(186003)(71200400001)(2906002)(53546011)(6506007)(36756003)(8676002)(6512007)(9326002)(8936002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: bnw8zOCOnbPqEP59RqzU42yNcPChvjmO+R3t5c6CWLdtqLJKgUWqNaTn1mt7VYDAZAdaQHYOECrs35q+6N2dvtl8NvtHOHzTHFbCsuB0/3kIVArK0eanEIH4hQz3uI19aUDU7Wd7EC7bgA4VarnlfsmrMdKradD8NHguuvjH+I8W6dAbF58QWGzz7O7AlEnS2E4Zs2W5WFfCfjwqcFilW4JPPEJnsZG/xuF6sd1Dqq0GyVSZf1uECOWK1JlA8Gvbh7bKM8qbYBIt7iynZatEDE2svzwz/goQR/6BqmrG7Kb7Ui6/Ac3/FiIkmsxk/khsPIZKcSPOeF5DSQbPOXl+crg8JEw4EBvzIZx2MIWE5JZiajLgT4M5WNwju5kMhCSa5aCaQU3z2XTK4XA72MtYE4FmGSGvcA3JhlIyHqtQZ69KsOTSIP3CSDsZU/M+YSlQanw1MVugAB0lW1+YKvFe6RMOP2jYdn/bCk2X4+4mPCBiZZlfy6MOdtStY2SjD3H2
Content-Type: multipart/alternative; boundary="_000_3B7335D85A73461E8C78BBD33E214F68ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1f4392c0-1353-4bb8-5e2f-08d7fd9425e0
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2020 14:35:02.7557 (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: D4ToHaQfP6Xp+YIwfZrxECQVQ8YAOlch8xLUiOR5Tc8Aj+5opNcX2h6nOS49XXc8
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4492
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aGXN9mQw8vaY9k05yYJO59XV8mg>
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 14:35:17 -0000
Hi Ron, Just to add to what Robert mentioned. “Re: [Ron] I think that this example refutes the premise of your (comment) argument” No, it does not "refutes the premise of" Robert's comment. It raises more questions and cements the need for a proper architecture and use-case document. In rev 10 of the CRH document[1], the following SIDs with normative reference to SRm6 were defined: "The following are valid segment types: o Adjacency. o Node. o Binding. " The ISIS extension for CRH still defines how to advertise prefix SIDs and Adjacency SIDs. In your example you introduced the notion of ranges ”0-65,000 (global significance; prefix SID) 65,001 - 65,565 (local significance; adjacency SIDs). Where is this defined? Did you not remove the above-quoted text in Feb. 2020? Will the working group see Binding SID definition back into the draft, too? What else … draft-bonica-6man-vpn-dest-opt? draft-alston-spring-crh-bgp-signalling? draft-bonica-6man-seg-end-opt-07? draft-ssangli-bess-bgp-vpn-srm6-01? Crh-PCEP draft? …. Etc. [1] https://tools.ietf.org/html/draft-bonica-6man-comp-rtg-hdr-10#section-4 Thanks Regards … Zafar From: ipv6 <ipv6-bounces@ietf.org> on behalf of Robert Raszuk <robert@raszuk.net> Date: Thursday, May 21, 2020 at 4:35 AM To: Ron Bonica <rbonica@juniper.net> Cc: 6man <6man@ietf.org> Subject: Re: Size of CR in CRH Ron, > Now recall that identifiers have node local significance. I was talking about case described in yr draft section 7: "Applications can: o Allocate SIDs so that they have domain-wide significance." While not a must - it is an option. So I believe my observation stays valid till draft either removes that option or describes scaling properties differences between both domain wide and local significance of the SIDs. Thx, R. On Thu, May 21, 2020 at 4:01 AM Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>> wrote: Robert, Consider the following network: * Contains 65,000 routers * Each router has 500 directly connected neighbors or fewer * Uses 16-bit CRH In this network, each node might have 65,499 CRH-FIB entries: * 64,999 CRH-FIB entries cause packets to follow the least-cost path to another node in the domain * 500 CRH-FIB entries cause packets to traverse a specific link to a specific neighbor. As a mnemonic device, an operator might assign identifiers as follows: * 0-65,000 identify CRH-FIB entries that cause packets to follow the least-cost path to another node in the domain * 65,001 – 65,565 identify CRH-FIB entries that that cause packets to traverse a specific link to a specific neighbor. Now recall that identifiers have node local significance. So, Node A and Node B might both have a CRH-FIB entry that is identified by the value 65,001. However: * The CRH-FIB entry on Node A causes packets to traverse a particular link towards Node X * The CRH-FIB entry on Node B causes packets to traverse a different link towards Node Y. I think that this example refutes the premise of your argument, so there is not further need to address the conclusion. Ron Juniper Business Use Only From: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>> Sent: Wednesday, May 20, 2020 6:20 PM 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] HI, So just to make sure I understand this analogy of 16 bit -- 2^16 = 65536 nodes. I think this is only on paper. Imagine I have 1000 routers so if I divide the 16 bit space by 1000 I get at most 65 local node behaviours if anyone would like to embed such into the SID. That means that if my router have more then 65 interfaces I am not able to steer packets by src route out of my router ... I must always depend on the lookup of next SID how to forward the packets. That also means that if I want to apply any form of NP in segment endpoint I am quite limited to the number of local functions I could use. To conclude - Let me restate to what I and others already said - flat SID space domain wide in mapping plane is a mistake. Yes this is like MPLS, but this does not make it great again due to that legacy.. Many thx, R.
- 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)