IETF Logo Mail Archive

Re: [sidr] wglc draft-ietf-sidr-policy-qualifiers-00

John Curran <jcurran@arin.net> Sun, 14 July 2013 20:10 UTC

Return-Path: <jcurran@arin.net>
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 329C821F9CD3 for <sidr@ietfa.amsl.com>; Sun, 14 Jul 2013 13:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cS2YCWICdrbQ for <sidr@ietfa.amsl.com>; Sun, 14 Jul 2013 13:10:49 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 2499C21F9CEF for <sidr@ietf.org>; Sun, 14 Jul 2013 13:10:47 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id B007F164F72; Sun, 14 Jul 2013 16:10:46 -0400 (EDT)
Received: from ASHXCH01.corp.arin.net (ashxch01.corp.arin.net [199.43.0.17]) by smtp1.arin.net (Postfix) with ESMTP id 322A2164F72; Sun, 14 Jul 2013 16:10:46 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by ASHXCH01.corp.arin.net (199.43.0.17) with Microsoft SMTP Server (TLS) id 14.1.421.2; Sun, 14 Jul 2013 16:10:33 -0400
Received: from CHAXCH02.corp.arin.net ([169.254.2.236]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0328.009; Sun, 14 Jul 2013 16:10:32 -0400
From: John Curran <jcurran@arin.net>
To: Randy Bush <randy@psg.com>
Thread-Topic: [sidr] wglc draft-ietf-sidr-policy-qualifiers-00
Thread-Index: AQHOgFHSYdjl7AtLxEeu76auZ5BeJQ==
Date: Sun, 14 Jul 2013 20:10:10 +0000
Message-ID: <FB6FFE26-B113-4938-B49D-EA419DF0BB5E@arin.net>
References: <24B20D14B2CD29478C8D5D6E9CBB29F6749A84D9@CVA-MB001.centreville.ads.sparta.com> <m2r4f3whgd.wl%randy@psg.com> <95789E5C-80B0-4307-9471-C116DB8219A5@arin.net> <51E2481E.7060103@gmail.com> <m2vc4dlz7l.wl%randy@psg.com>
In-Reply-To: <m2vc4dlz7l.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.149.252.96]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <234705EE591BCF49BCAF19C82F7C820D@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] wglc draft-ietf-sidr-policy-qualifiers-00
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: Sun, 14 Jul 2013 20:10:55 -0000

On Jul 14, 2013, at 3:26 PM, Randy Bush <randy@psg.com> wrote:

>>> overall system robustness is improved by having the policy qualifier
>>> language in RFC6487 more clearly line up with RFC5280 since they are
>>> going to be in use by others.
> 
> robustness?  how does this increase *engineering* robustness?  this is
> not the internet legal task force.  that's icann.

Fix RFC 6487 to make it clear, one way or the other.  Not having some 
folks treat the current spec one way and some treat it another will 
improve *engineering* robustness.

>> I'm not sure I understand the consequences of not publishing this.
> 
> there are no *technical* consequences i can see.  it's rir lawyer fud.


Incorrect, as the origin of the extension was RFC5280.  As someone noted
earlier, PKI technology often provides mechanisms which may be used for 
expressing various legal concepts, but your usage of them is entirely up 
to you (or at least it should be, unless/until folks start forcing their 
legal perspectives on others by disallowing existing extensions...)

/John

v2.29.0 | Report a Bug | By Email | System Status