Re: [netext] Comments on draft-koodli-netext-multiaccess-indicator-03.txt
Rajeev Koodli <rkoodli@cisco.com> Thu, 22 March 2012 22:59 UTC
Return-Path: <rkoodli@cisco.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 194EC21E801B for <netext@ietfa.amsl.com>; Thu, 22 Mar 2012 15:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.435
X-Spam-Level:
X-Spam-Status: No, score=-109.435 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, 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 YBAK7BFK26a4 for <netext@ietfa.amsl.com>; Thu, 22 Mar 2012 15:59:33 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF2421E800F for <netext@ietf.org>; Thu, 22 Mar 2012 15:59:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12206; q=dns/txt; s=iport; t=1332457173; x=1333666773; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=yqqPgyIdmftdw7WjL/eWir2EkMbs0lGhIABW82KYpwA=; b=BJi9XbbJcREO96arEfnI1qL94bn3PLAuVCIOEOfchFhvy3S7wvWIKiHn y0WrH2tteLSJloXvR5iufCiBeTFycRbhK26QARyr+BKYlP7D+9UdKVNxL 2gViTb3A2haWkJVL+IT6SwKnBxatMIX/aGLPZp21ykxY4Ddaa1SB7Szld w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAFCua0+tJXHA/2dsb2JhbABDgk+jaYgdAYdzfYEHggkBAQEDAQEBAQ8BKjELBQ0BCBEDAQIBTwYoCAEBBA4FCRmHYwULnniXJIlthncEiCMziSWDZIslCgODDoFogwc
X-IronPort-AV: E=Sophos; i="4.73,633,1325462400"; d="scan'208,217"; a="65719022"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-9.cisco.com with ESMTP; 22 Mar 2012 22:59:32 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id q2MMxWi6005847; Thu, 22 Mar 2012 22:59:32 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Mar 2012 17:59:32 -0500
Received: from 10.21.93.10 ([10.21.93.10]) by XMB-RCD-111.cisco.com ([72.163.62.153]) with Microsoft Exchange Server HTTP-DAV ; Thu, 22 Mar 2012 22:59:31 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Thu, 22 Mar 2012 16:02:54 -0700
From: Rajeev Koodli <rkoodli@cisco.com>
To: Hui Deng <denghui02@gmail.com>
Message-ID: <CB90FDAE.1A871%rkoodli@cisco.com>
Thread-Topic: [netext] Comments on draft-koodli-netext-multiaccess-indicator-03.txt
Thread-Index: Ac0If+nM5XKlog+UvU2qt+d4gzqaqw==
In-Reply-To: <CANF0JMBaLjwqWtaBBo1RobU4prApSoCLKX9v_KgJvhVqF3YxmQ@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3415276974_19707241"
X-OriginalArrivalTime: 22 Mar 2012 22:59:32.0006 (UTC) FILETIME=[71670C60:01CD087F]
Cc: netext@ietf.org
Subject: Re: [netext] Comments on draft-koodli-netext-multiaccess-indicator-03.txt
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 22:59:36 -0000
Hi Hui, On 3/21/12 12:52 AM, "Hui Deng" <denghui02@gmail.com> wrote: > Hi Rajeev, > > Excuse me for coming back late, > > Rajeev:> No problem. > > 1. I see your point, in the current draft, it only says logical interface, > would better to describe how really means of that, for example, you may need > implement virtual interface which take over all the interfaces. > > Rajeev:> There is a NetExt ID dedicated for describing the Logical Interface. > That¹s a good place for such a description. IMO. > > 2. One apn is future, today there are still multiple APNs > > Rajeev:> The design should support >1 APN¹, so that it can support =1 APN¹ > > 3. Where you would like to discuss your EAP draft? I have read it, would like > to comment on it. > > Rajeev:> NetExt is a good place. > > Thanks. > > -Rajeev > > Best > > -Hui > 2012/3/8 Rajeev Koodli <rkoodli@cisco.com> >> >> Hi Hui, >> >> Thank you for reviewing the draft. >> >> 1: I see your point. It¹s called Multi-access Indicator because it is able to >> do flow mobility. You can have multiple interfaces but not be ³able and >> willing² to do flow mobility >> >> 2: You mean that flow mobility indication should be made specific to an APN? >> I like your suggestion - what would be a good use case beyond the ³default² >> APN? >> >> BTW, have you seen >> http://tools.ietf.org/html/draft-valmikam-eap-attributes-wifi-epc-integration >> -00 >> >> Regards, >> >> -Rajeev >> >> >> >> >> On 3/6/12 8:11 PM, "Hui Deng" <denghui02@gmail.com >> <http://denghui02@gmail.com> > wrote: >> >>> Hi Rajeev, >>> >>> I have comments on your draft, you are assuming wifi eap authentication >>> could indicate handover, so >>> 1) maybe handover indicator is better than multiaccess indicator because UE >>> connect to WIFI and need handover, it has already two interfaces >>> >>> 2) I recommend you could support APN information in your eap extension, >>> without this information such indicatotion may lead wrong APN (wrong source >>> address) >>> >>> thanks a lot for your consideration >>> >>> -Hui >>> >>>> ---------- Forwarded message ---------- >>>> From: <internet-drafts@ietf.org <http://internet-drafts@ietf.org> > >>>> Date: 2012/3/3 >>>> Subject: I-D Action: draft-koodli-netext-multiaccess-indicator-03.txt >>>> To: i-d-announce@ietf.org <http://i-d-announce@ietf.org> >>>> >>>> >>>> >>>> A New Internet-Draft is available from the on-line Internet-Drafts >>>> directories. >>>> >>>> Title : Multi-access Indicator for Mobility >>>> Author(s) : Rajeev Koodli >>>> Jouni Korhonen >>>> Filename : draft-koodli-netext-multiaccess-indicator-03.txt >>>> Pages : 8 >>>> Date : 2012-03-02 >>>> >>>> When a Mobile Node attaches to the mobile network using multiple >>>> access networks, it is important for the Mobile Network Gateway to >>>> know whether the Mobile Node is capable of simultaneous multi-access, >>>> so that the former can distribute the traffic flows using the most >>>> appropriate interface. This document defines a new EAP attribute >>>> which can be used for such an indication to the Mobile Network >>>> Gateway. The document also reserves a new MIP6-Feature-Vector flag. >>>> >>>> >>>> A URL for this Internet-Draft is: >>>> http://www.ietf.org/internet-drafts/draft-koodli-netext-multiaccess-indicat >>>> or-03.txt >>>> >>>> Internet-Drafts are also available by anonymous FTP at: >>>> ftp://ftp.ietf.org/internet-drafts/ >>>> >>>> This Internet-Draft can be retrieved at: >>>> ftp://ftp.ietf.org/internet-drafts/draft-koodli-netext-multiaccess-indicato >>>> r-03.txt >>>> >>>> _______________________________________________ >>>> I-D-Announce mailing list >>>> I-D-Announce@ietf.org <http://I-D-Announce@ietf.org> >>>> https://www.ietf.org/mailman/listinfo/i-d-announce >>>> Internet-Draft >>>> <https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft> >>>> directories: http://www.ietf.org/shadow.html >>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >>>> >>> >>> >>> >>> _______________________________________________ >>> netext mailing list >>> netext@ietf.org <http://netext@ietf.org> >>> https://www.ietf.org/mailman/listinfo/netext > >