Return-Path: X-Original-To: mmusic@ietfa.amsl.com Delivered-To: mmusic@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE801B2CD9 for ; Wed, 17 Jun 2015 13:03:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.378 X-Spam-Level: X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_24=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 cLr-2DHT5hMU for ; Wed, 17 Jun 2015 13:03:44 -0700 (PDT) Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 779111B2BF8 for ; Wed, 17 Jun 2015 13:03:44 -0700 (PDT) Received: by iebmu5 with SMTP id mu5so41377948ieb.1 for ; Wed, 17 Jun 2015 13:03:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+UYs4ngckHrMmXGbno7jEEBlLRuOiam+z58CA2uE/dg=; b=hnCssYcklZ3S/25tBorOAjY78hqOOXjXoFk2YDRarnnaUuXNpFR+fviIr2oXAwm+jR ZT5CWlBlOb8glSHbzsBGf8BnzFjkH3BMGhsHJuYElt7r6+KmZNrQ4ME+CPhQ4YChQk5k BzjeD92zIeSF4r4NpF4oIIT38kQn3G1VNRRenyl3zvF2ldeKe0smln5l8lA4U4oyX/WO VdSNLYLwP/0h2ox5PCUpvevOWu0sdAVpyARwZlnBuCtUQfw0H0SfQvWY+5xjmQE9gsr2 VAzxvToFWw7Ky/dY4aEEx4H898RPnYdkUHOGhe3AKg8uRqcU5aiItEhsT/etGhnGAMCn uB2Q== X-Gm-Message-State: ALoCoQlJm9YaaafYK4m6LXO7578EiiFctW4pgga13B6RgT3uGC9Q7ZEpoRGZKHc7qQafQ+WlnXwo X-Received: by 10.43.162.136 with SMTP id mk8mr2082213icc.28.1434571423863; Wed, 17 Jun 2015 13:03:43 -0700 (PDT) Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com. [209.85.213.179]) by mx.google.com with ESMTPSA id s5sm3834939igh.6.2015.06.17.13.03.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Jun 2015 13:03:42 -0700 (PDT) Received: by igboe5 with SMTP id oe5so2060891igb.1 for ; Wed, 17 Jun 2015 13:03:41 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.155.74 with SMTP id d71mr10500282ioe.29.1434571421749; Wed, 17 Jun 2015 13:03:41 -0700 (PDT) Received: by 10.36.89.70 with HTTP; Wed, 17 Jun 2015 13:03:41 -0700 (PDT) In-Reply-To: References: Date: Wed, 17 Jun 2015 16:03:41 -0400 Message-ID: From: Roman Shpount To: Martin Thomson Content-Type: multipart/alternative; boundary=001a1140eadaffba970518bc2f82 Archived-At: Cc: "mmusic@ietf.org" Subject: Re: [MMUSIC] Fixing draft-holmberg-mmusic-sdp-dtls-00 X-BeenThere: mmusic@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multiparty Multimedia Session Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 20:03:46 -0000 --001a1140eadaffba970518bc2f82 Content-Type: text/plain; charset=UTF-8 If you add that you also define an attribute to tell if remote party is performing ICE restart or setting up new ICE connection then you got it covered. _____________ Roman Shpount On Wed, Jun 17, 2015 at 2:10 PM, Martin Thomson wrote: > Some of the statements here are backwards. For example, > > If an endpoint changes the local transport parameters associated with > a DTLS association, the endpoint MUST create a new DTLS association. > > I think that this document can be reduced to a series of conditionals: > > If you change the endpoint that is participating (because forking, or > for any other reason), then you need a new DTLS association. > Otherwise, how will that new endpoint know what keys to use. > > If you change the certificate you intend to use, then you need a new > DTLS association. Otherwise, you don't get to send the new > certificate. > > If you change the DTLS roles, then you need a new DTLS association. > Otherwise, it doesn't happen. > > If you request a new DTLS association, then you need a new transport. > Otherwise, demux issues. > > An ICE restart is not sufficient a change to constitute a new > transport. You need entirely new IP+port pairs. > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic > --001a1140eadaffba970518bc2f82 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
If you add that you also define an attribute to tell if re= mote party is performing ICE restart or setting up new ICE connection then = you got it covered.

_____________
Roman Shpount

On Wed, Jun 17, 2015 at 2:10 PM, Martin Thom= son <martin.thomson@gmail.com> wrote:
Some of the statements here are backwards.=C2=A0 For exa= mple,

=C2=A0 =C2=A0If an endpoint changes the local transport parameters associat= ed with
=C2=A0 =C2=A0a DTLS association, the endpoint MUST create a new DTLS associ= ation.

I think that this document can be reduced to a series of conditionals:

If you change the endpoint that is participating (because forking, or
for any other reason), then you need a new DTLS association.
Otherwise, how will that new endpoint know what keys to use.

If you change the certificate you intend to use, then you need a new
DTLS association.=C2=A0 Otherwise, you don't get to send the new
certificate.

If you change the DTLS roles, then you need a new DTLS association.
Otherwise, it doesn't happen.

If you request a new DTLS association, then you need a new transport.
Otherwise, demux issues.

An ICE restart is not sufficient a change to constitute a new
transport.=C2=A0 You need entirely new IP+port pairs.

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

--001a1140eadaffba970518bc2f82--