Re: [sidr] Expected protocols in rpki-rtr

"Montgomery, Douglas" <dougm@nist.gov> Tue, 02 August 2011 17:47 UTC

Return-Path: <dougm@nist.gov>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28A221F84EB for <sidr@ietfa.amsl.com>; Tue, 2 Aug 2011 10:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level:
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[AWL=0.262, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0sSk9AG88Fl0 for <sidr@ietfa.amsl.com>; Tue, 2 Aug 2011 10:47:35 -0700 (PDT)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id E716D11E80C2 for <sidr@ietf.org>; Tue, 2 Aug 2011 10:47:30 -0700 (PDT)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.323.0; Tue, 2 Aug 2011 13:47:38 -0400
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Tue, 2 Aug 2011 13:47:05 -0400
From: "Montgomery, Douglas" <dougm@nist.gov>
To: Paul Hoffman <paul.hoffman@vpnc.org>, sidr wg list <sidr@ietf.org>
Date: Tue, 02 Aug 2011 13:47:36 -0400
Thread-Topic: [sidr] Expected protocols in rpki-rtr
Thread-Index: AcxRPDDVTPjx4NSDRw25pWD/07oaqA==
Message-ID: <CA5DB039.5C296%dougm@nist.gov>
In-Reply-To: <84CE1DEB-76A8-4123-B20D-0AEB72CA694B@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sidr] Expected protocols in rpki-rtr
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 17:47:38 -0000

As a practical matter, what do you think the effect of the "MUST" in the
last sentence will be?

-- 
Doug Montgomery ­ Mgr. Internet & Scalable Systems Research / ITL / NIST






On 8/2/11 1:34 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

>Greetings again. Section 7 of draft-ietf-sidr-rpki-rtr-14 has a list of
>supported transports. However, it does not list the one that some people
>have said that they expect it to be run under sometimes, namely bare TCP.
>If we all know that this is likely to be the case, we should have it
>listed in the document. I propose the following for the end of section 7,
>just before 7.1:
>
>   Caches and routers MAY use unprotected TCP as a transport,
>   even though this provides none of the security protections of
>   the other protocols listed here. Unprotected TCP MUST only be
>   used when there is other forms of trusted security in place.
>
>Of course, we can also just ignore the fact that many users want to do
>this, but being honest in the document might be better than pretending
>otherwise.
>
>--Paul Hoffman
>
>_______________________________________________
>sidr mailing list
>sidr@ietf.org
>https://www.ietf.org/mailman/listinfo/sidr