Re: [tram] I-D Action: draft-ietf-tram-turn-mobility-00.txt
"Pal Martinsen (palmarti)" <palmarti@cisco.com> Wed, 27 January 2016 14:12 UTC
Return-Path: <palmarti@cisco.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0B311B2E87 for <tram@ietfa.amsl.com>; Wed, 27 Jan 2016 06:12:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gT6pA7ftllQh for <tram@ietfa.amsl.com>; Wed, 27 Jan 2016 06:12:32 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C07771B2E80 for <tram@ietf.org>; Wed, 27 Jan 2016 06:12:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6714; q=dns/txt; s=iport; t=1453903952; x=1455113552; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=DXLGdQZLUatJgp4YvHRQY8kBDDRq/5VE+bZXUMKE2YI=; b=atVyIEBM4cjEXqDD9n/X3DOMJAQvSBHqbJXgVoc/hdwLcckd2ns8YUSv TQLNLb/4sYMFFPD2P8J1YILwu6KHqN2eLyB1IsXMWjEYNPMi9vKgsUV/j FUcJcxtUTclYbFRZ3PK7foGSByjoS7g50WvbLI9CBmv6CrdGs9eOuZMGM o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0APAgCxz6hW/49dJa1egzpSbQaIUbFOAQ2BYhgKhW0CHIEpOBQBAQEBAQEBgQqEQQEBAQMBAQEBIBE6CwULAgEIGAICJgICAiULFRACBA4FG4d4CA6uL48vAQEBAQEBAQEBAQEBAQEBAQEBAQEBFXuFGYFtgkqEIQYogmsrgQ8FlnsBhUaID4FfSoN6iFeOQgEeAQFCg2xqh0h9AQEB
X-IronPort-AV: E=Sophos;i="5.22,354,1449532800"; d="scan'208";a="67454157"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Jan 2016 14:12:31 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u0RECV3p031160 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 27 Jan 2016 14:12:31 GMT
Received: from xch-rtp-019.cisco.com (64.101.220.159) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 27 Jan 2016 09:12:30 -0500
Received: from xch-rtp-019.cisco.com ([64.101.220.159]) by XCH-RTP-019.cisco.com ([64.101.220.159]) with mapi id 15.00.1104.009; Wed, 27 Jan 2016 09:12:30 -0500
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: Brandon Williams <brandon.williams@akamai.com>
Thread-Topic: [tram] I-D Action: draft-ietf-tram-turn-mobility-00.txt
Thread-Index: AQHRGd8PNyYawqYrh0qti/HaNjIsw58IeWgAgAfALoA=
Date: Wed, 27 Jan 2016 14:12:30 +0000
Message-ID: <C523146A-BB55-46FE-AE8D-5C9C5748267C@cisco.com>
References: <20151108043622.19002.79331.idtracker@ietfa.amsl.com> <56A24FDA.9000806@akamai.com>
In-Reply-To: <56A24FDA.9000806@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.220.158]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4661A6D6C97A9D4182379AA0165D18E3@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tram/-LmAztJ21SDcmJEcrqZTGr3F-9c>
Cc: "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turn-mobility-00.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2016 14:12:35 -0000
Thanks for review and comments > On 22 Jan 2016, at 16:50, Brandon Williams <brandon.williams@akamai.com> wrote: > > I've got a couple of comments on the current version of the draft. > > s3.1.2 > The current text has some discussion of path MTU and STUN message size > restrictions that relates to requirements that I think we have > previously decided to relax. If my memory is correct, we decided in > Dallas to allow request/response messages to assume reasonable path MTU > values (rather than the IPv4 minimum), so we might want to avoid > reiterating limiting guidance from RFC5389. I can't find reference to > this decision in the meeting minutes from Dallas, though, so maybe I'm > mistaken. Nevertheless, it's probably better to just mention that you > can't assume MTUs are the same and point to RFC5389 for further > guidance, rather than repeating requirements language. > +1. Should be fixed up in the document. > s3.2.2 > A common use case for mobility will likely be what some have described > as the "walk out the door" problem. Two interfaces are functional (e.g. > both wifi and lte) and you want to seamlessly switch from one to the > other. You probably want to be able to use both interfaces at the same > time while you're figuring out whether/when to switch from one to the > other (make before break). I don't think the current text supports this, > since it indicates that 1) the tuple for the allocation should be > updated and 2) the old ticket can only be used for retransmission. If > I'm misunderstanding the intent of the text, then it would be helpful to > see some explicit discussion of this use case. > Hmm. I think you are right. Will try to write up something. > Finally (same section), while I can see the value of maintaining the > existing allocation when switching between interfaces/addresses, > sticking to that relay server could be a bad idea if there are > other/better options for the new address. To support make before break > in this case, I think it would be useful for the relay server to be able > to send an ALTERNATE-SERVER attribute in its Refresh response message. > IOW, allow the client to continue using the new allocation, but also let > it know that a different/better relay is available for that address. > There would likely be some ICE work associated with supporting such an > option, so maybe it belongs in a separate more-general doc since > turn-mobility is useful without it, but it seemed worth bringing up in > this context. > Yes, the intention was to have a MICE draft (Mobility for ICE) that covers some of those use-cases. But we are waiting for all the trickle and nomination discussions to finalise to see if there is actually a need for a mobility extension. .-. Pål-Erik > --Brandon > > On 11/07/2015 11:36 PM, internet-drafts@ietf.org wrote: >> >> A New Internet-Draft is available from the on-line Internet-Drafts directories. >> This draft is a work item of the TURN Revised and Modernized Working Group of the IETF. >> >> Title : Mobility with TURN >> Authors : Dan Wing >> Prashanth Patil >> Tirumaleswar Reddy >> Paal-Erik Martinsen >> Filename : draft-ietf-tram-turn-mobility-00.txt >> Pages : 11 >> Date : 2015-11-07 >> >> Abstract: >> It is desirable to minimize traffic disruption caused by changing IP >> address during a mobility event. One mechanism to minimize >> disruption is to expose a shorter network path to the mobility event >> so only the local network elements are aware of the changed IP >> address but the remote peer is unaware of the changed IP address. >> >> This draft provides such an IP address mobility solution using >> Traversal Using Relays around NAT (TURN). This is achieved by >> allowing a client to retain an allocation on the TURN server when the >> IP address of the client changes. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/ >> >> There's also a htmlized version available at: >> https://tools.ietf.org/html/draft-ietf-tram-turn-mobility-00 >> >> >> Please note that it may take a couple of minutes from the time of submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> tram mailing list >> tram@ietf.org >> https://www.ietf.org/mailman/listinfo/tram >> > > _______________________________________________ > tram mailing list > tram@ietf.org > https://www.ietf.org/mailman/listinfo/tram
- [tram] I-D Action: draft-ietf-tram-turn-mobility-… internet-drafts
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Brandon Williams
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Pal Martinsen (palmarti)
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Pal Martinsen (palmarti)
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Tirumaleswar Reddy (tireddy)
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Brandon Williams
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Tirumaleswar Reddy (tireddy)
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Brandon Williams
- Re: [tram] I-D Action: draft-ietf-tram-turn-mobil… Tirumaleswar Reddy (tireddy)