Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc-access-network-identifier-04 - Ends May 2, 2013
Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 17 April 2013 21:22 UTC
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3A5521E80DE for <dhcwg@ietfa.amsl.com>; Wed, 17 Apr 2013 14:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level:
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=0.300, 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 h8-FEantjO4c for <dhcwg@ietfa.amsl.com>; Wed, 17 Apr 2013 14:22:45 -0700 (PDT)
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by ietfa.amsl.com (Postfix) with ESMTP id CE30721E80B1 for <dhcwg@ietf.org>; Wed, 17 Apr 2013 14:22:43 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id z13so2076052lbh.27 for <dhcwg@ietf.org>; Wed, 17 Apr 2013 14:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dqDk/LRQWf01yA6k8jTqBQUy1xTMU+DZxfdgIDUMUw0=; b=MmuF1ZCCnt//VIuNnvr/zn/iH95ptmKHoM6d930/XpSBJULn0WIZ73MS5OENnUMllt /SL3wgbGp+rWZjDAZYM58S7rItAwfC5BS8gqAeUwFhoWq5u7JUVhj1LkH/+UkC8SDfZk H+QccAopkn3lOe+LXGwsa23J4Fl9VR2TIuCgFq2dDtQM1JwKMvWQABCoYJQDMtkfOTop E1G+kvqIoba6bvhx6ibjkTtCrpTVEPIGW0JkZk9i6e61w34n12gU6yN5skvEYzU7DLEJ 3nraLmoThj60UCO6mUmpINa059DzR359BNi09Car6b0Ltjd/jpcONA8I7DbKpkA8wEj/ 5vtA==
MIME-Version: 1.0
X-Received: by 10.112.74.98 with SMTP id s2mr4529889lbv.9.1366233762724; Wed, 17 Apr 2013 14:22:42 -0700 (PDT)
Received: by 10.114.175.140 with HTTP; Wed, 17 Apr 2013 14:22:42 -0700 (PDT)
In-Reply-To: <24C0F3E22276D9438D6F366EB89FAEA810233F0C@xmb-aln-x03.cisco.com>
References: <8D23D4052ABE7A4490E77B1A012B63077514D333@mbx-01.win.nominum.com> <24C0F3E22276D9438D6F366EB89FAEA810233F0C@xmb-aln-x03.cisco.com>
Date: Wed, 17 Apr 2013 16:22:42 -0500
Message-ID: <CAC8QAceRUehOV9PWU68oofXOLd3EwwBs0NS=vh37T0KHmKsngw@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
Content-Type: multipart/alternative; boundary="14dae94738cd1b82c504da951692"
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc-access-network-identifier-04 - Ends May 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2013 21:22:46 -0000
Hi Sri, I think that Client/Server behaviour (Section 7 & 9) in the draft needs some clarification. Please check Bernie's mail: http://www.ietf.org/mail-archive/web/dhcwg/current/msg11144.html on draft-ietf-dhc-80211-option-01.txt. Also please check the operation described in Li's draft: http://tools.ietf.org/html/draft-xue-dhc-location-option-01 Regards, Behcet On Wed, Apr 17, 2013 at 10:47 AM, Sri Gundavelli (sgundave) < sgundave@cisco.com> wrote: > Hi Ted, > > Thanks for your comments. > > This requirement is not coming from any SDO. We believe this is a generic > requirement for IETF based IP architectures. > > As you are aware, many operators are deploying large scale SP WiFI > networks. These deployments are based on standard IETF protocols and > architectures (tunneling, mobility, Routing, AAA protocols ...). In many > of these deployments the subscriber services are tied to the access > network, for example, the initial portal page may be different based on > the user location (SSID, AP Mac address ..). These parameters are > typically carried on DHCP option-82, and are coded in a vendor basis. > There is no standard encoding that a backend system can reliably depend on > for learning these parameters. In the past when WiFI was largely contained > to enterprises, with single vendor solutions, this worked fine. But, now > in many deployments there are multi-vendor systems and interop is > required. The draft is trying to attempt to fix that gap. We want to drive > this work in DHC, not using a liaison statement, but as a gap in IETF > protocols, to solve a practical deployment issue and improve > interoperability. > > I'm copying Hui Deng, CMCC. They are deploying large scale SP WIFI > networks and he can comment on this. > > > > > Regards > Sri > > > > > > > > > > > > On 4/17/13 7:59 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote: > > >When we talked about this earlier, I said that it might be better to have > >this work done in DHC rather than forcing it to find a new working group > >because it seemed to be something that was being asked for by other SDOs. > > However, the authors never said anything about that over and above what > >they've already said in meetings, so I don't actually have a clear > >picture of who is asking for this. Looking in the data tracker, I don't > >find any liaison statement requesting that this work be done. > > > >The authors have expressed a great deal of urgency about this work, and I > >don't want to delay it any further, so I will state that as a > >participant, I'm in favor of the working group taking on the work. > >However, with my AD hat on, I would like to get some kind of actual > >request for help from the SDOs who want this functionality before the end > >of the call for adoption. Otherwise I think Bernie's concern that the > >DHC working group really isn't qualified to evaluate the validity of the > >option contents will remain unaddressed, and I think it's a valid concern. > > > >The request from the SDOs should be of the form "we need DHCP options to > >deliver the following bits of functionality," and should briefly describe > >the functionality that's needed, and refer to the documents that the SDO > >is working on that support this need. > > > >If this need is not really coming from these SDOs, but rather from some > >IETF working group, then perhaps Bernie's original observation was > >correct, and this work should be done in that working group instead. > > > >_______________________________________________ > >dhcwg mailing list > >dhcwg@ietf.org > >https://www.ietf.org/mailman/listinfo/dhcwg > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www.ietf.org/mailman/listinfo/dhcwg >
- [dhcwg] WG Adoption Call - draft-bhandari-dhc-acc… Bernie Volz (volz)
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Ted Lemon
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Sri Gundavelli (sgundave)
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Behcet Sarikaya
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Florin Baboescu
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Jouni Korhonen
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Jouni Korhonen
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Behcet Sarikaya
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Rajat Ghai
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Hui Deng
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Behcet Sarikaya
- Re: [dhcwg] WG Adoption Call - draft-bhandari-dhc… Prashant Jhingran (pjhingra)