Re: [sidr] WGLC: draft-ietf-sidr-origin-ops

Christopher Morrow <morrowc.lists@gmail.com> Mon, 14 November 2011 07:07 UTC

Return-Path: <christopher.morrow@gmail.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 D75AA21F84CC for <sidr@ietfa.amsl.com>; Sun, 13 Nov 2011 23:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.54
X-Spam-Level:
X-Spam-Status: No, score=-103.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 AzKjxieQaflm for <sidr@ietfa.amsl.com>; Sun, 13 Nov 2011 23:07:02 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 567D011E80BD for <sidr@ietf.org>; Sun, 13 Nov 2011 23:06:59 -0800 (PST)
Received: by iaeo4 with SMTP id o4so8922871iae.31 for <sidr@ietf.org>; Sun, 13 Nov 2011 23:06:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4dsI/CNOJh5RtwYEFz9EhVFSE2uyFzht5wvBNHfoOtc=; b=n8w8aoIN0YOEXrw2JKp5qUDLMpHcbSkGbJIIEHcefMqjUUPyRG3ATS/0i/TClsz96U J2bNvyRtBLus7XI7qVKXVYLs9umlqXPiFOTBLGUWMKHZb2LUfMbyJNnFo2PxYKP5fnMM FnByCVS50nc4LRq5mJMfGvoVh+o22dvTImbm8=
MIME-Version: 1.0
Received: by 10.231.48.142 with SMTP id r14mr5025544ibf.5.1321254406714; Sun, 13 Nov 2011 23:06:46 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.231.202.142 with HTTP; Sun, 13 Nov 2011 23:06:46 -0800 (PST)
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452386FC8@PRVPEXVS03.corp.twcable.com>
References: <CAL9jLaaOm_=W85r3P990A6DtROTcQwSJ-KBRzAi9ugw1Bo1_cQ@mail.gmail.com> <E4B4DE52-BBB3-4FA0-A75A-B51824BA83E7@lacnic.net> <m2hb3a7uqp.wl%randy@psg.com> <m2fwiu7uji.wl%randy@psg.com> <CAL9jLabcaLnBbZXbNf7Lbv+ppm-h9yO+wBHunG4s1=emOyM6=w@mail.gmail.com> <805B0799-7026-4532-A53C-4CFE3E863A33@castlepoint.net> <m2hb2q4uhj.wl%randy@psg.com> <6054A2B1-40D3-49E6-8972-946D426E830B@castlepoint.net> <DCC302FAA9FE5F4BBA4DCAD4656937791451629610@PRVPEXVS03.corp.twcable.com> <CAL9jLaZ2LYj4J0kzHd0p3a0RGtuPZ+7PiGVPQe2pzquEstchwg@mail.gmail.com> <2D5C11B3-B33E-4215-B15C-C10B0D581C57@tcb.net> <CAL9jLaYDs1X8kM-XMr5-x7w6qJMs2N-vUGJWr1q9gY3BrDN27Q@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD4656937791452386FC8@PRVPEXVS03.corp.twcable.com>
Date: Mon, 14 Nov 2011 02:06:46 -0500
X-Google-Sender-Auth: fweTTwTVJtivNDmCz45zmFaW2ZE
Message-ID: <CAL9jLaaQ+WOvSqDgYefQo76U7J5GDKf1y8jK6p2my3YbdC2Zfg@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] WGLC: draft-ietf-sidr-origin-ops
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: Mon, 14 Nov 2011 07:07:05 -0000

On Mon, Nov 14, 2011 at 1:41 AM, George, Wes <wesley.george@twcable.com> wrote:
>
>> From: christopher.morrow@gmail.com
>
>> there were a slew of changes (or a slew of comments made) requested, a
>> document update happened ~13 days ago, did the changes account for the
>> comments/requests or not?
>>
>
> [WEG] I diffed 11 and 12 when 12 came out, and no, not really. As I recall, Shane already replied that the proposed text (that made it into -12) was not adequate in explaining rationale around the recommendation of "close" for RPKI cache placement, among other things. (cf. emails on 10/31). Don't know if additional changes are pending for -13 based on those comments, but the mail thread died on the 31st with no further responses.
>

ok, I was/am looking for status. I think randy replied to shane's note
(or another note form shane) a bit ago, and talks some about 'close'.
I believe that a new version just arrived in the repository as well.

-chris

> Wes George
>
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
>