Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

Sander Steffann <sander@steffann.nl> Mon, 25 May 2020 10:10 UTC

Return-Path: <sander@steffann.nl>
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 DFF463A0B35; Mon, 25 May 2020 03:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 7LyziAF_4DpA; Mon, 25 May 2020 03:10:32 -0700 (PDT)
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 645113A0B21; Mon, 25 May 2020 03:10:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id EA64E49; Mon, 25 May 2020 12:10:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:in-reply-to:date:date:subject:subject :mime-version:content-type:content-type:message-id:from:from :received:received; s=mail; t=1590401424; bh=t0uPVDlDQD/iMOfhidN VQcpGGpjIxogPISSKdAs2yWQ=; b=q7j+NWrWiOFrNrr9QVC608fdxHFNim7FuMj 7uorXRgAhihBHH49dcMSufpqoc8K7GdPa8nC6XE8B8K7lu3YwNrD0jD5TJo7AKvC bIj62XFtQlaOg+d4kBve8VRATZzQg0CQxm7yxRWf0jmVD9J4Z32jhw7I2oOIBXMu n+r3hvZ0=
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 SWXJEKnj3TeD; Mon, 25 May 2020 12:10:24 +0200 (CEST)
Received: from [IPv6:2a02:a213:a300:ce80:1c8c:930:85c1:42] (unknown [IPv6:2a02:a213:a300:ce80:1c8c:930:85c1:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id E64EA3C; Mon, 25 May 2020 12:10:23 +0200 (CEST)
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Message-Id: <43FE1AA8-D2B8-4EBD-8775-69C53D663D25@steffann.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_74D4456B-F759-42B0-8523-E7DC1B1B6176"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
Date: Mon, 25 May 2020 12:10:22 +0200
In-Reply-To: <CAOj+MMFT-JVWOhRoJ3UBsvmYrYvt96N7vkL3_v9Sq4PXzNtzAw@mail.gmail.com>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, 6man <6man@ietf.org>, "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "spring@ietf.org" <spring@ietf.org>
To: Robert Raszuk <robert@raszuk.net>
References: <9CF68CCE-B584-4648-84DA-F2DBEA94622D@cisco.com> <C7C2E1C43D652C4E9E49FE7517C236CB02A2C1AE@dggeml529-mbx.china.huawei.com> <DM6PR05MB6348A22A123AFA7E7345087BAEB70@DM6PR05MB6348.namprd05.prod.outlook.com> <MW3PR11MB457041A967A6BBDA1C7EF0FDC1B70@MW3PR11MB4570.namprd11.prod.outlook.com> <93a31c7f-a102-da59-d9a8-2585cd8e3c65@gmail.com> <MW3PR11MB4570B197EE00C5385DAEE138C1B40@MW3PR11MB4570.namprd11.prod.outlook.com> <5F062FA6-9E2D-46BB-A3D6-257D374D8F92@gmail.com> <MW3PR11MB4570485EEDBADEF3B193BB82C1B40@MW3PR11MB4570.namprd11.prod.outlook.com> <ec63e90e-19fa-cd6c-eacb-4dee44815c99@joelhalpern.com> <MW3PR11MB4570FB2397D4B28A42626802C1B40@MW3PR11MB4570.namprd11.prod.outlook.com> <3bbb28c8-0106-ad63-abf9-c9dc4e428e0c@joelhalpern.com> <MW3PR11MB4570FD37ED32519C677F5E59C1B20@MW3PR11MB4570.namprd11.prod.outlook.com> <DM6PR05MB63486B842CD9DF5BE57FC1A5AEB30@DM6PR05MB6348.namprd05.prod.outlook.com> <CAOj+MMFT-JVWOhRoJ3UBsvmYrYvt96N7vkL3_v9Sq4PXzNtzAw@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KjJd3hUqiGsvpEFUWYcFb8lGROU>
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: Mon, 25 May 2020 10:10:40 -0000

Hi Robert,

> Your below list looks like custom made set of RFP requirements to eliminate any other vendor or any other solution to solve the problem at hand rather then rational list of requirements.

My main customer (an ISP in NL) would fit exactly in the list that Ron sent. They want a simple solution that they can understand and manage, that works over IPv6. Whether the path will include many nodes (>8) is not known at this point, but they want something that can support it in the future.

So the list of requirements isn't that strange.

Cheers,
Sander