Re: [nbs] NBS conflict with MEXT

"David Harrington" <ietfdbh@comcast.net> Mon, 01 November 2010 23:58 UTC

Return-Path: <ietfdbh@comcast.net>
X-Original-To: nbs@core3.amsl.com
Delivered-To: nbs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB39628C0D6 for <nbs@core3.amsl.com>; Mon, 1 Nov 2010 16:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level:
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXhuZ+4KJ+HX for <nbs@core3.amsl.com>; Mon, 1 Nov 2010 16:58:30 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 090403A67FB for <nbs@ietf.org>; Mon, 1 Nov 2010 16:58:29 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta07.westchester.pa.mail.comcast.net with comcast id Rs3K1f0041ei1Bg57zyZPa; Mon, 01 Nov 2010 23:58:33 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta24.westchester.pa.mail.comcast.net with comcast id RzyY1f00V2JQnJT3kzyZZf; Mon, 01 Nov 2010 23:58:33 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'The IESG'" <iesg@ietf.org>, <nbs@ietf.org>
References: <BF345F63074F8040B58C00A186FCA57F29F6C36FE6@NALASEXMB04.na.qualcomm.com><00EC5F89-8402-446C-A74E-72F530AF956F@ericsson.com><243735B8-AFCA-4CD3-9364-FFE5ECC61766@isi.edu> <62D06173-1430-4C9E-B153-F778E8E86686@isi.edu>
Date: Tue, 2 Nov 2010 07:58:37 +0800
Message-ID: <3C11E378B70942BABE4F9F1123324049@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-Index: Act6FniEIRSjNGpKQj+6X3feVotNSgABvqeA
In-Reply-To: <62D06173-1430-4C9E-B153-F778E8E86686@isi.edu>
Cc: 'WG Chairs' <wgchairs@ietf.org>
Subject: Re: [nbs] NBS conflict with MEXT
X-BeenThere: nbs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Name based sockets discussion list <nbs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nbs>, <mailto:nbs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nbs>
List-Post: <mailto:nbs@ietf.org>
List-Help: <mailto:nbs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nbs>, <mailto:nbs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2010 23:58:31 -0000

Hi,

NBS touches a wide variety of protocols and layers.
That is a major reason why the BOF is NOT a WG-forming BOF, but a
technology-exploring BOF.
We are looking to see what technologies might be impacted, and where
such work should be done.

The API bridges between an Application and a transport, and work could
be done in either area.
NBS separates identifier from locator, so could be impacted by HIP
and/or LISP.
NBS will discuss mobility, so there are multiple related mobility WGs
to avoid.
NBS might substitute one transport conection for another, which could
impact security.
All of this will need to be operated and managed, so will likely
impact OPS (where SHIM had problems due to operator pushbock, as I
recall).

As I see it, no matter where you put this BOF, it will conflict with
some other scheduled sessions.
After the BOF discussions, then we can determine what technologies
(and areas) might be impacted.
Then we can either redirect the work to existing WGs, or have one or
more BOFs focused on specific aspects.
I encourage the bulk of the discussion to happen on the NBS MAILING
LIST, not in the BOF.

So my tendency is to say, let's just leave the BOF where it is.

(and I consider the WG-Chairs list the wrong place for this
discussion. Please use the nbs@ietf.org list.
https://www.ietf.org/mailman/listinfo/nbs )

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: wgchairs-bounces@ietf.org 
> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Joe Touch
> Sent: Tuesday, November 02, 2010 6:44 AM
> To: Joe Touch
> Cc: WG Chairs; Laganier, Julien
> Subject: Re: NBS conflict with MEXT
> 
> 
> 
> On Nov 1, 2010, at 3:39 PM, Joe Touch <touch@isi.edu> wrote:
> 
> > I am hoping none of the issues cited will be in scope, and 
> thus this overlap wouldn't matter.  
> > 
> > NBS can - and IMO should - be limited to effect during initial
conn
> 
> Connection. All other proposals require revision to transport 
> and higher protocols that rely on IP adds as endpoint names, 
> and this revisits HIP and is not described yet enough. 
> 
> Joe 
> 
> 
> > 
> > On Nov 1, 2010, at 2:16 PM, Christian Vogt 
> <christian.vogt@ericsson.com> wrote:
> > 
> >> For me, moving the NBS BoF to Wednesday morning would be fine.
> >> 
> >> - Christian
> >> 
> >> 
> >> 
> >> You wrote:
> >> 
> >>> Folks -
> >>> 
> >>> I know it is very late but I just noticed that the NBS 
> BoF conflicts
> >>> With MEXT on Monday morning, which is especially 
> unfortunate since NBS
> >>> has impact on session continuity, mobility and ID/loc 
> split, which are
> >>> also related to MEXT. I am also very interested in NBS 
> but needs to
> >>> co-chair MEXT
> >>> 
> >>> I am not sure something can still be done to resolve the 
> conflict, but
> >>> FWIW, I'd like to know how people would feel about a swap 
> that looks
> >>> relatively benign: swap NBS with another TSV morning 
> session, such as 
> >>> the TSVWG on Wednesday morning.  
> >>> 
> >>> Thanks,
> >>> 
> >>> --julien
> >>