IETF Logo Mail Archive

Re: [sidr] Updates to rpki-rtr protocol (RFC 6810 bis)

"Murphy, Sandra" <Sandra.Murphy@parsons.com> Thu, 06 March 2014 19:30 UTC

Return-Path: <prvs=8142ff54b0=sandra.murphy@parsons.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1449C1A00F2 for <sidr@ietfa.amsl.com>; Thu, 6 Mar 2014 11:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 P3LHyB7aCjH3 for <sidr@ietfa.amsl.com>; Thu, 6 Mar 2014 11:30:49 -0800 (PST)
Received: from txdal11mx03.parsons.com (txdal11mx03.parsons.com [206.219.199.111]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0391A0084 for <sidr@ietf.org>; Thu, 6 Mar 2014 11:30:49 -0800 (PST)
Received: from pps.filterd (txdal11mx03 [127.0.0.1]) by txdal11mx03.parsons.com (8.14.5/8.14.5) with SMTP id s26JUWFq030307; Thu, 6 Mar 2014 13:30:43 -0600
Received: from m4.sparta.com (m4.sparta.com [157.185.61.2]) by txdal11mx03.parsons.com with ESMTP id 1jexqur61x-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 06 Mar 2014 13:30:42 -0600
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id s26JUetX000407; Thu, 6 Mar 2014 13:30:40 -0600
Received: from HSV-CAS003.huntsville.ads.sparta.com (HSV-CAS003.huntsville.sparta.com [10.62.8.138]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id s26JUYhJ025481; Thu, 6 Mar 2014 13:30:34 -0600
Received: from KRAVEN.huntsville.ads.sparta.com (10.62.8.137) by HSV-CAS003.huntsville.ads.sparta.com (10.62.8.138) with Microsoft SMTP Server (TLS) id 14.2.347.0; Thu, 6 Mar 2014 13:30:33 -0600
Received: from HSV-MB001.huntsville.ads.sparta.com ([fe80::292e:cdb7:1aa6:ce74]) by kraven.huntsville.ads.sparta.com ([::1]) with mapi id 14.02.0342.003; Thu, 6 Mar 2014 13:30:33 -0600
From: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
To: Randy Bush <randy@psg.com>
Thread-Topic: [sidr] Updates to rpki-rtr protocol (RFC 6810 bis)
Thread-Index: AQHPOV/V5Crks2I3o0ehVyh5N92J/JrUtauA//+g8NeAAHF3gP//na1C
Date: Thu, 06 Mar 2014 19:30:33 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F694A077C5@HSV-MB001.huntsville.ads.sparta.com>
References: <5318AD76.6060204@bbn.com>,<m2d2hzb2ca.wl%randy@psg.com>
In-Reply-To: <m2d2hzb2ca.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.185.61.23]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-03-06_06:2014-03-05, 2014-03-06, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=0 kscore.compositescore=0 circleOfTrustscore=48.445471141256 compositescore=0.0148378968684884 urlsuspect_oldscore=0.195307920112602 suspectscore=0 recipient_domain_to_sender_totalscore=4066 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=38 recipient_domain_to_sender_domain_totalscore=12528 rbsscore=0.0148378968684884 spamscore=0 recipient_to_sender_domain_totalscore=47 urlsuspectscore=0.1 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1403060107
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/_Ka12Yg2N-4U3UfrLiiJxYLQK9Y
Cc: Rob Austein <sra@hactrn.net>, "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] Updates to rpki-rtr protocol (RFC 6810 bis)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 06 Mar 2014 19:30:51 -0000

>> The new PDU assumes the wg agrees to the revision of the router cert
>> draft.  Correct?  So this is tied to progress of a revised router cert
>> draft?  Is somebody already on board to provide that new draft?>
>
>maybe you missed draft-ymbk-rpki-rtr-keys-01.txt

Rob's message said that the new PDU would "support binding a single router key to multiple ASNs".

I presumed that this came from the change to the router cert that Rob spoke about in the sidr meeting this week.  I presumed he was speaking about a change to draft-ietf-sidr-bgpsec-pki-profiles-06, in this part 

   Each BGPSEC Router Certificate MUST include the AS Resource
   Identifier Delegation extension, as specified in section 4.8.11 of
   [RFC6487].  The AS Resource Identifier Delegation extension MUST
   include exactly one AS number, and the "inherit" element MUST NOT be
   specified.

The 6810 change Rob suggests (and draft-ymbk-rpki-rtr-keys-01.txt, too) define a new PDU carrying the router cert's AS info to the router.  But draft-ietf-sidr-bgpsec-pki-profiles-06 needs to change, too, if multiple ASNs are going to be there to carry.

>how much bureaucracy can we create here?

This isn't a big job - a change from "exactly one" to "at least one" might be sufficient.  I think that's substantive, not bureaucratic.

--Sandy

________________________________________
From: Randy Bush [randy@psg.com]
Sent: Thursday, March 06, 2014 1:37 PM
To: Murphy, Sandra
Cc: Rob Austein; sidr@ietf.org
Subject: Re: [sidr] Updates to rpki-rtr protocol (RFC 6810 bis)

> I would expect that adding a new PDU would be a new document, not a
> revision to the protocol document.  Would you agree?

the version numbers all change

> The new PDU assumes the wg agrees to the revision of the router cert
> draft.  Correct?  So this is tied to progress of a revised router cert
> draft?  Is somebody already on board to provide that new draft?

maybe you missed draft-ymbk-rpki-rtr-keys-01.txt

how much bureaucracy can we create here?

randy

v2.23.0 | Report a Bug | By Email