Re: [sidr] draft-ietf-sidr-rpki-rtr-17.txt

"t.petch" <ietfc@btconnect.com> Fri, 14 October 2011 17:57 UTC

Return-Path: <ietfc@btconnect.com>
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 D4EE321F8C60 for <sidr@ietfa.amsl.com>; Fri, 14 Oct 2011 10:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level:
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260, 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 o80wrxb68jep for <sidr@ietfa.amsl.com>; Fri, 14 Oct 2011 10:57:47 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD1E21F8C57 for <sidr@ietf.org>; Fri, 14 Oct 2011 10:57:46 -0700 (PDT)
Received: from host86-163-147-122.range86-163.btcentralplus.com (HELO pc6) ([86.163.147.122]) by c2bthomr14.btconnect.com with SMTP id ETB04073; Fri, 14 Oct 2011 18:57:44 +0100 (BST)
Message-ID: <02b301cc8a91$bb397e20$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <m2ehymuufo.wl%randy@psg.com> <CAL9jLaZmXSPT+F=+K43rTuG3+H_5JW6WUHEmwrj356bU63eubQ@mail.gmail.com>
Date: Fri, 14 Oct 2011 18:52:55 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4E987817.004A, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.10.14.145715:17:7.586, ip=86.163.147.122, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __URI_NO_PATH, __FRAUD_REFNUM, BODY_SIZE_1300_1399, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr14.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020B.4E987819.0063, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] draft-ietf-sidr-rpki-rtr-17.txt
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: Fri, 14 Oct 2011 17:57:47 -0000

----- Original Message -----
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: "Randy Bush" <randy@psg.com>; "t.petch" <ietfc@btconnect.com>; "Samuel
Weiler" <weiler@watson.org>
Cc: "sidr wg list" <sidr@ietf.org>
Sent: Friday, October 14, 2011 4:52 PM
On Sun, Oct 9, 2011 at 10:10 AM, Randy Bush <randy@psg.com> wrote:
> could the chairs please pass $subject to the iesg? i am only aware of
> one possible issue raised in wglc, tp asked for a hyphen somewhere but
> did not respond to my asking him to be specific where. if this mystery
> is solved, i presume it can be handled in the iesg or auth48.

I believe Tom's issue was addressed in conversation (with mr weiler?),
but if not probably we can catch the problem in IESG review comment
recovery :)

<tp>
Chris

I raised the problem but the solution, replacement text, was supplied by Joe in
an e-mail to yourself (and the list) 27Sep2011.

Tom Petch

</tp>
I'll forward on the document to the IESG today + the writeup, of course.

-Chris

(If the authors could wrangle:
  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)

  ** Downref: Normative reference to an Informational RFC: RFC 4808

that'd be helpful to the process, again these can be caught in the
IESG review fixups as well)