Re: [sidr] replies needed quickly RE: possible additional meeting times
Brian Dickson <brian.peter.dickson@gmail.com> Mon, 19 March 2012 22:36 UTC
Return-Path: <brian.peter.dickson@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 AF16D21E802F for <sidr@ietfa.amsl.com>; Mon, 19 Mar 2012 15:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.548
X-Spam-Level:
X-Spam-Status: No, score=-3.548 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 m6DSIS-8CDQY for <sidr@ietfa.amsl.com>; Mon, 19 Mar 2012 15:36:37 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id 4529221E8012 for <sidr@ietf.org>; Mon, 19 Mar 2012 15:36:36 -0700 (PDT)
Received: by wibhr17 with SMTP id hr17so3855204wib.1 for <sidr@ietf.org>; Mon, 19 Mar 2012 15:36:35 -0700 (PDT)
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=NwMX7jySX7lZ3W4nm6vsnnse2wxQCAaWzx80Wuv4Da0=; b=jMvxlBV6rYh/32MyfLl3GgP/N7RNPJw/knoK+mzo/4IhEcR580hG6NB3uPmlbJrOwc uiU1lFgyrdi7ooHD8mpzROhAoyzw5YZM0glHZy1qVkdUfoNwVpeVsLDF1C5F/OpGyaTD 26JIK+zADit+iPJvPgv5mHuM9FS8y5tPdMOyBtnu71neWheZxgj7K+At5XfKGlNIpvSN Ddgx5oCKRYkj4g5EnOxwT8TBIaIp7t/t2iGWA1AO42yfWmvWmEsqbsNz7GcCVHg1JhAw TNbsqEsk5xnKmfk/K0eLnpXaolg6VQDVCqYQUdsASsh1COMZZqswIyzPLKAVZtxHN6fV T2IA==
MIME-Version: 1.0
Received: by 10.216.133.93 with SMTP id p71mr8295067wei.10.1332196595381; Mon, 19 Mar 2012 15:36:35 -0700 (PDT)
Received: by 10.223.88.212 with HTTP; Mon, 19 Mar 2012 15:36:35 -0700 (PDT)
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F60F6C88B2@Hermes.columbia.ads.sparta.com>
References: <24B20D14B2CD29478C8D5D6E9CBB29F60F6C88B2@Hermes.columbia.ads.sparta.com>
Date: Mon, 19 Mar 2012 18:36:35 -0400
Message-ID: <CAH1iCipA=8KBS32cdhvaPNpRbGEppEq2bbC=+89XEnmQAYawSg@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
Content-Type: multipart/alternative; boundary="0016e6dbde57d6b5e404bba030fd"
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] replies needed quickly RE: possible additional meeting times
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, 19 Mar 2012 22:36:37 -0000
Given that there is not a lot of lead time before this, *and* that the IDR meeting is immediate before this slot... And that there is a moratorium on -00 IDs (meaning any material under discussion is limited to already-submitted items)... Discussing the reqs doc then is fine. Perhaps the time slot adjacency to IDR might make for a good time to consider the issues relating to the material on route-leaks. I suspect that trying to conduct the full proposed agenda, would not be such a good idea. Too rushed, would do more harm than good. I would respectfully suggest that having an agenda of interest to the IDR folk, would actually be a good idea. It is entirely possible that insufficient input from IDR participants is leading to "group think", and that more diverse views would improve the WG output. I also suspect that attracting operator representation (who may be at IDR) would be beneficial as well. I think origin-ops, bgpsec-reqs, and bgpsec-ops would be a good slate. I do not think it would be timely to have a review of bgpsec-protocol, just yet, and in particular, might seem even more exclusionary to have this in the secondary SIDR slot. IMHO. Brian On Mon, Mar 19, 2012 at 5:58 PM, Murphy, Sandra <Sandra.Murphy@sparta.com>wrote: > One important point. > > The routing AD needs to know the decision by COB UTC time on Tuesday > (tomorrow). > > So replies are needed quickly. > > --Sandy > > ________________________________________ > From: sidr-bounces@ietf.org [sidr-bounces@ietf.org] on behalf of Murphy, > Sandra [Sandra.Murphy@sparta.com] > Sent: Monday, March 19, 2012 5:37 PM > To: sidr@ietf.org > Subject: [sidr] possible additional meeting times > > The routing ADs have suggested that sidr could use the cancelled EAI > and/or > the cancelled CODEC slot to make up for the cancelled virtual meeting. > > EAI was to meet 1300-1500 Afternoon Session I on Monday March 26. > CODEC was to meet 1120-1220 Afternoon Session I Friday March 30. > > Please speak up as to whether either of these two spots would work. > > --Sandy > _______________________________________________ > 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 >
- [sidr] replies needed quickly RE: possible additi… Murphy, Sandra
- Re: [sidr] replies needed quickly RE: possible ad… Brian Dickson
- Re: [sidr] replies needed quickly RE: possible ad… Murphy, Sandra
- Re: [sidr] replies needed quickly RE: possible ad… George, Wes
- Re: [sidr] replies needed quickly RE: possible ad… Terry Manderson
- Re: [sidr] replies needed quickly RE: possible ad… Tim Bruijnzeels
- Re: [sidr] replies needed quickly RE: possible ad… Stewart Bryant
- Re: [sidr] replies needed quickly RE: possible ad… Eric Osterweil