Re: [sidr] AD review and progressing draft-ietf-sidr-as-migration-02

Alia Atlas <akatlas@gmail.com> Mon, 09 February 2015 18:36 UTC

Return-Path: <akatlas@gmail.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 32B781A1B6E for <sidr@ietfa.amsl.com>; Mon, 9 Feb 2015 10:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 FRNQrYxyJmdL for <sidr@ietfa.amsl.com>; Mon, 9 Feb 2015 10:36:00 -0800 (PST)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7C5A1A1A9A for <sidr@ietf.org>; Mon, 9 Feb 2015 10:36:00 -0800 (PST)
Received: by mail-yh0-f43.google.com with SMTP id c41so2220390yho.2 for <sidr@ietf.org>; Mon, 09 Feb 2015 10:36:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3QEY8lVyiTmybHWT5U+YCnMPZjkTksbZpRjbXpwWFNk=; b=0Akm0ve3oYtN6n5NumcgAiwh85iSUOIthaEtYBh16sWb1U5Yk/+NCSCiU6gu2mMeXG swvfHzHfnsqXmHiQH7ywz3jDV7yVCLPPHOjciDwld9BaBzH/alEv3CR0D8Reixw1tTf4 LxwpcQl74TWSPkGt59a8uX5e9tpqsjUb+1ewd3S6T+KF6owXzPhpDkvqbjVhqycOwFCZ LK3oz5v6WRjaGdN7Y2j1mLSMNcno1+Sd51YCAai2L0981jR/TLE1fSDet4Rvu0QxcGzZ 0ITEbv1Id4sAFstfkcNipWZQcyGhsJ0lZPbFP6J8+kxcS04dGO18EcBY9B9s1A1qKepp uQaw==
MIME-Version: 1.0
X-Received: by 10.236.203.108 with SMTP id e72mr7062889yho.48.1423506959971; Mon, 09 Feb 2015 10:35:59 -0800 (PST)
Received: by 10.170.133.80 with HTTP; Mon, 9 Feb 2015 10:35:59 -0800 (PST)
In-Reply-To: <CAL9jLaYKT9578CHM_pXYL292i1H26_xiiA4eK9oYVMj3FkriTg@mail.gmail.com>
References: <CAG4d1reTZ8xcR8EO61Ap_VHsEdfgh19tk46o0ns+QFRAD=mPDQ@mail.gmail.com> <D0F5254B.41CBA%wesley.george@twcable.com> <D0F699CD.41F96%wesley.george@twcable.com> <D0F7DBE5.420F0%wesley.george@twcable.com> <m2siej10ej.wl%randy@psg.com> <D0FA6E3C.424DB%wesley.george@twcable.com> <CAL9jLaYKT9578CHM_pXYL292i1H26_xiiA4eK9oYVMj3FkriTg@mail.gmail.com>
Date: Mon, 09 Feb 2015 13:35:59 -0500
Message-ID: <CAG4d1rdUTS_x1Z-RMuk=dy4Q90E07xgicVamkVnEqM5OBr+T7g@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
Content-Type: multipart/alternative; boundary="089e0160b506af38f3050eac0a31"
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/vSpsRh8grLZIjC4f1RYjLa3oUWA>
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] AD review and progressing draft-ietf-sidr-as-migration-02
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: Mon, 09 Feb 2015 18:36:03 -0000

I've passed the draft back to the WG.  When the necessary conversation and
WGLC has occurred again,
I'll be happy to progress it quickly.

Thanks,
Alia

On Sat, Feb 7, 2015 at 1:03 PM, Christopher Morrow <morrowc.lists@gmail.com>
wrote:

> sounds like a good topic for the mic/front/preso in dallas... to me at
> least.
>
> On Sat, Feb 7, 2015 at 9:34 AM, George, Wes <wesley.george@twcable.com>
> wrote:
> > I posed some questions about this in my WGLC review of bgpsec spec, but
> > haven't heard anything back. Current schedule has this being evaluated by
> > IESG prior to our next meeting. If we need to discuss during the meeting
> > in Dallas, we could certainly delay processing of the document. It has a
> > normative block on the bgpsec spec, so it's not like it's getting
> > published right away anyway.
> >
> > Thanks,
> >
> > Wes
> >
> >
> >
> > On 2/6/15, 11:15 AM, "Randy Bush" <randy@psg.com> wrote:
> >
> >>has the wg really looked at 5.2 and 5.3 with respect to how the ibgp
> >>hacks affect the bgpsec spec?
> >>
> >>randy
> >
> >
> > 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.
> > _______________________________________________
> > sidr mailing list
> > sidr@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidr
>
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>