From nobody Thu Mar 10 20:39:05 2016 Return-Path: X-Original-To: tram@ietf.org Delivered-To: tram@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EC39A12E000; Thu, 10 Mar 2016 20:39:03 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.16.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160311043903.2754.65997.idtracker@ietfa.amsl.com> Date: Thu, 10 Mar 2016 20:39:03 -0800 Archived-At: Cc: tram@ietf.org Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt X-BeenThere: tram@ietf.org X-Mailman-Version: 2.1.17 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 04:39:04 -0000 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 of the IETF. Title : Mobility with TURN Authors : Dan Wing Prashanth Patil Tirumaleswar Reddy Paal-Erik Martinsen Filename : draft-ietf-tram-turn-mobility-01.txt Pages : 12 Date : 2016-03-10 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-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turn-mobility-01 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/ From nobody Thu Mar 10 20:48:49 2016 Return-Path: X-Original-To: tram@ietfa.amsl.com Delivered-To: tram@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29F4212DAF9 for ; Thu, 10 Mar 2016 20:48:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.521 X-Spam-Level: X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com 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 pXIZpdNhECkf for ; Thu, 10 Mar 2016 20:48:46 -0800 (PST) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ED9E12DA9D for ; Thu, 10 Mar 2016 20:48:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2335; q=dns/txt; s=iport; t=1457671726; x=1458881326; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ZSYGuHpHzC7Tk1rcQqcJOr+UIvLv5o0BtiC5JWXpFZY=; b=MZ4j/8iZpkI4SyeuVHQPxq4+WPlYnRuJtvAQ0+dyIX7ezU5gSz0Ifkgp qs1Ek6q5K3mSqdNOnRF0UZJBznorP4qyzPBjrDiNWTfJdTv7KqNaR9LvX yCj1Un48jX1d2mnb2bubbQjCuNtMh1pqjIK7HXxP5/o7czxOg2OfeyShz M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgD/TeJW/4sNJK1egz5SbQa6IwENg?= =?us-ascii?q?W0XCoVuAoFBOBQBAQEBAQEBZBwLhEEBAQEEAQEBNzQXBAIBCBEEAQEfCQcnCxQ?= =?us-ascii?q?JCAIEEwgTiAkOvU0BAQEBAQEBAQEBAQEBAQEBAQEBAQEVhhiEQoQihFIFlz0Bh?= =?us-ascii?q?WuICIFrS4N8iFSOawEeAQFCg2RqiVN+AQEB?= X-IronPort-AV: E=Sophos;i="5.24,319,1454976000"; d="scan'208";a="248231107" Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Mar 2016 04:48:43 +0000 Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u2B4mh9a001899 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Fri, 11 Mar 2016 04:48:43 GMT Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 10 Mar 2016 22:48:42 -0600 Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1104.009; Thu, 10 Mar 2016 22:48:43 -0600 From: "Tirumaleswar Reddy (tireddy)" To: "tram@ietf.org" Thread-Topic: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt Thread-Index: AQHRe0/1XNdwPPuTokCC39MWoUNZe59TqZBw Date: Fri, 11 Mar 2016 04:48:42 +0000 Message-ID: References: <20160311043903.2754.65997.idtracker@ietfa.amsl.com> In-Reply-To: <20160311043903.2754.65997.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.65.82.91] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt X-BeenThere: tram@ietf.org X-Mailman-Version: 2.1.17 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 04:48:48 -0000 This revision adds support for make-before-break and addresses comments fro= m Brandon. -Tiru > -----Original Message----- > From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet- > drafts@ietf.org > Sent: Friday, March 11, 2016 10:09 AM > To: i-d-announce@ietf.org > Cc: tram@ietf.org > Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the TURN Revised and Modernized of the IETF. >=20 > Title : Mobility with TURN > Authors : Dan Wing > Prashanth Patil > Tirumaleswar Reddy > Paal-Erik Martinsen > Filename : draft-ietf-tram-turn-mobility-01.txt > Pages : 12 > Date : 2016-03-10 >=20 > 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. >=20 > 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. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/ >=20 > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-tram-turn-mobility-01 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tram-turn-mobility-01 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > tram mailing list > tram@ietf.org > https://www.ietf.org/mailman/listinfo/tram From nobody Mon Mar 21 11:08:18 2016 Return-Path: X-Original-To: tram@ietfa.amsl.com Delivered-To: tram@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296BC12DA04 for ; Mon, 21 Mar 2016 11:08:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.722 X-Spam-Level: X-Spam-Status: No, score=-2.722 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_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=akamai.com 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 G-I8ibf_Q6CA for ; Mon, 21 Mar 2016 11:08:14 -0700 (PDT) Received: from prod-mail-xrelay05.akamai.com (prod-mail-xrelay05.akamai.com [23.79.238.179]) by ietfa.amsl.com (Postfix) with ESMTP id 8849F12D9E7 for ; Mon, 21 Mar 2016 11:08:12 -0700 (PDT) Received: from prod-mail-xrelay05.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id D9C3F3F4010 for ; Mon, 21 Mar 2016 18:08:11 +0000 (GMT) Received: from prod-mail-relay11.akamai.com (prod-mail-relay11.akamai.com [172.27.118.250]) by prod-mail-xrelay05.akamai.com (Postfix) with ESMTP id BA01D4F0CA for ; Mon, 21 Mar 2016 18:08:11 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1458583691; bh=jRxlmESDCfSKbdrLDVMxztjzTciusUqQrGXCaB0ChM4=; l=3972; h=To:References:From:Date:In-Reply-To:From; b=sbi6c50LKdIANnhGLtrgEEdGCADbJCfeKTpUSgc4f+9UZtOSBY+bqxcAF8vZdZ/EB FBYcSSpb929EwKuPKQHmlTDqKugQiXacd8P3YqgCavt587mrezbKPw8FuPw4h7mNTR wZESUovA+ux25rcIwA9udsc02eAxaL8eXoIIzKMk= Received: from [172.28.112.97] (bowill.kendall.corp.akamai.com [172.28.112.97]) by prod-mail-relay11.akamai.com (Postfix) with ESMTP id B63921FC88 for ; Mon, 21 Mar 2016 18:08:11 +0000 (GMT) To: tram@ietf.org References: <20160311043903.2754.65997.idtracker@ietfa.amsl.com> From: Brandon Williams Message-ID: <56F0388B.20805@akamai.com> Date: Mon, 21 Mar 2016 14:08:11 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt X-BeenThere: tram@ietf.org X-Mailman-Version: 2.1.17 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2016 18:08:17 -0000 Hi Tiru, Thanks for the update. I've got two minor comments. The new text about fragmentation and ticket length is less specific than the old text, but it still repeats guidance from the RFC that I believe we've agreed to change in STUNbis. How about instead of this: "... assume that the path MTU is unknown and MUST ensure that the ticket length is restricted to avoid UDP fragmentation ...", we say this: "... assume that the path MTU is unknown and use a ticket length in accordance with published guidance on STUN UDP fragmentation ...". This wording defers all requirements language to the STUN RFC but still calls out the possible concern. In the paragraph describing the handling of a verified Refresh request, it states "The server then updates it's state data with the new client IP address and port but does not discard the old 5-tuple from it's state data." However, in the next paragraph, the new text states "After receiving any of those messages, a TURN server updates its 5-tuple with the new client IP address and port." I think what you want in the second paragraph is "After receiving any of those messages, a TURN server discards the 5-tuple associated with the old MOBILITY-TICKET from its state data." In that paragraph, you can probably also say that it discards the old MOBILITY-TICKET at that point without waiting for the timeout, although the text about holding onto the old MOBILITY-TICKET hasn't appeared yet (it's in the next paragraph). --Brandon On 03/10/2016 11:48 PM, Tirumaleswar Reddy (tireddy) wrote: > This revision adds support for make-before-break and addresses comments from Brandon. > > -Tiru > >> -----Original Message----- >> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet- >> drafts@ietf.org >> Sent: Friday, March 11, 2016 10:09 AM >> To: i-d-announce@ietf.org >> Cc: tram@ietf.org >> Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt >> >> >> 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 of the IETF. >> >> Title : Mobility with TURN >> Authors : Dan Wing >> Prashanth Patil >> Tirumaleswar Reddy >> Paal-Erik Martinsen >> Filename : draft-ietf-tram-turn-mobility-01.txt >> Pages : 12 >> Date : 2016-03-10 >> >> 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-01 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turn-mobility-01 >> >> >> 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 > -- Brandon Williams; Chief Architect Cloud Networking; Akamai Technologies Inc. From nobody Tue Mar 22 00:53:47 2016 Return-Path: X-Original-To: tram@ietfa.amsl.com Delivered-To: tram@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2F912D692 for ; Tue, 22 Mar 2016 00:53:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.522 X-Spam-Level: X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com 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 rMysCWtMyOsr for ; Tue, 22 Mar 2016 00:53:44 -0700 (PDT) Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28F1B12D68B for ; Tue, 22 Mar 2016 00:53:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5129; q=dns/txt; s=iport; t=1458633224; x=1459842824; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=wOswSNw0RilMHsuz+4FlQea6C+JKl0KRHM+SbYkv6Zw=; b=eeeorm2xLmWYKBwdYoyNKUFmpX0vn2kpJ0WK7k9euwq1tThwS2k3qjay fPJpoxj8PWpGQ6gALGlbS/Qya8G0tDvMfhZK5zsadhC0xsvPspOB3KnK3 LNNhXy/jMhioOC1EV/NFxSg8wWddLmeNKPWXU05otCbtcMWdN6CWti7uq Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgDD+PBW/4sNJK1egzNTega6PgENg?= =?us-ascii?q?XAXCoVsAoE6OBQBAQEBAQEBZCeEQQEBAQMBAQEBNzQQBwQCAQgRBAEBAR4JByc?= =?us-ascii?q?LFAkIAgQBEggTiAQIDr4MAQEBAQEBAQEBAQEBAQEBAQEBAQEBFYYehESEJAaFa?= =?us-ascii?q?AWXVwGFcIgMgWxLg3+IWIYOiHcBHgEBQoNlaokIfgEBAQ?= X-IronPort-AV: E=Sophos;i="5.24,376,1454976000"; d="scan'208";a="251453260" Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Mar 2016 07:53:42 +0000 Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u2M7rgcE003159 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 22 Mar 2016 07:53:42 GMT Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 22 Mar 2016 02:53:41 -0500 Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1104.009; Tue, 22 Mar 2016 02:53:42 -0500 From: "Tirumaleswar Reddy (tireddy)" To: Brandon Williams , "tram@ietf.org" Thread-Topic: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt Thread-Index: AQHRe0/1XNdwPPuTokCC39MWoUNZe59TqZBwgBDs44CAAI7u8A== Date: Tue, 22 Mar 2016 07:53:41 +0000 Message-ID: <995693f2812e48efa262c8f1bf23d8c9@XCH-RCD-017.cisco.com> References: <20160311043903.2754.65997.idtracker@ietfa.amsl.com> <56F0388B.20805@akamai.com> In-Reply-To: <56F0388B.20805@akamai.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.65.60.143] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt X-BeenThere: tram@ietf.org X-Mailman-Version: 2.1.17 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2016 07:53:46 -0000 Hi Brandon, Please see inline=20 > -----Original Message----- > From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Brandon Williams > Sent: Monday, March 21, 2016 11:38 PM > To: tram@ietf.org > Subject: Re: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt >=20 > Hi Tiru, >=20 > Thanks for the update. I've got two minor comments. >=20 > The new text about fragmentation and ticket length is less specific than = the > old text, but it still repeats guidance from the RFC that I believe we've= agreed > to change in STUNbis.=20 I don't see any specific changes in STUNbis yet to handle fragmentation ! > How about instead of this: "... > assume that the path MTU is unknown and MUST ensure that the ticket > length is restricted to avoid UDP fragmentation ...", we say this: "... > assume that the path MTU is unknown and use a ticket length in accordance > with published guidance on STUN UDP fragmentation ...". This wording > defers all requirements language to the STUN RFC but still calls out the > possible concern. Okay, updated. >=20 > In the paragraph describing the handling of a verified Refresh request, i= t > states "The server then updates it's state data with the new client IP ad= dress > and port but does not discard the old 5-tuple from it's state data." Howe= ver, > in the next paragraph, the new text states "After receiving any of those > messages, a TURN server updates its 5-tuple with the new client IP addres= s > and port." I think what you want in the second paragraph is "After receiv= ing > any of those messages, a TURN server discards the 5-tuple associated with > the old MOBILITY-TICKET from its state data." In that paragraph, you can > probably also say that it discards the old MOBILITY-TICKET at that point > without waiting for the timeout, although the text about holding onto the= old > MOBILITY-TICKET hasn't appeared yet (it's in the next paragraph). NEW: After receiving any of those messages, a TURN server discards the 5-tuple a= ssociated with the old MOBILITY-TICKET and the old MOBILITY-TICKET from its= state data. -Tiru >=20 > --Brandon >=20 > On 03/10/2016 11:48 PM, Tirumaleswar Reddy (tireddy) wrote: > > This revision adds support for make-before-break and addresses > comments from Brandon. > > > > -Tiru > > > >> -----Original Message----- > >> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet- > >> drafts@ietf.org > >> Sent: Friday, March 11, 2016 10:09 AM > >> To: i-d-announce@ietf.org > >> Cc: tram@ietf.org > >> Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-01.txt > >> > >> > >> 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 of the IE= TF. > >> > >> Title : Mobility with TURN > >> Authors : Dan Wing > >> Prashanth Patil > >> Tirumaleswar Reddy > >> Paal-Erik Martinsen > >> Filename : draft-ietf-tram-turn-mobility-01.txt > >> Pages : 12 > >> Date : 2016-03-10 > >> > >> 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 eve= nt > >> 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-01 > >> > >> A diff from the previous version is available at: > >> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tram-turn-mobility-01 > >> > >> > >> 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 > > >=20 > -- > Brandon Williams; Chief Architect > Cloud Networking; Akamai Technologies Inc. >=20 > _______________________________________________ > tram mailing list > tram@ietf.org > https://www.ietf.org/mailman/listinfo/tram