Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?

Pradosh Mohapatra <pmohapat@cisco.com> Fri, 08 April 2011 17:47 UTC

Return-Path: <pmohapat@cisco.com>
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F3593A69E2 for <sidr@core3.amsl.com>; Fri, 8 Apr 2011 10:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSF46RYUpQr1 for <sidr@core3.amsl.com>; Fri, 8 Apr 2011 10:47:38 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 8AB053A69D6 for <sidr@ietf.org>; Fri, 8 Apr 2011 10:47:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pmohapat@cisco.com; l=836; q=dns/txt; s=iport; t=1302284964; x=1303494564; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=MmoX+w2LHiv6pVdsKCBaWO1zEiUDCva1hZO5osAXFoM=; b=BPDnC3Fg82R/1HlmRJTIU6r15gWU7hpiNy26vGJ7uJGo9fr1HTgeBixQ YXe3jCyvv3z/uJLUn9gcIysyWH5XMxZUK+ZQllo/puJJzy/f18AzXPIsg DAKGJD2wcgi5rq3Koc3Z5H7YNBsB4pEqdK4ICAOLRMNCELeXg9R9oJ16C M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAL9Jn02rRDoI/2dsb2JhbACmFXeIept0nByFbQSFVYd5
X-IronPort-AV: E=Sophos;i="4.63,325,1299456000"; d="scan'208";a="292332462"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 08 Apr 2011 17:49:24 +0000
Received: from dhcp-171-71-139-171.cisco.com (dhcp-171-71-139-171.cisco.com [171.71.139.171]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p38HnOxa012021; Fri, 8 Apr 2011 17:49:24 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Pradosh Mohapatra <pmohapat@cisco.com>
In-Reply-To: <20110408170400.GC11350@juniper.net>
Date: Fri, 08 Apr 2011 10:49:40 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A88F7EC-12D4-4AAA-92BE-D6A8BEACF776@cisco.com>
References: <BANLkTi=eZ=pQ2gJfiPBfeb4frH8Tncempw@mail.gmail.com> <m21v1i9ha8.wl%randy@psg.com> <BF88D659-1BE5-4DD2-AB24-7A113360DF37@cisco.com> <m2tyea7urr.wl%randy@psg.com> <8BE1C346-6214-4343-9E46-BFA8D96E4B6C@cisco.com> <BANLkTikTqCD4_=-Sjs7ng2qSLn3vYw5qLw@mail.gmail.com> <55B61488-045C-44FA-90DB-83543A6209FB@cisco.com> <m2ipupsmuy.wl%randy@psg.com> <BANLkTinoJRu=hkoiCS=Xj000r3W+n5KnZQ@mail.gmail.com> <F05F2600-9E6C-410B-9EC5-F4245E6F5B88@cisco.com> <20110408170400.GC11350@juniper.net>
To: Hannes Gredler <hannes@juniper.net>
X-Mailer: Apple Mail (2.1081)
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 08 Apr 2011 17:47:39 -0000

> not sure if mandating a single transport is needed at all.
> 
> since the pros and cons of the various transport protocols
> (TCP, TCP-MD5, TCP-AO, IPSec, SSH) are well understood, why not simply
> enumerating the choices and leave it to the operator's local security policy
> which one to deploy ?
> 
> IMO you cannot dictate local security policy as they are different between
> operators. also if the level of containment is sufficiently enough (e.g.
> local-cache only reachable through vrf, not accessible through internet
> it is perfectly reasonable even to load your cache records using vanilla TCP.)

I have no problem listing various transports. I thought there was a suggestion to
keep one of them mandatory to encourage better interoperability. That makes
some sense.

- Pradosh