From mipshop-bounces@ietf.org Wed Jul 9 14:47:47 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15EBD3A693C; Wed, 9 Jul 2008 14:47:47 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89FBA3A693C for ; Wed, 9 Jul 2008 14:47:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.669 X-Spam-Level: X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 4gFNl70ZHY48 for ; Wed, 9 Jul 2008 14:47:42 -0700 (PDT) Received: from dakia3.marvell.com (dakia3.marvell.com [65.219.4.28]) by core3.amsl.com (Postfix) with ESMTP id A75943A67B0 for ; Wed, 9 Jul 2008 14:47:42 -0700 (PDT) X-ASG-Debug-ID: 1215640075-15c5010c0000-Psfj6Z X-Barracuda-URL: http://dakia3.marvell.com:80/cgi-bin/mark.cgi Received: from maili.marvell.com (localhost [127.0.0.1]) by dakia3.marvell.com (Spam Firewall) with ESMTP id 935E450A012; Wed, 9 Jul 2008 14:47:55 -0700 (PDT) Received: from maili.marvell.com (maili.marvell.com [10.68.76.51]) by dakia3.marvell.com with ESMTP id poG52ETWakpXwP8z; Wed, 09 Jul 2008 14:47:55 -0700 (PDT) Received: from sc-exch03.marvell.com (sc-exch03.marvell.com [10.68.76.198]) by maili.marvell.com (Postfix) with ESMTP id 4300C5B18A; Wed, 9 Jul 2008 14:47:55 -0700 (PDT) X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: Call for presentations Date: Wed, 9 Jul 2008 14:47:46 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Call for presentations Thread-Index: AcjiDWylIoo3V+MFTsOW5PByrejvAA== From: "Stefano Faccin" To: X-Barracuda-Connect: maili.marvell.com[10.68.76.51] X-Barracuda-Start-Time: 1215640075 X-Barracuda-Virus-Scanned: by Marvell Mail Gateway at marvell.com Subject: [Mipshop] Call for presentations X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1217927150==" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org This is a multi-part message in MIME format. --===============1217927150== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E20D.6CE239C1" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8E20D.6CE239C1 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hello MIPSHOPers, Vijay and I are putting together the agenda for the MIPSHOP session. If you would like to request a slot, please let us know ASAP. =20 The following items are already on the agenda: - Use of DHCP for discovering MoS service in the visited link + related discussion - PMIPv6 handover optimizations - presentation of current proposed solutions - AAA-based Handover key for FMIPv6 =20 Cheers, Stefano ------_=_NextPart_001_01C8E20D.6CE239C1 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hello MIPSHOPers,

Vijay and I are putting together the agenda for the = MIPSHOP session. If you would like to request a slot, please let us know = ASAP.

 

The following items are already on the = agenda:

- Use of DHCP for = discovering MoS service in the visited link + related = discussion

- PMIPv6 handover = optimizations – presentation of current proposed solutions

- AAA-based Handover key for = FMIPv6

 

Cheers,

Stefano

------_=_NextPart_001_01C8E20D.6CE239C1-- --===============1217927150== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop --===============1217927150==-- From mipshop-bounces@ietf.org Thu Jul 10 08:15:02 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F33EB3A6891; Thu, 10 Jul 2008 08:15:01 -0700 (PDT) X-Original-To: mipshop@ietf.org Delivered-To: mipshop@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 37BFF3A6891; Thu, 10 Jul 2008 08:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080710151501.37BFF3A6891@core3.amsl.com> Date: Thu, 10 Jul 2008 08:15:01 -0700 (PDT) Cc: mipshop@ietf.org Subject: [Mipshop] I-D Action:draft-ietf-mipshop-mstp-solution-05.txt X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF. Title : Mobility Services Framework Design (MSFD) Author(s) : T. Melia, et al. Filename : draft-ietf-mipshop-mstp-solution-05.txt Pages : 27 Date : 2008-07-10 This document describes a mobility services framework design (MSFD) for the IEEE 802.21 Media Independent Handover (MIH) protocol that addresses identified issues associated with the transport of MIH messages. The document also describes mechanisms for mobility service (MoS) discovery and transport layer mechanisms for the reliable delivery of MIH messages. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mipshop-mstp-solution-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mipshop-mstp-solution-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-07-10081028.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop --NextPart-- From rafkone05@biz.by Fri Jul 11 09:06:34 2008 Return-Path: X-Original-To: ietfarch-mipshop-archive@core3.amsl.com Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2C5A3A67E3 for ; Fri, 11 Jul 2008 09:06:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.4 X-Spam-Level: **** X-Spam-Status: No, score=4.4 tagged_above=-999 required=5 tests=[BAYES_95=3, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SARE_BIZOP=0.7, SUBJ_ALL_CAPS=2.077] 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 ReZxILHVqsJS for ; Fri, 11 Jul 2008 09:06:33 -0700 (PDT) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.230]) by core3.amsl.com (Postfix) with ESMTP id BBA8B3A6768 for ; Fri, 11 Jul 2008 09:06:32 -0700 (PDT) Received: by hu-out-0506.google.com with SMTP id 24so1283216hud.14 for ; Fri, 11 Jul 2008 09:06:50 -0700 (PDT) Received: by 10.210.76.12 with SMTP id y12mr6660711eba.151.1215792382907; Fri, 11 Jul 2008 09:06:22 -0700 (PDT) Received: by 10.210.39.15 with HTTP; Fri, 11 Jul 2008 09:06:22 -0700 (PDT) Message-ID: <14bbeb3b0807110906t12076197med39fe548eaf7f77@mail.gmail.com> Date: Fri, 11 Jul 2008 16:06:22 +0000 From: "Rafael Kone" Reply-To: rafaelkone63@yahoo.fr Subject: URGENT PLEASE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_20767_21382663.1215792382897" To: undisclosed-recipients:; ------=_Part_20767_21382663.1215792382897 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline *From: Mr Rafael Kone.* *Tel: +226 78 15 47 47 Dear, * *This message might meet you in utmost surprise. However, it's just my urgent need for foreign partner that made me to contact you for this transaction. I assured you honesty and reliability to champion this business opportunity when i prayed to God about you. I am a banker by profession in BURKINA-FASO, WEST AFRICA and currently holding the post foreign remittance director in our bank. I have the opportunity of transferring the left over funds ($15, Million Dollars) of one of my bank clients who died along with his entire family on 26th December 2003 in a plane crash.* *I am inviting you for a business deal where this money can be shared between us in the ratio of 50/50 if you agree to my business proposal. Further details of the transfer will be forwarded to you as soon as i receive your return mail immediately as soon as you receive this letter. Please indicate your willingness by sending the below information for more clarification and easy communication. (1) YOUR FULL NAME (2) YOUR CONTACT ADDRESS (3) YOUR TEL AND FAX NUMBER (4) YOUR OCCUPATION (5) YOUR AGE* *Hoping to hear from you as soon as possible. Regards* *Rafael Kone.* ------=_Part_20767_21382663.1215792382897 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

From: Mr Rafael Kone.

Tel: +226 78 15 47 47

Dear,

 

This message might meet you in utmost surprise. However, it's just my urgent need for foreign partner that made me to contact you for this transaction. I assured you honesty and reliability to champion this business opportunity when i prayed to God about you.

I am a banker by profession in BURKINA-FASO, WEST AFRICA and currently holding the post foreign remittance director in our bank. I have the opportunity of transferring the left over funds ($15, Million Dollars) of one of my bank clients who died along with his entire family
on 26th December 2003 in a plane crash.


I am inviting you for a business deal where this money can be shared between us in the ratio of 50/50 if you agree to my business proposal. Further details of the transfer will be forwarded to you as soon as i receive your return mail immediately as soon as you receive this letter.

Please indicate your willingness by sending the below information for more
clarification and easy communication.

(1) YOUR FULL NAME
(2) YOUR CONTACT ADDRESS
(3) YOUR TEL AND FAX NUMBER
(4) YOUR OCCUPATION
(5) YOUR AGE

 

Hoping to hear from you as soon as possible.
Regards

Rafael Kone.


 
------=_Part_20767_21382663.1215792382897-- From mipshop-bounces@ietf.org Fri Jul 11 21:27:26 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB45D3A6B33; Fri, 11 Jul 2008 21:27:26 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 094913A6B33 for ; Fri, 11 Jul 2008 21:27:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.468 X-Spam-Level: X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599] 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 Mvax+P9+08Eb for ; Fri, 11 Jul 2008 21:27:25 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id D43233A6983 for ; Fri, 11 Jul 2008 21:27:24 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 9D65D198727; Sat, 12 Jul 2008 07:27:43 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id F3C7C1986D8; Sat, 12 Jul 2008 07:27:40 +0300 (EEST) Message-ID: <487832BA.4080209@piuha.net> Date: Sat, 12 Jul 2008 00:27:38 -0400 From: Jari Arkko User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: "Telemaco Melia (tmelia)" References: <483170AA.2000403@piuha.net><4831AC1B.7020501@piuha.net> <4860FF97.6070902@piuha.net> In-Reply-To: X-Virus-Scanned: ClamAV using ClamSMTP Cc: gorry@erg.abdn.ac.uk, draft-ietf-mipshop-mstp-solution@tools.ietf.org, Mipshop Subject: Re: [Mipshop] AD review of draft-ietf-mipshop-mstp-solution X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org I have reviewed the updated draft (thanks for the update!), and compared it to my earlier comments and Gorry's review comments. Most of the problems were corrected. The remaining parts seem easy to address, perhaps you could even do it before the I-D deadline on Monday. Here's what remains: In Gorry's review he pointed out that the UDP usage guidelines document recommends an exponential back-off mechanism. The mstp draft deviates from this, and I'm not sure its appropriate to do so. Note that the guidelines had only a recommendation, not a requirement. But its not clear that you actually want to avoid an exponential back-off. Its easy to think of situations (such as the base station going down) where there would be a significant amount of retransmission traffic from a large number of hosts. Section 5.3 talks about "step c" which I no longer can find. I would like to see Appendix A removed; for the reasons discussed earlier the relay approach has problems. I don't think we want to publish a spec that hints that the relay approach should be done. I did not notice changes relating to the following: > MIH Transport Options > > > The document does not talk about how servers know the capabilities of > clients that send event/command services to. Is this a part of the IEEE > definitions, and you subscribe to a particular event stream? In any > case, the document should talk about this and point to the relevant > other specifications where needed. > > >> > In the case where DHCP is used for node discovery and authentication >> > of the source and content of DHCP messages is required, network >> > administrators SHOULD use DHCP authentication option described in >> > [RFC3118 ], where available or rely upon link layer security. This >> > will also protect the DHCP server against denial of service attacks >> > to. [RFC3118 ] provides mechanisms for both entity authentication and >> > message authentication. >> > > I think the overall recommendation is good, but practically no one is > going to deploy RFC 3118. With this in mind, I would like to see the > above paragraph explain in more detail the security implications of > relying on link layer security. > Jari _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Fri Jul 11 22:49:00 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5D653A6B52; Fri, 11 Jul 2008 22:49:00 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C5903A6B4D for ; Fri, 11 Jul 2008 22:48:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.595 X-Spam-Level: X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599] 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 yoSeK3e7Mdz4 for ; Fri, 11 Jul 2008 22:48:58 -0700 (PDT) Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id 1C3BF3A6B52 for ; Fri, 11 Jul 2008 22:48:57 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 12 Jul 2008 01:49:15 -0400 Message-ID: In-Reply-To: <487832BA.4080209@piuha.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mipshop] AD review of draft-ietf-mipshop-mstp-solution Thread-Index: Acjj16S3DdP5j6xeRQCY3QLejYbvtQACdZPg References: <483170AA.2000403@piuha.net><4831AC1B.7020501@piuha.net><4860FF97.6070902@piuha.net> <487832BA.4080209@piuha.net> From: "Vijay Devarapalli" To: "Jari Arkko" , "Telemaco Melia (tmelia)" Cc: gorry@erg.abdn.ac.uk, draft-ietf-mipshop-mstp-solution@tools.ietf.org, Mipshop Subject: Re: [Mipshop] AD review of draft-ietf-mipshop-mstp-solution X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi Jari, > -----Original Message----- > From: mipshop-bounces@ietf.org > [mailto:mipshop-bounces@ietf.org] On Behalf Of Jari Arkko > Sent: Friday, July 11, 2008 9:28 PM > To: Telemaco Melia (tmelia) > Cc: gorry@erg.abdn.ac.uk; > draft-ietf-mipshop-mstp-solution@tools.ietf.org; Mipshop > Subject: Re: [Mipshop] AD review of draft-ietf-mipshop-mstp-solution > I would like to see Appendix A removed; for the reasons discussed > earlier the relay approach has problems. I don't think we want to > publish a spec that hints that the relay approach should be done. I think we need a little bit more discussion on this before removing it. Personally, I would like to hear from folks who participated in the design team. I also want to figure out what exactly 3GPP wants in this space for their ANDSF feature. I also want to chat with Vivek (.21 chair) to see if they care about this scenario. It might be premature to remove this. Vijay _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Sat Jul 12 04:08:44 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AC7C3A691C; Sat, 12 Jul 2008 04:08:44 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A62D63A691C for ; Sat, 12 Jul 2008 04:08:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.484 X-Spam-Level: X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599] 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 5psSKNZWISgR for ; Sat, 12 Jul 2008 04:08:43 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id D1DD83A68EC for ; Sat, 12 Jul 2008 04:08:42 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 2EEFD1986E3; Sat, 12 Jul 2008 14:09:02 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id E8C5C1986A4; Sat, 12 Jul 2008 14:09:00 +0300 (EEST) Message-ID: <487890CD.3030301@piuha.net> Date: Sat, 12 Jul 2008 07:09:01 -0400 From: Jari Arkko User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Vijay Devarapalli References: <483170AA.2000403@piuha.net><4831AC1B.7020501@piuha.net><4860FF97.6070902@piuha.net> <487832BA.4080209@piuha.net> In-Reply-To: X-Virus-Scanned: ClamAV using ClamSMTP Cc: gorry@erg.abdn.ac.uk, draft-ietf-mipshop-mstp-solution@tools.ietf.org, Mipshop Subject: Re: [Mipshop] AD review of draft-ietf-mipshop-mstp-solution X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Vijay, > I think we need a little bit more discussion on this before removing it. > OK, but I take it that this discussion applies to the entire issue, and not just the appendix question. If we were to support relay-based discovery after the discussion, Appendix A wouldn't be sufficient. I was commenting on this on the assumption that the authors agreed with the issue that I raised, since the actual support was removed. If we still need to talk about that, that's fine. I would be very interested to hear more .21 and 3GPP viewpoints on this. Jari _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Mon Jul 14 05:45:38 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6991B28C242; Mon, 14 Jul 2008 05:45:38 -0700 (PDT) X-Original-To: mipshop@ietf.org Delivered-To: mipshop@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 576483A68F3; Mon, 14 Jul 2008 05:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080714124502.576483A68F3@core3.amsl.com> Date: Mon, 14 Jul 2008 05:45:02 -0700 (PDT) Cc: mipshop@ietf.org Subject: [Mipshop] I-D Action:draft-ietf-mipshop-4140bis-04.txt X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF. Title : Hierarchical Mobile IPv6 Mobility Management Author(s) : H. Soliman, et al. Filename : draft-ietf-mipshop-4140bis-04.txt Pages : 37 Date : 2008-07-14 This document introduces extensions to Mobile IPv6 and IPv6 Neighbour Discovery to allow for local mobility handling. Hierarchical mobility management for Mobile IPv6 is designed to reduce the amount of signalling between the Mobile Node, its Correspondent Nodes, and its Home Agent. The Mobility Anchor Point (MAP) described in this document can also be used to improve the performance of Mobile IPv6 in terms of handover speed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mipshop-4140bis-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mipshop-4140bis-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-07-14053822.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop --NextPart-- From cacuman@antide.com Mon Jul 14 19:44:52 2008 Return-Path: X-Original-To: ietfarch-mipshop-archive@core3.amsl.com Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AF0228C0DC; Mon, 14 Jul 2008 19:44:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.955 X-Spam-Level: **** X-Spam-Status: No, score=4.955 tagged_above=-999 required=5 tests=[BAYES_80=2, FB_QUALITY_REPLICA=10.357, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357, GB_ROLEX=5, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX=1.666, SARE_SPEC_ROLEX_HIQLT=1.666, SARE_SPEC_ROLEX_NOV5A=1.062, SARE_SPEC_ROLEX_NOV5F=0.666, SARE_SPEC_ROLEX_REP=1.666, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, 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 oQ0rbhoWwlgs; Mon, 14 Jul 2008 19:44:52 -0700 (PDT) Received: from 190-95-86-124.bk21-dsl.surnet.cl (190-95-86-124.bk21-dsl.surnet.cl [190.95.86.124]) by core3.amsl.com (Postfix) with SMTP id 7110128C152; Mon, 14 Jul 2008 19:44:37 -0700 (PDT) X-Originating-IP: 121.208.20.156 by smtp.190.95.86.124; Mon, 14 Jul 2008 22:45:11 -0500 Message-ID: From: "Parker Dyer" Reply-To: "Parker Dyer" To: mip6@ietf.org Subject: Qualitative Breitling watches at Prestige Replicas Date: Mon, 14 Jul 2008 22:45:11 -0500 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit Have you always wanted a Rolex, but don't want to pay high prices for a brand name watch? Then you need to visit Prestige Replicas, a website dedicated exclusively to high quality replicas, with the most extensive inventory on the web and a proven track record of satisfied customers. http://www.wellsoe.com/ Prestige Replicas offers hundreds of Rolex replica watches starting just above $100, and during this spring season, their already low prices have been slashed by 15 percent if you buy two or more watches! No matter which model Rolex you choose, their 15% discount applies to them all! But don't let this limited time offer go by... spring is ending and it's time to impress your friends with a realistic, high quality Rolex replica watch, that will look and perform just like the real deal! http://www.wellsoe.com/ From mipshop-bounces@ietf.org Thu Jul 17 15:30:52 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83F1328C103; Thu, 17 Jul 2008 15:30:52 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CB3D3A692C; Thu, 17 Jul 2008 15:30:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.537 X-Spam-Level: X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 b86u9CjprsUg; Thu, 17 Jul 2008 15:30:50 -0700 (PDT) Received: from mx0.starentnetworks.com (mx0.starentnetworks.com [12.38.223.203]) by core3.amsl.com (Postfix) with ESMTP id 9FC503A6831; Thu, 17 Jul 2008 15:30:49 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mx0.starentnetworks.com (Postfix) with ESMTP id 691C6C801E; Thu, 17 Jul 2008 18:31:15 -0400 (EDT) Received: from mx0.starentnetworks.com ([127.0.0.1]) by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11242-04; Thu, 17 Jul 2008 18:31:11 -0400 (EDT) Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com [10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP; Thu, 17 Jul 2008 18:31:11 -0400 (EDT) Received: from exchtewks3.starentnetworks.com ([10.2.4.31]) by exchtewks1.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 17 Jul 2008 18:31:11 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 17 Jul 2008 18:33:07 -0400 Message-ID: <4D35478224365146822AE9E3AD4A2666033E173C@exchtewks3.starentnetworks.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Network-based Mobility Extensions (NetExt) Bar BOF Thread-Index: AcjoXRWPSJApqEV3R5GKw/F7RXnI0g== From: "Koodli, Rajeev" To: , , X-OriginalArrivalTime: 17 Jul 2008 22:31:11.0751 (UTC) FILETIME=[D0C8B970:01C8E85C] X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com Cc: Jari Arkko , Basavaraj Patil Subject: [Mipshop] Network-based Mobility Extensions (NetExt) Bar BOF X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1839664031==" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org This is a multi-part message in MIME format. --===============1839664031== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E85C.D0982C75" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8E85C.D0982C75 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello folks, =20 As many of you involved in Network-based Mobility (PMIPv6) are aware, there appears to be more interest in Network-based Mobility than the NETLMM charter can reasonably handle. So, Raj and myself are pondering whether there is enough interest among folks to work on a few more items. To this extent, we are planning to hold a Bar BOF at Dublin. At this stage, this is only to investigate=20 =20 a) if there are a few topics which we should be working on (relevant to network-based mobility), and=20 b) whether there is enough interest behind them to work on.=20 =20 This is tentatively set for Thursday (7/31), at 1300. We will confirm the time and venue later.=20 =20 If you are interested in presenting what you think should be worked on, here is a template we would like you to use. 1. Title (of course)=20 2. Brief description of the topic, no more than few sentences=20 3. Why this topic needs to be worked on now (feel free to include any need(s) from external organizations/industry but please be as clear as possible). Again, no more than couple of sentences=20 You should spend at most a slide for this. As an example, 1. Session Control for PMIPv6=20 2. PMIPv6 provides a network-based mobility management without the explicit involvement of a Mobile Node. It does not provide control mechanisms to offer features such as QoS and Policy at the granularity of an individual mobility session. This work extends the PMIPv6 protocol to provide such support.=20 3. Deployments (such as in 3GPP) where PMIPv6 is a candidate protocol need Session Control. For instance, the GPRS Tunneling Protocol (GTP) already provides the necessary signaling support for QoS.=20 Please send us your requests. The ML to be used for this discussion is: netext@mail.mobileip.jp If you have any questions or comments, please post to the Netext ML or send email to basavaraj.patil@nokia.com and rkoodli@starentnetworks.com =20 We hope to have a good and focused discussion which could lead to a short list of topics for further consideration. =20 Thank you and see you in Dublin. =20 Regards, =20 -Rajeev and Raj =20 ------_=_NextPart_001_01C8E85C.D0982C75 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello folks,
 
As many of you involved in Network-based Mobility (PMIPv6) are aware, = there appears to be more interest in Network-based Mobility than the NETLMM = charter can reasonably handle. So, Raj and myself are pondering whether there is = enough interest among folks to work on a few more items. To this extent, we are planning to hold a Bar BOF at Dublin. At this stage, this is only to investigate

 

a) if there are a few topics which we should be = working on (relevant to network-based mobility), and

b) whether there is enough interest behind them to = work on.

 

This is tentatively set for Thursday (7/31), at 1300. = We will confirm the time and venue later.
 
If you are interested in presenting what you think should be worked on, = here is a template we would like you to use.

  1. Title (of course) =
  2. Brief description of the topic, no more = than few sentences
  3. Why this topic needs to be worked on now = (feel free to include any need(s) from external organizations/industry = but please be as clear as possible). Again, no more than couple of = sentences =

You should spend at most a slide for this. As an = example,

  1. Session Control for = PMIPv6 =
  2. PMIPv6 provides a network-based mobility management without the explicit involvement of a Mobile Node. It = does not provide control mechanisms to offer features such as QoS and Policy = at the granularity of an individual mobility session. This work extends = the PMIPv6 protocol to provide such support. =
  3. Deployments (such as in 3GPP) where = PMIPv6 is a candidate protocol need Session Control. For instance, the GPRS = Tunneling Protocol (GTP) already provides the necessary signaling support for = QoS.

Please send us your requests.

The ML to be used for this discussion is: netext@mail.mobileip.jp<= /span>

If you have any questions or comments, please post to the Netext ML or send email to = basavaraj.patil@nokia.com and rkoodli@starentnetworks.com
=  
We hope to have a good and focused discussion which could lead to a = short list of topics for further consideration.
 
Thank you and see you in Dublin.
 
Regards,
 
-Rajeev and Raj

 

------_=_NextPart_001_01C8E85C.D0982C75-- --===============1839664031== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop --===============1839664031==-- From mipshop-bounces@ietf.org Thu Jul 17 18:14:52 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC9E828C115; Thu, 17 Jul 2008 18:14:52 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94A693A69F2 for ; Thu, 17 Jul 2008 18:14:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 8MH5ne5B0lHI for ; Thu, 17 Jul 2008 18:14:51 -0700 (PDT) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by core3.amsl.com (Postfix) with ESMTP id 682E63A69E7 for ; Thu, 17 Jul 2008 18:14:51 -0700 (PDT) Received: by rv-out-0506.google.com with SMTP id b25so119729rvf.49 for ; Thu, 17 Jul 2008 18:15:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:in-reply-to:subject :references:message-id:content-type:content-transfer-encoding :mime-version:date:cc:x-mailer; bh=pSbZc/7zCyXXtCkJMW16t8bxxJ2YfnwaX6eZDsBL9Fo=; b=FLs/S+J7Juyzi0JvK9pskor2rlPpbwVyab5Iv93jrQ94S/y4xbEVWRDmCW6ryx+zkg zMLtoZv0ll4kR6qG/ilUWPkWM2B4FGl2lSNbl4qhdDfm0zDT8Vj3Lv4gfAm6cLE7YQPM TguWn5+FhMtR/tBB/dcVdcsgXmHR2xiiR/3fw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:in-reply-to:subject:references:message-id:content-type :content-transfer-encoding:mime-version:date:cc:x-mailer; b=rA37iFnL78ff3zVLDK2UASngzzW62CtSvI5kBBwzRH0IAS+oKAARsU+12rEg/yBmh/ bJ6nY37C+CvrXfyzDCH+OYUCM3tFl9WbRIvHqeF5kgXymoU4sTQaNeFrI5cboLertYcM X5SKwTM8viCY3n9fOnDfeZB+YhU7V4GjhnLVE= Received: by 10.141.29.8 with SMTP id g8mr1572130rvj.62.1216343722782; Thu, 17 Jul 2008 18:15:22 -0700 (PDT) Received: from ?172.17.105.59? ( [61.200.198.242]) by mx.google.com with ESMTPS id g22sm952049rvb.7.2008.07.17.18.15.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Jul 2008 18:15:22 -0700 (PDT) From: Ryuji Wakikawa To: "Koodli, Rajeev" In-Reply-To: <4D35478224365146822AE9E3AD4A2666033E173C@exchtewks3.starentnetworks.com> References: <4D35478224365146822AE9E3AD4A2666033E173C@exchtewks3.starentnetworks.com> Message-Id: <2BED9A33-0B58-48EC-84A8-621CBE2B806A@gmail.com> Mime-Version: 1.0 (Apple Message framework v926) Date: Fri, 18 Jul 2008 10:15:18 +0900 X-Mailer: Apple Mail (2.926) Cc: Jari Arkko , mipshop@ietf.org, Basavaraj Patil , "netlmm@ietf.org Mailing List" , mext Subject: Re: [Mipshop] Network-based Mobility Extensions (NetExt) Bar BOF X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed"; DelSp="yes" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org WW91IGNhbiBzdWJzY3JpYmUgdG8gdGhlIGxpc3QgZnJvbSB0aGUgZm9sbG93aW5nIFVSTC4KCmh0 dHA6Ly93d3cubW9iaWxlaXAuanAvbWFpbG1hbi9saXN0aW5mby9uZXRleHQKCnJlZ2FyZHMsCnJ5 dWppCgpPbiAyMDA4LzA3LzE4LCBhdCA3OjMzLCBLb29kbGksIFJhamVldiB3cm90ZToKCj4gSGVs bG8gZm9sa3MsCj4KPiBBcyBtYW55IG9mIHlvdSBpbnZvbHZlZCBpbiBOZXR3b3JrLWJhc2VkIE1v YmlsaXR5IChQTUlQdjYpIGFyZSAgCj4gYXdhcmUsIHRoZXJlIGFwcGVhcnMgdG8gYmUgbW9yZSBp bnRlcmVzdCBpbiBOZXR3b3JrLWJhc2VkIE1vYmlsaXR5ICAKPiB0aGFuIHRoZSBORVRMTU0gY2hh cnRlciBjYW4gcmVhc29uYWJseSBoYW5kbGUuIFNvLCBSYWogYW5kIG15c2VsZiAgCj4gYXJlIHBv bmRlcmluZyB3aGV0aGVyIHRoZXJlIGlzIGVub3VnaCBpbnRlcmVzdCBhbW9uZyBmb2xrcyB0byB3 b3JrICAKPiBvbiBhIGZldyBtb3JlIGl0ZW1zLiBUbyB0aGlzIGV4dGVudCwgd2UgYXJlIHBsYW5u aW5nIHRvIGhvbGQgYSBCYXIgIAo+IEJPRiBhdCBEdWJsaW4uIEF0IHRoaXMgc3RhZ2UsIHRoaXMg aXMgb25seSB0byBpbnZlc3RpZ2F0ZQo+Cj4gYSkgaWYgdGhlcmUgYXJlIGEgZmV3IHRvcGljcyB3 aGljaCB3ZSBzaG91bGQgYmUgd29ya2luZyBvbiAocmVsZXZhbnQgIAo+IHRvIG5ldHdvcmstYmFz ZWQgbW9iaWxpdHkpLCBhbmQKPiBiKSB3aGV0aGVyIHRoZXJlIGlzIGVub3VnaCBpbnRlcmVzdCBi ZWhpbmQgdGhlbSB0byB3b3JrIG9uLgo+Cj4gVGhpcyBpcyB0ZW50YXRpdmVseSBzZXQgZm9yIFRo dXJzZGF5ICg3LzMxKSwgYXQgMTMwMC4gV2Ugd2lsbCAgCj4gY29uZmlybSB0aGUgdGltZSBhbmQg dmVudWUgbGF0ZXIuCj4KPiBJZiB5b3UgYXJlIGludGVyZXN0ZWQgaW4gcHJlc2VudGluZyB3aGF0 IHlvdSB0aGluayBzaG91bGQgYmUgd29ya2VkICAKPiBvbiwgaGVyZSBpcyBhIHRlbXBsYXRlIHdl IHdvdWxkIGxpa2UgeW91IHRvIHVzZS4KPiAJ4oCiIFRpdGxlIChvZiBjb3Vyc2UpCj4gCeKAoiBC cmllZiBkZXNjcmlwdGlvbiBvZiB0aGUgdG9waWMsIG5vIG1vcmUgdGhhbiBmZXcgc2VudGVuY2Vz Cj4gCeKAoiBXaHkgdGhpcyB0b3BpYyBuZWVkcyB0byBiZSB3b3JrZWQgb24gbm93IChmZWVsIGZy ZWUgdG8gaW5jbHVkZSAgCj4gYW55IG5lZWQocykgZnJvbSBleHRlcm5hbCBvcmdhbml6YXRpb25z L2luZHVzdHJ5IGJ1dCBwbGVhc2UgYmUgYXMgIAo+IGNsZWFyIGFzIHBvc3NpYmxlKS4gQWdhaW4s IG5vIG1vcmUgdGhhbiBjb3VwbGUgb2Ygc2VudGVuY2VzCj4gWW91IHNob3VsZCBzcGVuZCBhdCBt b3N0IGEgc2xpZGUgZm9yIHRoaXMuIEFzIGFuIGV4YW1wbGUsCj4gCeKAoiBTZXNzaW9uIENvbnRy b2wgZm9yIFBNSVB2Ngo+IAnigKIgUE1JUHY2IHByb3ZpZGVzIGEgbmV0d29yay1iYXNlZCBtb2Jp bGl0eSBtYW5hZ2VtZW50IHdpdGhvdXQgdGhlICAKPiBleHBsaWNpdCBpbnZvbHZlbWVudCBvZiBh IE1vYmlsZSBOb2RlLiBJdCBkb2VzIG5vdCBwcm92aWRlIGNvbnRyb2wgIAo+IG1lY2hhbmlzbXMg dG8gb2ZmZXIgZmVhdHVyZXMgc3VjaCBhcyBRb1MgYW5kIFBvbGljeSBhdCB0aGUgIAo+IGdyYW51 bGFyaXR5IG9mIGFuIGluZGl2aWR1YWwgbW9iaWxpdHkgc2Vzc2lvbi4gVGhpcyB3b3JrIGV4dGVu ZHMgdGhlICAKPiBQTUlQdjYgcHJvdG9jb2wgdG8gcHJvdmlkZSBzdWNoIHN1cHBvcnQuCj4gCeKA oiBEZXBsb3ltZW50cyAoc3VjaCBhcyBpbiAzR1BQKSB3aGVyZSBQTUlQdjYgaXMgYSBjYW5kaWRh dGUgIAo+IHByb3RvY29sIG5lZWQgU2Vzc2lvbiBDb250cm9sLiBGb3IgaW5zdGFuY2UsIHRoZSBH UFJTIFR1bm5lbGluZyAgCj4gUHJvdG9jb2wgKEdUUCkgYWxyZWFkeSBwcm92aWRlcyB0aGUgbmVj ZXNzYXJ5IHNpZ25hbGluZyBzdXBwb3J0IGZvciAgCj4gUW9TLgo+IFBsZWFzZSBzZW5kIHVzIHlv dXIgcmVxdWVzdHMuCj4gVGhlIE1MIHRvIGJlIHVzZWQgZm9yIHRoaXMgZGlzY3Vzc2lvbiBpczog bmV0ZXh0QG1haWwubW9iaWxlaXAuanAKPiBJZiB5b3UgaGF2ZSBhbnkgcXVlc3Rpb25zIG9yIGNv bW1lbnRzLCBwbGVhc2UgcG9zdCB0byB0aGUgTmV0ZXh0IE1MICAKPiBvciBzZW5kIGVtYWlsIHRv IGJhc2F2YXJhai5wYXRpbEBub2tpYS5jb20gYW5kIHJrb29kbGlAc3RhcmVudG5ldHdvcmtzLmNv bQo+Cj4gV2UgaG9wZSB0byBoYXZlIGEgZ29vZCBhbmQgZm9jdXNlZCBkaXNjdXNzaW9uIHdoaWNo IGNvdWxkIGxlYWQgdG8gYSAgCj4gc2hvcnQgbGlzdCBvZiB0b3BpY3MgZm9yIGZ1cnRoZXIgY29u c2lkZXJhdGlvbi4KPgo+IFRoYW5rIHlvdSBhbmQgc2VlIHlvdSBpbiBEdWJsaW4uCj4KPiBSZWdh cmRzLAo+Cj4gLVJhamVldiBhbmQgUmFqCj4KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwo+IE1pcHNob3AgbWFpbGluZyBsaXN0Cj4gTWlwc2hvcEBpZXRm Lm9yZwo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWlwc2hvcAoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlwc2hvcCBtYWls aW5nIGxpc3QKTWlwc2hvcEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp c3RpbmZvL21pcHNob3AK From mipshop-bounces@ietf.org Thu Jul 17 20:23:19 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 910823A6941; Thu, 17 Jul 2008 20:23:19 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C45BE3A6941 for ; Thu, 17 Jul 2008 20:23:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.59 X-Spam-Level: X-Spam-Status: No, score=-1.59 tagged_above=-999 required=5 tests=[AWL=-0.388, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396] 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 Ip8AsZg5OguM for ; Thu, 17 Jul 2008 20:23:16 -0700 (PDT) Received: from dakia3.marvell.com (dakia3.marvell.com [65.219.4.28]) by core3.amsl.com (Postfix) with ESMTP id 7605B3A67B7 for ; Thu, 17 Jul 2008 20:23:16 -0700 (PDT) X-ASG-Debug-ID: 1216351428-44f6032a0000-Psfj6Z X-Barracuda-URL: http://dakia3.marvell.com:80/cgi-bin/mark.cgi Received: from maili.marvell.com (localhost [127.0.0.1]) by dakia3.marvell.com (Spam Firewall) with ESMTP id CA1FD569285 for ; Thu, 17 Jul 2008 20:23:48 -0700 (PDT) Received: from maili.marvell.com (maili.marvell.com [10.68.76.51]) by dakia3.marvell.com with ESMTP id IbGMmKZsIwjaYY7v for ; Thu, 17 Jul 2008 20:23:48 -0700 (PDT) Received: from sc-exch03.marvell.com (sc-exch03.marvell.com [10.68.76.198]) by maili.marvell.com (Postfix) with ESMTP id C8DAD5B73A for ; Thu, 17 Jul 2008 20:23:48 -0700 (PDT) X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: MIPSHOP Agenda Date: Thu, 17 Jul 2008 20:23:39 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MIPSHOP Agenda Thread-Index: Acjohavaw2BRMj8JQuyh4DR2w3TuVQ== From: "Stefano Faccin" To: X-Barracuda-Connect: maili.marvell.com[10.68.76.51] X-Barracuda-Start-Time: 1216351428 X-Barracuda-Virus-Scanned: by Marvell Mail Gateway at marvell.com Subject: [Mipshop] MIPSHOP Agenda X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2009296380==" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org This is a multi-part message in MIME format. --===============2009296380== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E885.B10F2B88" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8E885.B10F2B88 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ----------------------- IETF72 MIPSHOP WG meeting agenda ----------------------- Tuesday, July 29, 1520-1720 0. Agenda review, Blue sheets and volunteers for=20 notes and Jabber 5 Mins 1. WG status and I-Ds update 10 Mins 2. Discussion on MSTP scenarios draft-ietf-mipshop-mstp-solution-05 20 Mins 3. Use of DHCP for discovering MoS service in the visited link =20 draft-ietf-mipshop-mos-dhcp-options-03 20 Mins =20 4. PMIPv6 handover optimizations 50 Mins 5. AAA-based Handover key for FMIPv6 10 Mins 6. Next Steps 5 Mins Chairs =20 ------_=_NextPart_001_01C8E885.B10F2B88 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A=
-----------------------
=0A=

IETF72

=0A=

MIPSHOP WG meeting agenda

=0A=

-----------------------

=0A=

Tuesday, July 29, 1520-1720

=0A= 
0. Agenda review, Blue sheets and volunteers for =
=0A=

   notes and = Jabber          &= nbsp;           &n= bsp;         &n= bsp;5 Mins

=0A= 
1. WG status and I-Ds =
update          &=
nbsp;           &n=
bsp; 10 Mins
=0A= 
2. Discussion on MSTP scenarios
=0A=

   = draft-ietf-mipshop-mstp-solution-05    &= nbsp;         20 = Mins

=0A= 
3. Use of DHCP for discovering MoS service in =
the
=0A=

   visited link =         

=0A=

   = draft-ietf-mipshop-mos-dhcp-options-03  &nb= sp;        20 Mins   =

=0A= 
4. PMIPv6 handover =
optimizations         =
           =
50 Mins
=0A=
=0A=

5. AAA-based Handover key = for FMIPv6     =            10 = Mins

6. Next Steps               =
                         5 Mins
=0A=

   = Chairs     

------_=_NextPart_001_01C8E885.B10F2B88-- --===============2009296380== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop --===============2009296380==-- From mipshop-bounces@ietf.org Fri Jul 18 01:13:42 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 736A73A6812; Fri, 18 Jul 2008 01:13:42 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52F403A67FD for ; Fri, 18 Jul 2008 01:13:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] 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 sdu2bJRkQhLq for ; Fri, 18 Jul 2008 01:13:40 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) by core3.amsl.com (Postfix) with ESMTP id 940853A6812 for ; Fri, 18 Jul 2008 01:13:40 -0700 (PDT) Received: from IBM52A5038A94F ([88.245.252.54]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1KJl6P12ot-0005w7; Fri, 18 Jul 2008 04:14:12 -0400 From: "Alper Yegin" To: "'Stefano Faccin'" , Date: Fri, 18 Jul 2008 11:14:04 +0300 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: Acjohavaw2BRMj8JQuyh4DR2w3TuVQAKGQUg In-Reply-To: Message-Id: <0MKp8S-1KJl6P12ot-0005w7@mrelay.perfora.net> X-Provags-ID: V01U2FsdGVkX1+goZZIMGijHU3DzI8FVt+Ma+GuOIEFj2T3e20 BXRb7qhyf6ErQ1S6H5VzYWiJm3IY4InWPNmBV4rjtnbN1GrPW9 nllAa8kCqJdarLTMoDAcA== Subject: Re: [Mipshop] MIPSHOP Agenda X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2138854331==" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org This is a multi-part message in MIME format. --===============2138854331== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BB_01C8E8C7.6691DB70" This is a multi-part message in MIME format. ------=_NextPart_000_00BB_01C8E8C7.6691DB70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Stefano, What is the plan for this item? In the past we touched on this at least 2-3 times and never drove it to conclusion. 5. AAA-based Handover key for FMIPv6 10 Mins ------=_NextPart_000_00BB_01C8E8C7.6691DB70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi = Stefano,

 

What is the plan for this item? In = the past we touched on this at least 2-3 times and never drove it to = conclusion.

 

5. AAA-based Handover key for FMIPv6                10 = Mins

 

------=_NextPart_000_00BB_01C8E8C7.6691DB70-- --===============2138854331== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop --===============2138854331==-- From mipshop-bounces@ietf.org Fri Jul 18 07:57:51 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E1F53A6AD1; Fri, 18 Jul 2008 07:57:51 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B71D028C0F1 for ; Fri, 18 Jul 2008 07:57:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599] 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 EGUpkjov-apH for ; Fri, 18 Jul 2008 07:57:50 -0700 (PDT) Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id C6BC63A6ACD for ; Fri, 18 Jul 2008 07:57:49 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 18 Jul 2008 10:58:15 -0400 Message-ID: In-Reply-To: <0MKp8S-1KJl6P12ot-0005w7@mrelay.perfora.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mipshop] MIPSHOP Agenda Thread-Index: Acjohavaw2BRMj8JQuyh4DR2w3TuVQAKGQUgAA4nDSA= References: <0MKp8S-1KJl6P12ot-0005w7@mrelay.perfora.net> From: "Vijay Devarapalli" To: "Alper Yegin" , "Stefano Faccin" , Subject: Re: [Mipshop] MIPSHOP Agenda X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org This time we have a plan. :) Vijay ________________________________ From: mipshop-bounces@ietf.org [mailto:mipshop-bounces@ietf.org] On Behalf Of Alper Yegin Sent: Friday, July 18, 2008 1:14 AM To: 'Stefano Faccin'; mipshop@ietf.org Subject: Re: [Mipshop] MIPSHOP Agenda Hi Stefano, What is the plan for this item? In the past we touched on this at least 2-3 times and never drove it to conclusion. 5. AAA-based Handover key for FMIPv6 10 Mins _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Fri Jul 18 13:52:45 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A875328C28C; Fri, 18 Jul 2008 13:52:45 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CEAAC3A6B7A for ; Fri, 18 Jul 2008 13:52:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.082 X-Spam-Level: X-Spam-Status: No, score=-2.082 tagged_above=-999 required=5 tests=[AWL=0.517, BAYES_00=-2.599] 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 xjrxDZHOHKhz for ; Fri, 18 Jul 2008 13:52:43 -0700 (PDT) Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id 4549D3A6B78 for ; Fri, 18 Jul 2008 13:52:43 -0700 (PDT) Received: from [127.0.0.1] ([75.26.137.116]) by outbound.mse15.exchange.ms with Microsoft SMTPSVC(6.0.3790.3959); Fri, 18 Jul 2008 16:53:16 -0400 Message-ID: <488102B0.5040603@wichorus.com> Date: Fri, 18 Jul 2008 13:53:04 -0700 From: Vijay Devarapalli User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: mipshop@ietf.org, hesham@elevatemobile.com, jari.arkko@piuha.net X-OriginalArrivalTime: 18 Jul 2008 20:53:16.0511 (UTC) FILETIME=[4D47FEF0:01C8E918] Subject: [Mipshop] IESG review related changes to 4140bis X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org All, The following changes are to be made to draft-ietf-mipshop-4140bis. These changes are required to address IESG comments. Let us know if anyone has comments on the changes being proposed. The plan is to have one more revision before approving the document. Please change this in Section 2: OLD: Mobile IPv6 [RFC3775] allows nodes to move within the Internet topology while maintaining reachability and on-going connections between mobile and correspondent nodes. To do this a mobile node sends Binding Updates (BUs) to its Home Agent (HA) and all Correspondent Nodes (CNs) it communicates with, every time it moves. Authenticating binding updates requires approximately 1.5 round-trip times between the mobile node and each correspondent node (for the entire return routability procedure in a best case scenario, i.e., no packet loss). In addition, one round-trip time is needed to update the Home Agent; this can be done simultaneously while updating correspondent nodes. The re-use of the home cookie (i.e., eliminating HOTI/HOT) will not reduce the number of round trip times needed to update correspondent nodes. These round trip delays will disrupt active connections every time a handoff to a new AR is performed. Eliminating this additional delay element from the time- critical handover period will significantly improve the performance of Mobile IPv6. NEW: Mobile IPv6 [RFC3775] allows nodes to move within the Internet topology while maintaining reachability and on-going connections between mobile and correspondent nodes. To do this a mobile node sends a Binding Update (BUs) to its Home Agent (HA) every time it moves. The mobile node may send data packets via its Home Agent immediately after sending the Binding Update, but the Home Agent will not be able to route traffic back to the mobile node before it receives the Binding Update. This incurs at least half a round-trip delay before packets are again forwarded to the right place. There is an additional delay for sending data packets if the mobile node chooses to wait for a Binding Acknowledgement (BA). The round-trip times can be relatively long, if the mobile node and its home agent are in different parts of the world. Additional delay is also incurred if the mobile node employs route optimization. Authenticating binding updates requires approximately 1.5 round-trip times between the mobile node and each correspondent node (for the entire return routability procedure in a best case scenario, i.e., no packet loss). This can be done in parallel with sending Binding Updates to the Home agent, and there are further optimizations that reduce the required 1.5 round-trips [RFC4449, RFC4651, RFC4866]. Nevertheless, the signaling exchanges required to update your location will always cause some disruption to active connections. Some packets will be lost. Together with link layer and IP layer connection setup delays there may be effects to upper layer protocols. Reducing these delays during the time-critical handover period will improve the performance of Mobile IPv6. Please change this in Section 5: OLD: Dist A 4-bit unsigned integer identifying the Distance Between MAP and the receiver of the advertisement. The Distance MUST be set to 1 if the MAP is on the same link as the mobile node. This field need not be interpreted as the number of hops between MAP and the mobile node. The only requirement is that the meaning of the Distance field is consistently interpreted within one Domain. A larger value in the dist field indicates that the MAP is further away from the mobile node. That is, a MAP option with a dist field of 5 indicates that this MAP is further away from the mobile node than another option with a dist field value of 3. A Distance value of Zero MUST NOT be used. If the MAP option is advertised within an overlap between two different MAP domains then this field MUST be consistently interpreted within the overlap area. Pref The preference of a MAP. A 4-bit unsigned integer. A decimal value of 15 indicates the highest availability. NEW: Dist A 4-bit unsigned integer identifying the Distance Between MAP and the receiver of the advertisement, measure in the number of hops and starting from 1 if the MAP is on the same link as the mobile node. A Distance value of Zero MUST NOT be used. Pref The preference field, used as an indicator of operator preference. A 4-bit unsigned integer. A decimal value of 15 indicates the highest preference. When comparing two potential MAPs, the mobile node SHOULD inspect this field as a tie-breaker for MAPs that have equal Dist values. Please change HOTI, COTI, HOT and COT to HoTI, CoTI, HoT and CoT, which are the correct way to write these (from RFC 3775). s/Figure 1: Figure 1:/Figure 1:/ Delete the word "significantly" in Section 2. Also, please change in Section 11: OLD: Confidentiality may be needed for payload traffic, but is not required for binding updates to the MAP. NEW: Confidentiality may be needed for payload traffic, such as when the mobile node is unwilling to reveal any traffic to the access network beyond what is needed for the mobile node to attach to the network and communicate with a MAP. Confidentiality is not required for binding updates to the MAP. And remove appendix A entirely. Update references as follows: - Remove reference RFC 4068 - Remove reference RFC 4302 - Remove reference RFC 4303 - Remove reference RFC 4862 - Remove reference RFC 2827 - Remove reference RFC 3971 In Section 3.1, change: OLD: through the MAP option NEW: through Neighbour Discovery [RFC 4861] and the MAP option Please change this in 3.1: OLD: The Home address used in the BU is the RCoA. NEW: The Home address used in the BU is the RCoA, which the mobile node acquires via RFC 4877 [RFC4877] Section 9 mechanisms when it first contacts a given MAP. Please change in Section 5: OLD: Global Address One of the MAP's global addresses. The 64-bit prefix extracted from this address MUST be configured in the MAP to be used for RCoA construction by the mobile node. Although not explicitly included in the MAP option, the prefix length of the MAP's Global IP address MUST be 64. This prefix is the one used by the mobile node to form an RCoA, by appending a 64-bit identifier to the prefix. Thus, it necessitates a static prefix length for the MAP's subnet. NEW: Global Address One of the MAP's global addresses. Please change in Section 6: OLD: This RCoA is formed in a stateless manner by combining the mobile node's interface identifier and the subnet prefix received in the MAP option. NEW: This RCoA is formed by the MAP when it is contacted by the mobile node for the first time. Please change in Section 6.1: OLD: The RCoA is formed in a stateless manner. After forming the RCoA based on the prefix received in the MAP option, the mobile node sends a local BU to the MAP with the A and M flags set. NEW: After employing RFC 4877 [RFC4877] to acquire an RCoA, the mobile node sends a local BU to the MAP with the A and M flags set. Please change in Section 6.1: OLD: The MAP (acting as a HA) will then perform DAD (when a new binding is being created) for the mobile node's RCoA on its link and return a Binding Acknowledgement to the MN. NEW: The MAP (acting as a HA) will then return a Binding Acknowledgement to the MN. Please change in Section 6.2: OLD: The MAP acts as a HA for the RCoA. NEW: The MAP employs [RFC4877] Section 9 procedures for the allocation of RCoA, and subsequently acts as a HA for the RCoA. Please change in Section 12.1: OLD: The IPsec PAD entries described in [RFC4877] for allocating dynamic home addresses SHOULD be used by the MAP to allocate the RCoA for mobile nodes. NEW: The IPsec PAD entries and configuration payloads described in [RFC4877] for allocating dynamic home addresses SHOULD be used by the MAP to allocate the RCoA for mobile nodes. Vijay _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Sun Jul 20 08:45:01 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 083843A6A42; Sun, 20 Jul 2008 08:45:01 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 738513A6AFC; Tue, 15 Jul 2008 09:37:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 v-vBK9H+ogMF; Tue, 15 Jul 2008 09:37:03 -0700 (PDT) Received: from smtp.cs.ucdavis.edu (smtp.cs.ucdavis.edu [169.237.4.8]) by core3.amsl.com (Postfix) with ESMTP id 63A733A6848; Tue, 15 Jul 2008 09:37:03 -0700 (PDT) X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-ASG-Debug-ID: 1216139850-288f00010000-1pz6IU X-Barracuda-URL: http://169.237.4.8:8000/cgi-bin/mark.cgi Received: from imapssl.cs.ucdavis.edu (imapssl.cs.ucdavis.edu [169.237.6.5]) by smtp.cs.ucdavis.edu (Spam Firewall) with ESMTP id 9E73852A3C; Tue, 15 Jul 2008 09:37:30 -0700 (PDT) Received: from imapssl.cs.ucdavis.edu (imapssl.cs.ucdavis.edu [169.237.6.5]) by smtp.cs.ucdavis.edu with ESMTP id KAwzfakwEzuQiDy0; Tue, 15 Jul 2008 09:37:30 -0700 (PDT) Received: from localhost (liu@localhost) by imapssl.cs.ucdavis.edu (8.13.8/8.13.5/Submit) with ESMTP id m6FGb2Q4027642; Tue, 15 Jul 2008 09:37:02 -0700 (PDT) X-Authentication-Warning: imapssl.cs.ucdavis.edu: liu owned process doing -bs Date: Tue, 15 Jul 2008 09:37:02 -0700 (PDT) From: Xin Liu To: amlist@takilab.k.dendai.ac.jp, announce@tcos.org, cfp@mmlab.snu.ac.kr, comm-theory@ieee.org, comswtc@comsoc.org, end2end-interest@postel.org, ga@terena.nl, ifip-tc6@informatik.rwth-aachen.de, info-autonomic@autonomic-communication.org, info-confs@comsoc.org, itc@comsoc.org, iwqos@comsoc.org, manet@ietf.org, MOBICOM@acm.org, mip6@ietf.org, mipshop@ietf.org, multicomm@comsoc.org, orctrans@loria.fr, podc-related@acm.org, reres@laas.fr, SIGCOMM-MEMBERS@acm.org, SIGMOB@acm.org, SIGSIM@acm.org, SENSORNET@LISTSERV.ACM.ORG X-ASG-Orig-Subj: MC2R Special Issue on Cognitive Radio Technologies and Systems Message-ID: MIME-Version: 1.0 X-Barracuda-Connect: imapssl.cs.ucdavis.edu[169.237.6.5] X-Barracuda-Start-Time: 1216139850 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at cs.ucdavis.edu X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=INFO_TLD X-Barracuda-Spam-Report: Code version 3.1, rules version 3.1.56134 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 INFO_TLD URI: Contains an URL in the INFO top-level domain X-Mailman-Approved-At: Sun, 20 Jul 2008 08:45:00 -0700 Cc: "Cordeiro, Carlos" , stds-802-wpan@ieee.org Subject: [Mipshop] MC2R Special Issue on Cognitive Radio Technologies and Systems X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org ACM Mobile Computing and Communications Review (MC2R) Special Issue on Cognitive Radio Technologies and Systems Motivated by the need for efficient spectrum utilization, facilitated by regulatory policy movements, and enabled by advances in RF technologies, there has been significant research towards developing cognitive radio (CR) networks technologies. The purpose of this special issue is to facilitate the exchange of cutting-edge research in cognitive radio network technologies, including the exploration of networking and communication protocols and algorithms needed to facilitate the interconnection of CR platforms. Since CR research is taking place across multiple communities, ranging from academic to government to industry, from physical layer to networking to hardware researchers, we intend for this special issue to serve as a forum for collaboration that will accelerate the design, deployment, and eventual success of CR platforms. This special issue invites submission of manuscripts on analytical modeling, protocol/algorithm design, and/or experimental studies. Areas of interest include but are not limited to: * Spectrum Sensing and Spectrum Management * Cognitive Radio Test-Beds and Hardware Prototypes * Enabling CR technologies such as Software Defined Radios, IEEE P1900, and IEEE 802.22 * Protocol and Algorithms for the PHY, MAC, and Network layer * Accreditation, Trust, & Security Mechanisms for Cognitive Radio Networks * QoS Support and Cross-Layer Protocol Design * Cooperation and Game-Theoretical Protocols for Cognitive Radios * Practical Experience and Systems Implementations * Applications of Cognitive Radios Original, unpublished contributions and invited articles will be considered for the issue. The papers should be formatted according to MC2R guidelines (http://www.sigmobile.org/pubs/mc2r/guidelines/author.html). Authors should submit their complete manuscript in PDF format via EDAS (http://edas.info/) under the Cognitive Radio Track of MC2R according to the following timetable: Manuscript Submission Due: Nov. 1, 2008, 5pm PDT Acceptance Notification: Feb. 1, 2009 Camera-Ready Paper Due: March 1, 2009 Projected publication date: Apr., 2009 Guest Editors: Carlos Cordeiro Communication Technology Lab Intel Corporation Carlos.Cordeiro@intel.com Xin Liu Computer Science Department University of California, Davis Liu@cs.ucdavis.com _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Sun Jul 20 08:45:08 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B60B3A6A59; Sun, 20 Jul 2008 08:45:05 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B9913A6A00 for ; Sun, 20 Jul 2008 03:28:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.026 X-Spam-Level: X-Spam-Status: No, score=-3.026 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, DNS_FROM_DOB=0.732, GB_I_INVITATION=-2, RCVD_IN_DOB=1.103] 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 qa5noJ2DZ-JJ for ; Sun, 20 Jul 2008 03:28:12 -0700 (PDT) Received: from rygel.liquidweb.com (rygel.liquidweb.com [72.52.197.4]) by core3.amsl.com (Postfix) with ESMTP id AC8EB3A6969 for ; Sun, 20 Jul 2008 03:28:12 -0700 (PDT) Received: from [69.141.170.21] (port=34467 helo=Oana2) by rygel.liquidweb.com with esmtpa (Exim 4.69) (envelope-from ) id 1KKW9n-00060S-Kg for mipshop@ietf.org; Sun, 20 Jul 2008 06:28:47 -0400 Date: Sun, 20 Jul 2008 06:28:46 -0400 (EDT) From: IARIA Invitation To: mipshop@ietf.org Message-ID: <8404242.47910.1216549726187.JavaMail.Onitza@Oana2> MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rygel.liquidweb.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - iariaannounce.org X-Mailman-Approved-At: Sun, 20 Jul 2008 08:45:00 -0700 Subject: [Mipshop] First CfP: InfoSys 2009 [ICNS, ICAS, INTENSIVE], Valencia/Spain, April 21-25, 2009 X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org INVITATION 2009 Please consider to contribute and encourage your team members and fellow scientists to contribute to the following federated events. Thanks for forwarding the information on this Call for Submissions to those potentially interested to submit. ===== Call for Submissions ======= InfoSys 2009, April 21-25, 2009 - Valencia/Spain see: http://www.iaria.org/conferences2009/InfoSys09.html InfoSys 2009 is a federated event focusing on advances topics concerning the networking, services, autonomic and autonomous systems, and intensive services and applications. InfoSys 2009 continues the tradition of well-established conferences, ICNS and ICAS, and adds new trends on intensive services and applications (INTENSIVE). Submission deadline: November 1st, 2008 - ICNS 2009, The Fifth International Conference on Networking and Services http://www.iaria.org/conferences2009/ICNS09.html - ICAS 2009, The Fifth International Conference on Autonomic and Autonomous Systems http://www.iaria.org/conferences2009/ICAS09.html - INTENSIVE 2009, The First International Conference on Intensive Applications and Services http://www.iaria.org/conferences2009/INTENSIVE09.html Submissions must be electronically done using the "Submit a Paper" link on the entry page of each conference. For details on the each conference's topics, see the individual Call for Papers for each conference. Unpublished high quality contributions in terms of Regular papers and Forum posters are welcome. Workshop proposals and Panel proposals on challenging topics are encouraged. Extended versions of selected papers will be published in IARIA on-line Journals ( http://www.iariajournals.org) and in Special issues of different journals mentioned on the entry page of each conference. Submissions will be peer-reviewed, published by IEEE Computer Society Press, posted in IEEE Digital Library, and indexed via all the IEEE indexing agreements. -------------------------------- IARIA Publicity Board ------------------------------- To stop receiving notices about InfoSys, please reply with "DROP InfoSys mipshop@ietf.org" in the subject field. To receive notices about specific topics only, please reply with "TOPIC CHANGE mipshop@ietf.org" in the subject field, and the specific topics in the email body. To stop receiving any notice, please reply with "UNSUBSCRIBE mipshop@ietf.org" in the subject field. _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Tue Jul 22 04:23:34 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B96E83A6929; Tue, 22 Jul 2008 04:23:34 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A1AE3A6945 for ; Tue, 22 Jul 2008 04:23:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.573 X-Spam-Level: X-Spam-Status: No, score=-3.573 tagged_above=-999 required=5 tests=[AWL=-0.974, BAYES_00=-2.599] 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 okLoXjqKN5WZ for ; Tue, 22 Jul 2008 04:23:33 -0700 (PDT) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id E88B13A6929 for ; Tue, 22 Jul 2008 04:23:32 -0700 (PDT) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id m6MBO81k032731 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jul 2008 13:24:08 +0200 Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id m6MBO8E2024619; Tue, 22 Jul 2008 13:24:08 +0200 Received: from demuexc024.nsn-intra.net ([10.159.32.11]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 22 Jul 2008 13:24:08 +0200 Received: from FIESEXC007.nsn-intra.net ([10.159.0.15]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 22 Jul 2008 13:24:06 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 22 Jul 2008 14:24:06 +0300 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] Rechartering: draft-stupar-dime-mos-options Thread-Index: Acjmqc6lW04Uc3zPSkKq7QzSTKg8JQFQazhg From: "Tschofenig, Hannes (NSN - FI/Espoo)" To: X-OriginalArrivalTime: 22 Jul 2008 11:24:06.0657 (UTC) FILETIME=[7408CF10:01C8EBED] X-TM-AS-Product-Ver: SMEX-7.0.0.1584-5.5.1027-16046.006 X-TM-AS-Result: No--6.936600-8.000000-31 Cc: ext David Frascone Subject: [Mipshop] FW: [Dime] Rechartering: draft-stupar-dime-mos-options X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi all, In the DIME working group we are currently having a re-chartering discussion and one document that has been submitted to DIME relates to functionality that was developed in your working group. We would therefore like to understand whether * there is an interest from the MIPSHOP WG to have DIME to work on this subject * there are folks in MIPSHOP willing todo reviews and thereby help to finish the work quickly. We need your feedback! Ciao Hannes & Dave DIME Chairs >-----Original Message----- >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On >Behalf Of ext Hannes Tschofenig >Sent: 15 July, 2008 21:30 >To: dime@ietf.org >Cc: Patrick Stupar; subir@research.telcordia.com >Subject: [Dime] Rechartering: draft-stupar-dime-mos-options > >Document: http://tools.ietf.org/id/draft-stupar-dime-mos-options-00.txt > >* Who is able to be editor of the document? > >* Who is interested to help the editor with the work on the >draft by co-authoring it? > >* Who is able to provide reviews? > >* Who is unable to actively help with a specific document but >supports the work? > >* Are there concerns regarding this document? > >* Is there a dependency with another IETF working group or >with another SDO? > >* How long will it take to finish this document? >(A rough guess based on the current status of the document. By >"finished" I mean "ready for WGLC".) > >_______________________________________________ >DiME mailing list >DiME@ietf.org >https://www.ietf.org/mailman/listinfo/dime > _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Wed Jul 23 08:04:58 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7F423A6A2C; Wed, 23 Jul 2008 08:04:58 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4737E28C17E for ; Wed, 23 Jul 2008 08:04:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 XyuiK9ly-NAS for ; Wed, 23 Jul 2008 08:04:51 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 27D743A689B for ; Wed, 23 Jul 2008 08:04:47 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.31,239,1215388800"; d="scan'208";a="15175920" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 23 Jul 2008 15:05:29 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m6NF5SFT014667; Wed, 23 Jul 2008 17:05:28 +0200 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m6NF5SZI005875; Wed, 23 Jul 2008 15:05:28 GMT Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jul 2008 17:05:28 +0200 X-Mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 23 Jul 2008 17:07:16 +0200 Message-ID: In-Reply-To: <487832BA.4080209@piuha.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mipshop] AD review of draft-ietf-mipshop-mstp-solution Thread-Index: Acjj16oQWlENRTh8QDGYz7FLkwiu2AI/Eulg References: <483170AA.2000403@piuha.net><4831AC1B.7020501@piuha.net> <4860FF97.6070902@piuha.net> <487832BA.4080209@piuha.net> From: "Telemaco Melia (tmelia)" To: "Jari Arkko" X-OriginalArrivalTime: 23 Jul 2008 15:05:28.0883 (UTC) FILETIME=[8B456830:01C8ECD5] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2653; t=1216825528; x=1217689528; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=tmelia@cisco.com; z=From:=20=22Telemaco=20Melia=20(tmelia)=22=20 |Subject:=20RE=3A=20[Mipshop]=20AD=20review=20of=20draft-ie tf-mipshop-mstp-solution |Sender:=20; bh=XPX/8kmyenNFZd0lluEZ3yaLQY2dvgmOnvHxmkSfX1Q=; b=leytjfeu+0dL99XzuLca+/Alw79VE8ROE0d4rOTbXvcDibZdw/X+lUyY9a syYv1i0HqsEJ/6AxjjXzGVEZwyXV2i3QCfK2HRDKwrJdgxkF4Tf4Z12ZtywS mIZs9AuNeR; Authentication-Results: ams-dkim-2; header.From=tmelia@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: gorry@erg.abdn.ac.uk, draft-ietf-mipshop-mstp-solution@tools.ietf.org, Mipshop Subject: Re: [Mipshop] AD review of draft-ietf-mipshop-mstp-solution X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi Jari, Please see comments below. [SNIP] In Gorry's review he pointed out that the UDP usage guidelines document recommends an exponential back-off mechanism. The mstp draft deviates from this, and I'm not sure its appropriate to do so. Note that the guidelines had only a recommendation, not a requirement. But its not clear that you actually want to avoid an exponential back-off. Its easy to think of situations (such as the base station going down) where there would be a significant amount of retransmission traffic from a large number of hosts. [TELE] We had an email exchange with Gorry and he agreed on the current text at the end of section 6.3 (See Gorry's email from 6/8/2008) Section 5.3 talks about "step c" which I no longer can find. [TELE] Fixed. I would like to see Appendix A removed; for the reasons discussed earlier the relay approach has problems. I don't think we want to publish a spec that hints that the relay approach should be done. [TELE] I see in the Mishop agenda an item to discuss such issue in the WG. I guess we can quickly update the ID accordingly afterwards. I did not notice changes relating to the following: > MIH Transport Options > > > The document does not talk about how servers know the capabilities of > clients that send event/command services to. Is this a part of the > IEEE definitions, and you subscribe to a particular event stream? In > any case, the document should talk about this and point to the > relevant other specifications where needed. > [TELE] Beginning of section 6 mentions the fact that capabilities discovery and subscription procedures are specified in IEEE802.21 > >> > In the case where DHCP is used for node discovery and authentication >> > of the source and content of DHCP messages is required, network >> > administrators SHOULD use DHCP authentication option described in >> > [RFC3118 ], where available or rely upon link layer security. This >> > will also protect the DHCP server against denial of service attacks >> > to. [RFC3118 ] provides mechanisms for both entity authentication and >> > message authentication. >> > > I think the overall recommendation is good, but practically no one is > going to deploy RFC 3118. With this in mind, I would like to see the > above paragraph explain in more detail the security implications of > relying on link layer security. > [TELE] Text will be shown during the presentation. Telemaco Jari _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Wed Jul 23 12:13:30 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D51033A6887; Wed, 23 Jul 2008 12:13:30 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFC803A6A50 for ; Wed, 23 Jul 2008 12:13:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599] 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 T9IKus5fdTQc for ; Wed, 23 Jul 2008 12:13:28 -0700 (PDT) Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id BA3793A6887 for ; Wed, 23 Jul 2008 12:13:28 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 23 Jul 2008 15:14:05 -0400 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mipshop] FW: [Dime] Rechartering: draft-stupar-dime-mos-options Thread-Index: Acjmqc6lW04Uc3zPSkKq7QzSTKg8JQFQazhgAEMBViA= References: From: "Vijay Devarapalli" To: "Tschofenig, Hannes (NSN - FI/Espoo)" Cc: mipshop@ietf.org, ext David Frascone Subject: Re: [Mipshop] FW: [Dime] Rechartering: draft-stupar-dime-mos-options X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi Hannes, draft-ietf-mipshop-mstp-solution-05, which is with the IESG currently, has a dependency on this document. The extensions specified in draft-stupar-dime-mos-options are required for delivering the MIH server information to the NAS/access router. However, in the AD review, a question was raised on whether we need this scenario at all. We are currently discussing this. We should be able to decide on this in the next couple of weeks. I will get back to you. If we decide to keep this scenario in draft-ietf-mipshop-mstp-solution-05, then I would like to see draft-stupar-dime-mos-options adopted as a DIME WG document. Vijay > -----Original Message----- > From: mipshop-bounces@ietf.org > [mailto:mipshop-bounces@ietf.org] On Behalf Of Tschofenig, > Hannes (NSN - FI/Espoo) > Sent: Tuesday, July 22, 2008 4:24 AM > To: mipshop@ietf.org > Cc: ext David Frascone > Subject: [Mipshop] FW: [Dime] Rechartering: > draft-stupar-dime-mos-options > > Hi all, > > In the DIME working group we are currently having a re-chartering > discussion and one document that has been submitted to DIME relates to > functionality that was developed in your working group. > > We would therefore like to understand whether > * there is an interest from the MIPSHOP WG to have DIME to > work on this > subject > * there are folks in MIPSHOP willing todo reviews and thereby help to > finish the work quickly. > > We need your feedback! > > Ciao > Hannes & Dave > DIME Chairs > > >-----Original Message----- > >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On > >Behalf Of ext Hannes Tschofenig > >Sent: 15 July, 2008 21:30 > >To: dime@ietf.org > >Cc: Patrick Stupar; subir@research.telcordia.com > >Subject: [Dime] Rechartering: draft-stupar-dime-mos-options > > > >Document: > http://tools.ietf.org/id/draft-stupar-dime-mos-options-00.txt > > > >* Who is able to be editor of the document? > > > >* Who is interested to help the editor with the work on the > >draft by co-authoring it? > > > >* Who is able to provide reviews? > > > >* Who is unable to actively help with a specific document but > >supports the work? > > > >* Are there concerns regarding this document? > > > >* Is there a dependency with another IETF working group or > >with another SDO? > > > >* How long will it take to finish this document? > >(A rough guess based on the current status of the document. By > >"finished" I mean "ready for WGLC".) > > > >_______________________________________________ > >DiME mailing list > >DiME@ietf.org > >https://www.ietf.org/mailman/listinfo/dime > > > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www.ietf.org/mailman/listinfo/mipshop > _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Wed Jul 23 12:25:22 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43E6C3A6B0B; Wed, 23 Jul 2008 12:25:22 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC5673A6B08 for ; Wed, 23 Jul 2008 12:25:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.512 X-Spam-Level: X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599] 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 oK5vmoukmIKI for ; Wed, 23 Jul 2008 12:25:20 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 416C03A6B09 for ; Wed, 23 Jul 2008 12:25:20 -0700 (PDT) Received: (qmail invoked by alias); 23 Jul 2008 19:19:22 -0000 Received: from a91-154-105-144.elisa-laajakaista.fi (EHLO [192.168.255.3]) [91.154.105.144] by mail.gmx.net (mp011) with SMTP; 23 Jul 2008 21:19:22 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX19BwJYt4TxBBDN6Nj6GdRFlExELUSunIdkm1ajAD0 MZlBBCZvCA8YvK Message-ID: <48878439.1070701@gmx.net> Date: Wed, 23 Jul 2008 22:19:21 +0300 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Vijay Devarapalli References: In-Reply-To: X-Y-GMX-Trusted: 0 X-FuHaFi: 0.54 Cc: dime@ietf.org, mipshop@ietf.org, ext David Frascone Subject: Re: [Mipshop] FW: [Dime] Rechartering: draft-stupar-dime-mos-options X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Your feedback has helped. Thanks a lot! Vijay Devarapalli wrote: > Hi Hannes, > > draft-ietf-mipshop-mstp-solution-05, which is with the IESG currently, > has a dependency on this document. The extensions specified in > draft-stupar-dime-mos-options are required for delivering the MIH server > information to the NAS/access router. > > However, in the AD review, a question was raised on whether we need this > scenario at all. We are currently discussing this. We should be able to > decide on this in the next couple of weeks. I will get back to you. > > If we decide to keep this scenario in > draft-ietf-mipshop-mstp-solution-05, then I would like to see > draft-stupar-dime-mos-options adopted as a DIME WG document. > > Vijay > > >> -----Original Message----- >> From: mipshop-bounces@ietf.org >> [mailto:mipshop-bounces@ietf.org] On Behalf Of Tschofenig, >> Hannes (NSN - FI/Espoo) >> Sent: Tuesday, July 22, 2008 4:24 AM >> To: mipshop@ietf.org >> Cc: ext David Frascone >> Subject: [Mipshop] FW: [Dime] Rechartering: >> draft-stupar-dime-mos-options >> >> Hi all, >> >> In the DIME working group we are currently having a re-chartering >> discussion and one document that has been submitted to DIME relates to >> functionality that was developed in your working group. >> >> We would therefore like to understand whether >> * there is an interest from the MIPSHOP WG to have DIME to >> work on this >> subject >> * there are folks in MIPSHOP willing todo reviews and thereby help to >> finish the work quickly. >> >> We need your feedback! >> >> Ciao >> Hannes & Dave >> DIME Chairs >> >> >>> -----Original Message----- >>> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On >>> Behalf Of ext Hannes Tschofenig >>> Sent: 15 July, 2008 21:30 >>> To: dime@ietf.org >>> Cc: Patrick Stupar; subir@research.telcordia.com >>> Subject: [Dime] Rechartering: draft-stupar-dime-mos-options >>> >>> Document: >>> >> http://tools.ietf.org/id/draft-stupar-dime-mos-options-00.txt >> >>> * Who is able to be editor of the document? >>> >>> * Who is interested to help the editor with the work on the >>> draft by co-authoring it? >>> >>> * Who is able to provide reviews? >>> >>> * Who is unable to actively help with a specific document but >>> supports the work? >>> >>> * Are there concerns regarding this document? >>> >>> * Is there a dependency with another IETF working group or >>> with another SDO? >>> >>> * How long will it take to finish this document? >>> (A rough guess based on the current status of the document. By >>> "finished" I mean "ready for WGLC".) >>> >>> _______________________________________________ >>> DiME mailing list >>> DiME@ietf.org >>> https://www.ietf.org/mailman/listinfo/dime >>> >>> >> _______________________________________________ >> Mipshop mailing list >> Mipshop@ietf.org >> https://www.ietf.org/mailman/listinfo/mipshop >> >> > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www.ietf.org/mailman/listinfo/mipshop > _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Wed Jul 23 12:57:39 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 547B23A685E; Wed, 23 Jul 2008 12:57:39 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3419C3A685E; Wed, 23 Jul 2008 12:57:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 zQkHs2vAHBXX; Wed, 23 Jul 2008 12:57:37 -0700 (PDT) Received: from flower.research.telcordia.com (flower.research.telcordia.com [128.96.41.5]) by core3.amsl.com (Postfix) with ESMTP id 136C23A67D6; Wed, 23 Jul 2008 12:57:36 -0700 (PDT) Received: from mailee.research.telcordia.com (mailee.research.telcordia.com [192.4.16.29]) by flower.research.telcordia.com (8.14.2/8.14.2) with ESMTP id m6NJwMJe019029; Wed, 23 Jul 2008 15:58:22 -0400 (EDT) Received: from [127.0.0.1] (vpntnlB42 [128.96.59.42]) by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id PAA22323; Wed, 23 Jul 2008 15:56:15 -0400 (EDT) Message-ID: <48878D52.5070008@research.telcordia.com> Date: Wed, 23 Jul 2008 15:58:10 -0400 From: Subir Das User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Hannes Tschofenig References: <48878439.1070701@gmx.net> In-Reply-To: <48878439.1070701@gmx.net> Cc: ext David Frascone , dime@ietf.org, mipshop@ietf.org Subject: Re: [Mipshop] FW: [Dime] Rechartering: draft-stupar-dime-mos-options X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hannes, I will echo with Vijay. We have sufficient interests in working on this document and would request you to add this item in DIME charter once we decide to keep the scenario. regards, -Subir Hannes Tschofenig wrote: > Your feedback has helped. > Thanks a lot! > > Vijay Devarapalli wrote: >> Hi Hannes, >> >> draft-ietf-mipshop-mstp-solution-05, which is with the IESG currently, >> has a dependency on this document. The extensions specified in >> draft-stupar-dime-mos-options are required for delivering the MIH server >> information to the NAS/access router. >> >> However, in the AD review, a question was raised on whether we need this >> scenario at all. We are currently discussing this. We should be able to >> decide on this in the next couple of weeks. I will get back to you. >> >> If we decide to keep this scenario in >> draft-ietf-mipshop-mstp-solution-05, then I would like to see >> draft-stupar-dime-mos-options adopted as a DIME WG document. >> >> Vijay >> >> >>> -----Original Message----- >>> From: mipshop-bounces@ietf.org [mailto:mipshop-bounces@ietf.org] On >>> Behalf Of Tschofenig, Hannes (NSN - FI/Espoo) >>> Sent: Tuesday, July 22, 2008 4:24 AM >>> To: mipshop@ietf.org >>> Cc: ext David Frascone >>> Subject: [Mipshop] FW: [Dime] Rechartering: >>> draft-stupar-dime-mos-options >>> >>> Hi all, >>> In the DIME working group we are currently having a re-chartering >>> discussion and one document that has been submitted to DIME relates to >>> functionality that was developed in your working group. >>> We would therefore like to understand whether * there is an interest >>> from the MIPSHOP WG to have DIME to work on this >>> subject >>> * there are folks in MIPSHOP willing todo reviews and thereby help to >>> finish the work quickly. >>> We need your feedback! >>> >>> Ciao >>> Hannes & Dave >>> DIME Chairs >>> >>>> -----Original Message----- >>>> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On >>>> Behalf Of ext Hannes Tschofenig >>>> Sent: 15 July, 2008 21:30 >>>> To: dime@ietf.org >>>> Cc: Patrick Stupar; subir@research.telcordia.com >>>> Subject: [Dime] Rechartering: draft-stupar-dime-mos-options >>>> >>>> Document: >>> http://tools.ietf.org/id/draft-stupar-dime-mos-options-00.txt >>> >>>> * Who is able to be editor of the document? >>>> >>>> * Who is interested to help the editor with the work on the draft >>>> by co-authoring it? >>>> >>>> * Who is able to provide reviews? >>>> >>>> * Who is unable to actively help with a specific document but >>>> supports the work? >>>> >>>> * Are there concerns regarding this document? >>>> >>>> * Is there a dependency with another IETF working group or with >>>> another SDO? >>>> >>>> * How long will it take to finish this document? >>>> (A rough guess based on the current status of the document. By >>>> "finished" I mean "ready for WGLC".) >>>> >>>> _______________________________________________ >>>> DiME mailing list >>>> DiME@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dime >>>> >>>> >>> _______________________________________________ >>> Mipshop mailing list >>> Mipshop@ietf.org >>> https://www.ietf.org/mailman/listinfo/mipshop >>> >>> >> _______________________________________________ >> Mipshop mailing list >> Mipshop@ietf.org >> https://www.ietf.org/mailman/listinfo/mipshop >> > > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www.ietf.org/mailman/listinfo/mipshop _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Thu Jul 24 11:53:05 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3164F3A6359; Thu, 24 Jul 2008 11:53:05 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 164603A6359 for ; Thu, 24 Jul 2008 11:53:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599] 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 8kx+h6LX+7St for ; Thu, 24 Jul 2008 11:53:02 -0700 (PDT) Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id 7176D3A6358 for ; Thu, 24 Jul 2008 11:53:01 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 24 Jul 2008 14:53:42 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Thomas Narten's review of draft-ietf-mipshop-mos-dns-discovery Thread-Index: AcjtvdPlILCGWmo0Q2iRgZpN6/jjSwAAKJvA From: "Vijay Devarapalli" To: Subject: [Mipshop] Thomas Narten's review of draft-ietf-mipshop-mos-dns-discovery X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org FYI -----Original Message----- From: Thomas Narten [mailto:narten@us.ibm.com] Sent: Thursday, July 24, 2008 11:48 AM I have some general concerns, but I'm not sure how strong there are. First, my understanding is that the overall algorithm is: 1) MN somehow knows (e.g., via DHCP) which domain it wants mobility info from. Let's call it target.example.com. 2) The MN does a NAPTR query for target.example.com. 2a) A NAPTR RR response contains a service name of the form +X, where is a defined mobility service such as "IS", "ES", or "CS", and "X" is "T" for TCP, "U" for UDP, "S" for SCTP, etc. (For example "CS+T") 2b) MN decides which service/transport it wants to use from the list of returned NAPTR RRs 2c) From the chosen NAPTR RR, MN uses the target DNS name as the DNS name where the service is located. (e.g., the target might be _ES._tcp.target.example.com) 2d) MN generates SRV query using name in 2c). 2e) Contact server(s) based on SRV response. The above is all straightforward, and I don't see any issue right off. But what I don't quite like is that there are a bunch of exceptions and the above steps can be skipped. This may lead to operational problems. E.g., if the MN only supports (say UDP) for accessing a mobility service, it (per the spec) simply skips the NAPTR query and goes to 2d), using target.example.com as the domain name and then prepending (say) _ES._udp to it. There is no requirement that the NAPTR RR in 2c) above has to be target.example.com. It could be foo.bar.com. So now there is the chance for inconistencies in behavior, with different NMs getting different behavior (i.e, those that query for NAPTR and those that skip the step). Also, there is a rule: It is not necessary for the domain suffixes in the NAPTR replacement field to match the domain of the original query (i.e., example.com above). However, a domain MUST maintain SRV records for the domain of the original query, even if the NAPTR record is in a different domain, as the access network the MN is attached to might implement policies which restrict access to certain domains. As an example, even though the SRV record for TCP is _IS._tcp.school.edu, there MUST also be an SRV record at _IS._tcp.example.com. Here, it is clear that the target DNS name and configured DNS name do not have to be same. Yet, it is stated that some MN's will ignore such names, so both names have to be maintained. This to me seems like a recipe for confusion and operational problems. Is this sort of inconcistency really needed to be supported by the protocol? Maybe the better way to describe this algorithm is to make the case for when NAPTR should be used at all. Why is it needed if the NM can chose to skip that step? more detaild comments: It is not necessary for the domain suffixes in the NAPTR replacement field to match the domain of the original query (i.e., example.com above). However, a domain MUST maintain SRV records for the domain of the original query, even if the NAPTR record is in a different domain, as the access network the MN is attached to might implement policies which restrict access to certain domains. As an example, even though the SRV record for TCP is _IS._tcp.school.edu, there MUST also be an SRV record at _IS._tcp.example.com. Don't understand/follow this. It may just need rewording. I.e., "which domain" is being talked about? Note, that the regexp field in the NAPTR example above is empty. This document discourages the use of this field as its usage can be complex and error prone; and the discovery of the MIH services do not require the flexibility provided by this field over a static target present in the TARGET field. Sounds weak. Is it allowed? MUST clients support this field? If no SRV records are found, the client SHOULD use TCP to contact a server which hosts an IS service and UDP to contact a server which hosts an ES and/or CS service. Which server name, exactly? If the MN knows the IP address of the server, it may contact the server using the default port number for that service. Default port numbers for IS, ES and CS services are requested from IANA in [ID.ietf-mipshop-mstp-solution]. Huh? Why say this? This seems unnecessary, undesirable. The transition to Section 2.3 seems out of place. Shouldn't this just be a continuation of the previous section for the case where a NAPTR RR exists? If so, why not include it there? Perhaps the separate subsection should be for when there is no NAPTR RR. That is presumably a standalone action. If the TARGET was not a numeric IP address, then the MN performs an A or AAAA record lookup of the domain name. The result will be a Don't just say "or" here. Correct process is to do a lookup "for A and/or AAAA records as appropriate" or some such. New entries to the registry MAY be added by IANA on a "First Come First Served" basis. Seems like a least some superficial review be done. Not much review, but more than FCFS, IMO. For starters, one doesn't expect many of these to ever be assigned, since they are for transport protocols. Thomas _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Sat Jul 26 01:00:03 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A7343A69E2; Sat, 26 Jul 2008 01:00:03 -0700 (PDT) X-Original-To: mipshop@ietf.org Delivered-To: mipshop@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 99A923A6937; Sat, 26 Jul 2008 01:00:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080726080001.99A923A6937@core3.amsl.com> Date: Sat, 26 Jul 2008 01:00:01 -0700 (PDT) Cc: mipshop@ietf.org Subject: [Mipshop] I-D ACTION:draft-ietf-mipshop-4140bis-05.txt X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF. Title : Hierarchical Mobile IPv6 Mobility Management Author(s) : H. Soliman, C. Castelluccia, K. El Malki, L. Bellier Filename : draft-ietf-mipshop-4140bis-05.txt Pages : 32 Date : 2008-7-26 This document introduces extensions to Mobile IPv6 and IPv6 Neighbour Discovery to allow for local mobility handling. Hierarchical mobility management for Mobile IPv6 is designed to reduce the amount of signalling between the Mobile Node, its Correspondent Nodes, and its Home Agent. The Mobility Anchor Point (MAP) described in this document can also be used to improve the performance of Mobile IPv6 in terms of handover speed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mipshop-4140bis-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mipshop-4140bis-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-7-26005848.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop --NextPart-- From mipshop-bounces@ietf.org Sat Jul 26 04:15:53 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 913AB3A6930; Sat, 26 Jul 2008 04:15:53 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C99D13A68EB for ; Sat, 26 Jul 2008 04:15:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.592 X-Spam-Level: X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599] 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 zWYvT2AaKVH2 for ; Sat, 26 Jul 2008 04:15:52 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id DA7783A69A2 for ; Sat, 26 Jul 2008 04:15:51 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 5C028198725; Sat, 26 Jul 2008 14:15:55 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id D065A1986E3; Sat, 26 Jul 2008 14:15:54 +0300 (EEST) Message-ID: <488B076B.1090302@piuha.net> Date: Sat, 26 Jul 2008 12:15:55 +0100 From: Jari Arkko User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Mipshop References: <20080726080001.8CEB73A696A@core3.amsl.com> In-Reply-To: <20080726080001.8CEB73A696A@core3.amsl.com> X-Virus-Scanned: ClamAV using ClamSMTP Cc: draft-ietf-mipshop-4140bis@tools.ietf.org, pasi.eronen@nokia.com, David Ward Subject: Re: [Mipshop] New Version Notification - draft-ietf-mipshop-4140bis-05.txt X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi all, Hesham has submitted a new version of the document to address IESG review comments. I asked the secretariat to bypass the before-the-meeting I-D submission block for this draft as I believe the sooner we get to see this version the better. I have now reviewed the new version and I think it is correct with the exception of two minor details at the end of this e-mail. However, I would like the WG to take a look at the new version because it has changed quite a bit, and make sure they like the end result. The main changes have resulted from Pasi's and David's Discusses, which dealt with the details of how RCoA allocation and security work, and the way that Dist and Pref are used. If there is no opposition, I will approve the draft by the end of the IETF week. Please review. Here are the files: http://tools.ietf.org/rfcdiff?url2=http://tools.ietf.org/id/draft-ietf-mipshop-4140bis-05.txt http://tools.ietf.org/html/draft-ietf-mipshop-4140bis-05 Jari In Section 3.1, change: OLD: through Neighbour Discovery [RFC 4861]the MAP option NEW: through Neighbour Discovery [RFC 4861] and the MAP option Please change this in 3.1: OLD: The Home address used in the BU is the RCoA. NEW: The Home address used in the BU is the RCoA, which the mobile node acquires via RFC 4877 [RFC4877] Section 9 mechanisms when it first contacts a given MAP. _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Mon Jul 28 08:27:32 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0C1228C198; Mon, 28 Jul 2008 08:27:32 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 929F13A6892 for ; Mon, 28 Jul 2008 08:27:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 F0hcTkd0IxXv for ; Mon, 28 Jul 2008 08:27:26 -0700 (PDT) Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id 1813C28C198 for ; Mon, 28 Jul 2008 08:27:25 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 28 Jul 2008 11:27:28 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Change of Meeting rooms for MIPSHOP Thread-Index: AcjwxiVoJG6VQUrQSI+dcflktX7FugAAA5yw From: "Vijay Devarapalli" To: Subject: [Mipshop] Change of Meeting rooms for MIPSHOP X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hello, Note that the MIPSHOP meeting has been moved to Ballroom 1. Vijay ---------- Forwarded message ---------- From: IETF Secretariat Date: Mon, Jul 28, 2008 at 8:24 AM Subject: MIPSHOP - Requested session has been scheduled for IETF 72 To: dvijay@gmail.com Cc: smfaccin@marvell.com, jari.arkko@piuha.net, townsley@cisco.com, session-request@ietf.org Dear Vijay Devarapalli, The sessions that you have requested have been scheduled. Below is the scheduled session information followed by the information of sessions that you have requested. MIPSHOP Session 1 (2 hours) Tuesday, Afternoon Session II 1520-1720 Room Name: Ballroom 1 ---------------------------------------------- Special Note: Room Change Requested Information: --------------------------------------------------------- Working Group Name: mipshop Area Name: Internet Area Session Requester: Vijay Devarapalli Number of Sessions: 1 Length of Session(s): 2 hours Number of Attendees: 100 Conflicts to Avoid: First Priority: mext Second Priority: netlmm Third Priority: mip4 Special Requests: Please avoid conflicts with mobopts, hokey also. --------------------------------------------------------- _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Tue Jul 29 03:23:18 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 052DE28C289; Tue, 29 Jul 2008 03:23:18 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4D2728C28D for ; Tue, 29 Jul 2008 03:23:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 U0wPz7oxgS1v for ; Tue, 29 Jul 2008 03:23:15 -0700 (PDT) Received: from flower.research.telcordia.com (flower.research.telcordia.com [128.96.41.5]) by core3.amsl.com (Postfix) with ESMTP id 4342928C282 for ; Tue, 29 Jul 2008 03:23:15 -0700 (PDT) Received: from [128.96.58.178] (vpntnlA178.research.telcordia.com [128.96.58.178]) by flower.research.telcordia.com (8.14.2/8.14.2) with ESMTP id m6TANgK5028202 for ; Tue, 29 Jul 2008 06:23:43 -0400 (EDT) Message-ID: <488EEF9D.6080003@research.telcordia.com> Date: Tue, 29 Jul 2008 06:23:25 -0400 From: Ashutosh Dutta User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: "'Mipshop'" Subject: [Mipshop] Extended Deadline for IMSAA-2008: August 15, 2008 X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Dear Colleagues, Here is a relevant CFP. Please help distribute to your colleagues. Regards Ashutosh *********************************************************************************************************************** We apologize for multiple receipts Deadline Extension: 2nd International IEEE Conference on Internet Multimedia Services Architecture and Application (IMSAA-2008), Dec 10th-12th, 2008, Bangalore, India. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- CALL FOR PAPERS The 2nd International IEEE Conference on Internet Multimedia Services Architecture and Application (IMSAA-2008) Bangalore, India December, 10-12, 2008 http://www.iiitb.ac.in/imsaa2008/index.html EXTENDED DEADLINE: AUGUST 15, 2008. Co-Sponsored By IEEE Bangalore Section and International Institute of Information Technology-Bangalore (iiit-b) ************** Extended Paper Submission Deadline: August 15th, 2008 ************** The IMS (IP Multimedia Subsystem) is a timely attempt at defining a uniform services control layer for next-generation telecommunication networks, and is attracting increased interest from telecom providers and carriers across the world. In particular, IMS is core to the vision of converged services, and aims to provide multimedia services across a variety of access networks, such as 3G, cable and 802.11 hotspots, with appropriate charging and access control. IMS is also expected as the vehicle for offering a variety of exciting new services, such as IPTV, multimedia conferencing and multiplayer gaming, as well as a means to enable seamless communication across enterprise and provider networks through integration with other technologies (such as Web 2.0). Link for Paper Uploading at EDAS: http://edas.info/newPaper.php?c=6534& Accepted papers will be included in the IEEE Xplore database. ----------------------------------------------------------------------------------- Topics of interest include but are NOT LIMITED to the following: * Architectures and Runtimes for IMS Elements 1. Application Server Architectures and Converged Containers 2. Architectures for Rich and Scalable Presence 3. Service Mediation and Billing Platforms * IMS Core Services 1. Real-time Service Support: (voice, video calls, multimedia conferencing, multiplayer gaming) 2. Content/Context-aware services: (Location, presence, social and community context) 3. Service Creation Environments (IMS, SCIM, Service Delivery Platforms, Integrated environments) * Device, Subscriber, Service and Network Management 1. Provisioning and management (Handsets, PDA's, Set top Box, Home Gateway) 2. Subscriber and User Profile Management 3. Managing the quality of the user experience (QoE, QoS) 4. End to end Performance Measurement and modeling (signaling, media,services) * Operator Network Planning 1. Routing and Load Balancing 2. Redundancy and Fault Tolerance 3. MVNO Operations and Support * Novel IMS-based Applications 1. Gaming and mixed-reality 2. Environmental and Sensor Monitoring 3. Multimedia Content Sharing 4. Converged IN 5. Converged Home Network 6. IPTV over IMS * Security, Identity Management and Privacy 1. Privacy and Security in Composite Applications 2. Privacy in LBS 3. IMS authentication * IMS mobility 1. Heterogeneous Mobility 2. Roaming issues 3. Mobility performance * IMS and Alternative Technologies 1. P2P and IMS (VoIP, Instant Messaging, Gaming) 2. Integrating IMS and Web2.0 services (Mashups, Rich Internet Applications) 3. User-generated Services and Content 4. IMS simplification 5. Non-IMS support * Case Studies and Status of IMS deployment 1. Interoperability Testing 2. IMS Support in Vendor Products 3. Benchmarking IMS Services and Applications * Testbeds and Software Tools 1. Service Test and Validation Platforms 2. Open Source Initiatives 3. Benchmarking IMS Services and Applications * IMS Clients and Devices 1. IMS-aware consumer devices 2. Media/communication platforms ----------------------------------------------------------------------------------- PAPER SUBMISSION GUIDELINES Paper submission format: Papers must be submitted in IEEE format (.pdf file). The EDAS website for paper registration and complete paper submission is as follows: http://edas.info/newPaper.php?c=6534& Formating instruction: Papers for review: Double-column, 10pt IEEE format and no longer than 6 pages (including all figures and references). Camera ready paper: It will be in double-column, IEEE format,10 pt font, and no longer than 6 pages (including all figures and references). Instruction for paper formatting can be found at: http://www.iiitb.ac.in/imsaa2008/documents/A4.doc (Word) http://www.iiitb.ac.in/imsaa2008/documents/IEEEtran.tar.gz (Latex) Demo proposals should be sent via e-mail directly to Demo chairs: Sachin Deshpande (sdeshpande@sharplabs.com) and Tilak Kesavapillai (tilak@motorola.com), before 15th August, 2008 . A Demo proposal should include the following information: a) Demo title b) Full contact information of the company putting up the demo c) Description of the Demo including objectives, content, and format of the demo d) IMS Ring support detail (if any). Details of the IMS ring hosted at IIITB can be given accordingly. e) UPS, WLAN, furniture requirements d) List of potential demonstrators f) A short brief on company information More information at:- http://www.iiitb.ac.in/imsaa2008/demo.html Tutorial proposals should be submitted to Tutorial chair:- Jyotsna Bapat (jbapat@iiitb.ac.in). * Papers must not substantially overlap with papers which are already published or are simultaneously submitted to other journals or conference with proceedings. ----------------------------------------------------------------------------------- IMPORTANT DATES Extended deadline: 15th August, 2008 (EST, USA) Last date for tutorial proposal submission: 15th August, 2008 (EST, USA) Last date for demo proposal submission: 15th August 2008 (EST, USA) Paper review notification: 25th Sept., 2008 Paper camera ready: 5th Oct. 2008 ----------------------------------------------------------------------------------- CONFERENCE COMMITTEE * Steering Committee Chairs 1. Sowmyanarayanan Sadagopan (IIIT-Bangalore, India) 2. Sammy Sana (Country President, Motorola, India) 3. Madhukar V Pitke (Founder Director C-DoT, India) * General Chairs 1. Vinod Vasudeban (Reliance Communication, India) 2. Sandeep Mehta (Tata Communications, India) 3. K.Ramakrishna (IEEE Bangalore Section Chair) * Organizing Committee 1. Subir Saha (Motorola Research Lab, India) * Technical Program Committee 1. Ashutosh Dutta (Telcordia Applied Research, USA) 2. Tsunehiko Chiba (KDDI R&D Labs, Japan) * Publicity Chair 1. Vishal K Singh (NEC Labs, USA) 2. R. Muralidharan (Nayna Networks, India) * Publication Chair 1. Aileen Cheng (Telcordia Applied Research, USA) 2. Debabrata Das (IIIT-Bangalore, India ) * Tutorial Chair 1. Jyotsna Bapat (IIIT-Bangalore) * Demo Chair 1. Sachin Deshpande (Sharp Labs, USA) 2. Tilak Kesavapillai (Motorola, India) * Panel Discussion Chair 1. Ajay RajKumar (Alcatel-Lucent, USA) * Local Activities Chair 1. Sreeja M. (Open Call, Hewlett Packard, India) * Registration Chair 1. Koushik Sinha (Honeywell, India) * Treasurer 1. C. M. Abraham (International Institute of Information Technology-Bangalore) ----------------------------------------------------------------------------------- Additional details about the conference can be found at: http://www.iiitb.ac.in/imsaa2008/index.html _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Wed Jul 30 10:49:22 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 418F228C3BA; Wed, 30 Jul 2008 10:49:22 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 582F028C3BA for ; Wed, 30 Jul 2008 10:49:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.419 X-Spam-Level: X-Spam-Status: No, score=-2.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599] 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 uyTcxZCV4trl for ; Wed, 30 Jul 2008 10:49:17 -0700 (PDT) Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id 6EFA53A6BCC for ; Wed, 30 Jul 2008 10:49:16 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 30 Jul 2008 13:49:07 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AAA-based Handover Keys Thread-Index: AcjybJDL1hVd1Mi4Q5SC4tOQisY0xA== From: "Vijay Devarapalli" To: Subject: [Mipshop] AAA-based Handover Keys X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hello Folks, We didn't get a chance to discuss the next steps on AAA-based handover keys. We ran out of time. Here are some observations. For progressing FMIPv6 to Proposed Standard, we have standardized one mechanism based on SeND. I don't expect this mechanism to be implemented by anyone. This could change if SeND does get deployed, but that might take some time. There are some solutions available for AAA-based handover keys. - There is one draft from Alper that talks about deriving the MN-AR key assuming that there is some sort of shared key between the mobile node and the access router. - The second one is from Vidya that defines a new protocol with message exchange between the mobile node, the access router and the handover keying server (presumably on the AAA) for deriving a MN-AR key for use with FMIPv6. - The third one is to punt part of the problem to HOKEY. We assume that there is an USRK available for FMIPv6 and we just describe how to derive the MN-AR key from this USRK. We could pick one and standardize it. But the issue is that I don't think there would be any customers (SDO or non-SDO) for the solution we develop in the MIPSHOP WG. The expectation is that SDOs would use some access-specific signaling to secure MN-AR FMIPv6 messages. I also think that we don't have sufficient information today to pick a solution. So the proposal is to write up an Informational document that says there are a number of ways to leverage the AAA infrastructure to derive MN-AR key for FMIPv6. We don't actually define a solution. Just point to some of the possible solutions. We won't be standardizing any of the solution documents. In addition, we can mention in the document that if there is sufficient interest in one of the solutions or if some solution actually gets deployed in the future, we can pick that and standardize it. The slides that I was going to present are at http://www.ietf.org/proceedings/08jul/slides/mipshop-3.pdf Comments? Vijay _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Wed Jul 30 10:55:40 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E285C28C387; Wed, 30 Jul 2008 10:55:40 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D0DC3A68C7 for ; Wed, 30 Jul 2008 10:55:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.546 X-Spam-Level: X-Spam-Status: No, score=-1.546 tagged_above=-999 required=5 tests=[AWL=1.052, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001] 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 S77EyzuWPb3R for ; Wed, 30 Jul 2008 10:55:39 -0700 (PDT) Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 40EFD3A68AF for ; Wed, 30 Jul 2008 10:55:39 -0700 (PDT) Received: from huawei.com (usaga04-in [172.18.9.16]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K4T00L8RZ54SW@usaga04-in.huawei.com> for mipshop@ietf.org; Wed, 30 Jul 2008 12:55:52 -0500 (CDT) Received: from X24512z ([10.124.12.92]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K4T00557Z52C1@usaga04-in.huawei.com> for mipshop@ietf.org; Wed, 30 Jul 2008 12:55:52 -0500 (CDT) Date: Wed, 30 Jul 2008 12:55:50 -0500 From: Frank Xia To: Vijay Devarapalli , mipshop@ietf.org Message-id: <033801c8f26d$81611740$5c0c7c0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-Priority: 3 X-MSMail-priority: Normal References: Subject: Re: [Mipshop] AAA-based Handover Keys X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi Vijay Sounds good. I think it makes sense to have an informational document. BR Frank ----- Original Message ----- From: "Vijay Devarapalli" To: Sent: Wednesday, July 30, 2008 12:49 PM Subject: [Mipshop] AAA-based Handover Keys > Hello Folks, > > We didn't get a chance to discuss the next steps on AAA-based handover > keys. We ran out of time. Here are some observations. > > For progressing FMIPv6 to Proposed Standard, we have standardized one > mechanism based on SeND. I don't expect this mechanism to be implemented > by anyone. This could change if SeND does get deployed, but that might > take some time. > > There are some solutions available for AAA-based handover keys. > > - There is one draft from Alper that talks about deriving the MN-AR key > assuming that there is some sort of shared key between the mobile node > and the access router. > - The second one is from Vidya that defines a new protocol with message > exchange between the mobile node, the access router and the handover > keying server (presumably on the AAA) for deriving a MN-AR key for use > with FMIPv6. > - The third one is to punt part of the problem to HOKEY. We assume that > there is an USRK available for FMIPv6 and we just describe how to derive > the MN-AR key from this USRK. > > We could pick one and standardize it. But the issue is that I don't > think there would be any customers (SDO or non-SDO) for the solution we > develop in the MIPSHOP WG. The expectation is that SDOs would use some > access-specific signaling to secure MN-AR FMIPv6 messages. I also think > that we don't have sufficient information today to pick a solution. > > So the proposal is to write up an Informational document that says there > are a number of ways to leverage the AAA infrastructure to derive MN-AR > key for FMIPv6. We don't actually define a solution. Just point to some > of the possible solutions. We won't be standardizing any of the solution > documents. In addition, we can mention in the document that if there is > sufficient interest in one of the solutions or if some solution actually > gets deployed in the future, we can pick that and standardize it. > > The slides that I was going to present are at > http://www.ietf.org/proceedings/08jul/slides/mipshop-3.pdf > > Comments? > > Vijay > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www.ietf.org/mailman/listinfo/mipshop > _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Wed Jul 30 13:41:46 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E9753A68C0; Wed, 30 Jul 2008 13:41:46 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75CA73A68DF for ; Wed, 30 Jul 2008 13:41:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 ibkNsQvSmMe9 for ; Wed, 30 Jul 2008 13:41:44 -0700 (PDT) Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 8DF003A685E for ; Wed, 30 Jul 2008 13:41:44 -0700 (PDT) Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m6UKfe8K021152; Wed, 30 Jul 2008 15:41:58 -0500 Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 30 Jul 2008 23:41:15 +0300 Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 30 Jul 2008 15:41:10 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 30 Jul 2008 15:41:09 -0500 Message-ID: <2198383E1141814486F0B881B3260CF50295A2A4@daebe103.NOE.Nokia.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mipshop] AAA-based Handover Keys Thread-Index: AcjybJDL1hVd1Mi4Q5SC4tOQisY0xAAF/CmQ References: From: To: , X-OriginalArrivalTime: 30 Jul 2008 20:41:10.0683 (UTC) FILETIME=[999C6EB0:01C8F284] X-Nokia-AV: Clean Subject: Re: [Mipshop] AAA-based Handover Keys X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Very pragmatic and refreshingly realistic. -----Original Message----- From: mipshop-bounces@ietf.org [mailto:mipshop-bounces@ietf.org] On Behalf Of ext Vijay Devarapalli Sent: 30 July, 2008 10:49 To: mipshop@ietf.org Subject: [Mipshop] AAA-based Handover Keys Hello Folks, We didn't get a chance to discuss the next steps on AAA-based handover keys. We ran out of time. Here are some observations. For progressing FMIPv6 to Proposed Standard, we have standardized one mechanism based on SeND. I don't expect this mechanism to be implemented by anyone. This could change if SeND does get deployed, but that might take some time. There are some solutions available for AAA-based handover keys. - There is one draft from Alper that talks about deriving the MN-AR key assuming that there is some sort of shared key between the mobile node and the access router. - The second one is from Vidya that defines a new protocol with message exchange between the mobile node, the access router and the handover keying server (presumably on the AAA) for deriving a MN-AR key for use with FMIPv6. - The third one is to punt part of the problem to HOKEY. We assume that there is an USRK available for FMIPv6 and we just describe how to derive the MN-AR key from this USRK. We could pick one and standardize it. But the issue is that I don't think there would be any customers (SDO or non-SDO) for the solution we develop in the MIPSHOP WG. The expectation is that SDOs would use some access-specific signaling to secure MN-AR FMIPv6 messages. I also think that we don't have sufficient information today to pick a solution. So the proposal is to write up an Informational document that says there are a number of ways to leverage the AAA infrastructure to derive MN-AR key for FMIPv6. We don't actually define a solution. Just point to some of the possible solutions. We won't be standardizing any of the solution documents. In addition, we can mention in the document that if there is sufficient interest in one of the solutions or if some solution actually gets deployed in the future, we can pick that and standardize it. The slides that I was going to present are at http://www.ietf.org/proceedings/08jul/slides/mipshop-3.pdf Comments? Vijay _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Thu Jul 31 02:49:11 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 092293A6A60; Thu, 31 Jul 2008 02:49:10 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B04E73A6A60 for ; Thu, 31 Jul 2008 02:49:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599] 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 reEspkggGT8s for ; Thu, 31 Jul 2008 02:49:06 -0700 (PDT) Received: from dakia3.marvell.com (dakia3.marvell.com [65.219.4.28]) by core3.amsl.com (Postfix) with ESMTP id DEEB43A6A3F for ; Thu, 31 Jul 2008 02:49:05 -0700 (PDT) X-ASG-Debug-ID: 1217497753-3533036a0000-Psfj6Z X-Barracuda-URL: http://dakia3.marvell.com:80/cgi-bin/mark.cgi Received: from maili.marvell.com (localhost [127.0.0.1]) by dakia3.marvell.com (Spam Firewall) with ESMTP id 9A5145FFEA8; Thu, 31 Jul 2008 02:49:13 -0700 (PDT) Received: from maili.marvell.com (maili.marvell.com [10.68.76.51]) by dakia3.marvell.com with ESMTP id NkPiEaqVdQkhkEey; Thu, 31 Jul 2008 02:49:13 -0700 (PDT) Received: from sc-exch03.marvell.com (sc-exch03.marvell.com [10.68.76.198]) by maili.marvell.com (Postfix) with ESMTP id 9AA735C151; Thu, 31 Jul 2008 02:49:13 -0700 (PDT) X-MIMEOLE: Produced By Microsoft Exchange V6.5 X-Barracuda-BBL-IP: 10.68.76.198 X-Barracuda-RBL-IP: 10.68.76.198 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: RE: [Mipshop] AAA-based Handover Keys Date: Thu, 31 Jul 2008 02:49:10 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mipshop] AAA-based Handover Keys Thread-Index: AcjybJDL1hVd1Mi4Q5SC4tOQisY0xAAhhSiw References: From: "Stefano Faccin" To: "Vijay Devarapalli" , X-Barracuda-Connect: maili.marvell.com[10.68.76.51] X-Barracuda-Start-Time: 1217497753 X-Barracuda-Virus-Scanned: by Marvell Mail Gateway at marvell.com Subject: Re: [Mipshop] AAA-based Handover Keys X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org I would definitely support creating only the informational document. Stefano > -----Original Message----- > From: mipshop-bounces@ietf.org [mailto:mipshop-bounces@ietf.org] On Behalf > Of Vijay Devarapalli > Sent: Wednesday, July 30, 2008 10:49 AM > To: mipshop@ietf.org > Subject: [Mipshop] AAA-based Handover Keys > > Hello Folks, > > We didn't get a chance to discuss the next steps on AAA-based handover > keys. We ran out of time. Here are some observations. > > For progressing FMIPv6 to Proposed Standard, we have standardized one > mechanism based on SeND. I don't expect this mechanism to be implemented > by anyone. This could change if SeND does get deployed, but that might > take some time. > > There are some solutions available for AAA-based handover keys. > > - There is one draft from Alper that talks about deriving the MN-AR key > assuming that there is some sort of shared key between the mobile node > and the access router. > - The second one is from Vidya that defines a new protocol with message > exchange between the mobile node, the access router and the handover > keying server (presumably on the AAA) for deriving a MN-AR key for use > with FMIPv6. > - The third one is to punt part of the problem to HOKEY. We assume that > there is an USRK available for FMIPv6 and we just describe how to derive > the MN-AR key from this USRK. > > We could pick one and standardize it. But the issue is that I don't > think there would be any customers (SDO or non-SDO) for the solution we > develop in the MIPSHOP WG. The expectation is that SDOs would use some > access-specific signaling to secure MN-AR FMIPv6 messages. I also think > that we don't have sufficient information today to pick a solution. > > So the proposal is to write up an Informational document that says there > are a number of ways to leverage the AAA infrastructure to derive MN-AR > key for FMIPv6. We don't actually define a solution. Just point to some > of the possible solutions. We won't be standardizing any of the solution > documents. In addition, we can mention in the document that if there is > sufficient interest in one of the solutions or if some solution actually > gets deployed in the future, we can pick that and standardize it. > > The slides that I was going to present are at > http://www.ietf.org/proceedings/08jul/slides/mipshop-3.pdf > > Comments? > > Vijay > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www.ietf.org/mailman/listinfo/mipshop _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Thu Jul 31 05:22:54 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1BDD53A6C37; Thu, 31 Jul 2008 05:22:54 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14D4E3A6C37 for ; Thu, 31 Jul 2008 05:22:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 B4Xl+pUYpOv0 for ; Thu, 31 Jul 2008 05:22:52 -0700 (PDT) Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id E71513A6932 for ; Thu, 31 Jul 2008 05:22:51 -0700 (PDT) Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m6VCMYae019656; Thu, 31 Jul 2008 07:22:34 -0500 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 31 Jul 2008 07:22:34 -0500 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 31 Jul 2008 08:19:45 -0400 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA05160103@ecamlmw720.eamcs.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mipshop] AAA-based Handover Keys thread-index: AcjybJDL1hVd1Mi4Q5SC4tOQisY0xAAhhSiwAAVEmCg= References: From: "Suresh Krishnan" To: "Stefano Faccin" , "Vijay Devarapalli" , X-OriginalArrivalTime: 31 Jul 2008 12:22:34.0370 (UTC) FILETIME=[1C831620:01C8F308] Subject: Re: [Mipshop] AAA-based Handover Keys X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi Chairs, I think that having at least an informational document is a good idea. I am willing to work on such a document along with other interested folks. Thanks Suresh ________________________________ From: mipshop-bounces@ietf.org on behalf of Stefano Faccin Sent: Thu 31/07/2008 5:49 AM To: Vijay Devarapalli; mipshop@ietf.org Subject: Re: [Mipshop] AAA-based Handover Keys I would definitely support creating only the informational document. Stefano > -----Original Message----- > From: mipshop-bounces@ietf.org [mailto:mipshop-bounces@ietf.org] On Behalf > Of Vijay Devarapalli > Sent: Wednesday, July 30, 2008 10:49 AM > To: mipshop@ietf.org > Subject: [Mipshop] AAA-based Handover Keys > > Hello Folks, > > We didn't get a chance to discuss the next steps on AAA-based handover > keys. We ran out of time. Here are some observations. > > For progressing FMIPv6 to Proposed Standard, we have standardized one > mechanism based on SeND. I don't expect this mechanism to be implemented > by anyone. This could change if SeND does get deployed, but that might > take some time. > > There are some solutions available for AAA-based handover keys. > > - There is one draft from Alper that talks about deriving the MN-AR key > assuming that there is some sort of shared key between the mobile node > and the access router. > - The second one is from Vidya that defines a new protocol with message > exchange between the mobile node, the access router and the handover > keying server (presumably on the AAA) for deriving a MN-AR key for use > with FMIPv6. > - The third one is to punt part of the problem to HOKEY. We assume that > there is an USRK available for FMIPv6 and we just describe how to derive > the MN-AR key from this USRK. > > We could pick one and standardize it. But the issue is that I don't > think there would be any customers (SDO or non-SDO) for the solution we > develop in the MIPSHOP WG. The expectation is that SDOs would use some > access-specific signaling to secure MN-AR FMIPv6 messages. I also think > that we don't have sufficient information today to pick a solution. > > So the proposal is to write up an Informational document that says there > are a number of ways to leverage the AAA infrastructure to derive MN-AR > key for FMIPv6. We don't actually define a solution. Just point to some > of the possible solutions. We won't be standardizing any of the solution > documents. In addition, we can mention in the document that if there is > sufficient interest in one of the solutions or if some solution actually > gets deployed in the future, we can pick that and standardize it. > > The slides that I was going to present are at > http://www.ietf.org/proceedings/08jul/slides/mipshop-3.pdf > > Comments? > > Vijay > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www.ietf.org/mailman/listinfo/mipshop _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop From mipshop-bounces@ietf.org Thu Jul 31 05:47:15 2008 Return-Path: X-Original-To: mipshop-archive@megatron.ietf.org Delivered-To: ietfarch-mipshop-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E4293A6BF2; Thu, 31 Jul 2008 05:47:15 -0700 (PDT) X-Original-To: mipshop@core3.amsl.com Delivered-To: mipshop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8384F3A6BF2 for ; Thu, 31 Jul 2008 05:47:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.084 X-Spam-Level: *** X-Spam-Status: No, score=3.084 tagged_above=-999 required=5 tests=[AWL=3.579, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] 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 e4iHidS4iqwy for ; Thu, 31 Jul 2008 05:47:12 -0700 (PDT) Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 6E5BB3A6AA2 for ; Thu, 31 Jul 2008 05:47:12 -0700 (PDT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K4V00L7PF8GH4@szxga03-in.huawei.com> for mipshop@ietf.org; Thu, 31 Jul 2008 20:41:04 +0800 (CST) Received: from huawei.com ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K4V001FJF8GOJ@szxga03-in.huawei.com> for mipshop@ietf.org; Thu, 31 Jul 2008 20:41:04 +0800 (CST) Received: from jysa3108021144 (jysa3108021144.meeting.ietf.org [130.129.23.20]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K4V00EZ6F8BQD@szxml02-in.huawei.com>; Thu, 31 Jul 2008 20:41:04 +0800 (CST) Date: Thu, 31 Jul 2008 13:40:57 +0100 From: "John.zhao" To: Vijay Devarapalli , "mipshop@ietf.org" Message-id: <0K4V00EZ9F8DQD@szxml02-in.huawei.com> Organization: Huawei Technologies Co.,LTD MIME-version: 1.0 X-Mailer: Foxmail 5.0 beta1 [cn] Subject: Re: [Mipshop] AAA-based Handover Keys X-BeenThere: mipshop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: john.zhao@huawei.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mipshop-bounces@ietf.org Errors-To: mipshop-bounces@ietf.org Hi,Chairs +1. Best Rgds, Thanks, John.zhao john.zhao@huawei.com 2008-07-31 ======= 2008-07-31 08:19:00 You have said:======= >Hi Chairs, > I think that having at least an informational document is a good idea. I am willing to work on such a document along with other interested folks. > >Thanks >Suresh > >________________________________ > >From: mipshop-bounces@ietf.org on behalf of Stefano Faccin >Sent: Thu 31/07/2008 5:49 AM >To: Vijay Devarapalli; mipshop@ietf.org >Subject: Re: [Mipshop] AAA-based Handover Keys > > > >I would definitely support creating only the informational document. >Stefano > >> -----Original Message----- >> From: mipshop-bounces@ietf.org [mailto:mipshop-bounces@ietf.org] On >Behalf >> Of Vijay Devarapalli >> Sent: Wednesday, July 30, 2008 10:49 AM >> To: mipshop@ietf.org >> Subject: [Mipshop] AAA-based Handover Keys >> >> Hello Folks, >> >> We didn't get a chance to discuss the next steps on AAA-based handover >> keys. We ran out of time. Here are some observations. >> >> For progressing FMIPv6 to Proposed Standard, we have standardized one >> mechanism based on SeND. I don't expect this mechanism to be >implemented >> by anyone. This could change if SeND does get deployed, but that might >> take some time. >> >> There are some solutions available for AAA-based handover keys. >> >> - There is one draft from Alper that talks about deriving the MN-AR >key >> assuming that there is some sort of shared key between the mobile node >> and the access router. >> - The second one is from Vidya that defines a new protocol with >message >> exchange between the mobile node, the access router and the handover >> keying server (presumably on the AAA) for deriving a MN-AR key for use >> with FMIPv6. >> - The third one is to punt part of the problem to HOKEY. We assume >that >> there is an USRK available for FMIPv6 and we just describe how to >derive >> the MN-AR key from this USRK. >> >> We could pick one and standardize it. But the issue is that I don't >> think there would be any customers (SDO or non-SDO) for the solution >we >> develop in the MIPSHOP WG. The expectation is that SDOs would use some >> access-specific signaling to secure MN-AR FMIPv6 messages. I also >think >> that we don't have sufficient information today to pick a solution. >> >> So the proposal is to write up an Informational document that says >there >> are a number of ways to leverage the AAA infrastructure to derive >MN-AR >> key for FMIPv6. We don't actually define a solution. Just point to >some >> of the possible solutions. We won't be standardizing any of the >solution >> documents. In addition, we can mention in the document that if there >is >> sufficient interest in one of the solutions or if some solution >actually >> gets deployed in the future, we can pick that and standardize it. >> >> The slides that I was going to present are at >> http://www.ietf.org/proceedings/08jul/slides/mipshop-3.pdf >> >> Comments? >> >> Vijay >> _______________________________________________ >> Mipshop mailing list >> Mipshop@ietf.org >> https://www.ietf.org/mailman/listinfo/mipshop >_______________________________________________ >Mipshop mailing list >Mipshop@ietf.org >https://www.ietf.org/mailman/listinfo/mipshop > > >_______________________________________________ >Mipshop mailing list >Mipshop@ietf.org >https://www.ietf.org/mailman/listinfo/mipshop = = = = = = = = = = = = = = = = = = = = _______________________________________________ Mipshop mailing list Mipshop@ietf.org https://www.ietf.org/mailman/listinfo/mipshop