Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Thu, 27 March 2014 18:36 UTC

Return-Path: <gsalguei@cisco.com>
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 9476E1A01CC for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 11:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level:
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 K0-dAoue6-X7 for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 11:36:24 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 70EAB1A0182 for <mmusic@ietf.org>; Thu, 27 Mar 2014 11:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2348; q=dns/txt; s=iport; t=1395945382; x=1397154982; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=SmzsaRS0FDgJhCKrATD5Tq1N4gtq6AiCQ897d6tWpgc=; b=frVo866un1PICeZxU8Hk/P2FT4xqthoO6ufeoqvf7l+0eEwxeOrfgg3r fNFxrpiUf66AvvnQVmE5OxHu9PDEVNJMe3YREE+k2d4nqA9cCJjYN1KOH DZ0cRKa2YEftOi2LLJ4+RtSeswYQUcHQUO1N0XvpOye4nsku5A8ag3G7f Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFAKhuNFOtJXHB/2dsb2JhbABZgwY7V7smhmZRgR4WdIIlAQEBAwEBAQE3NAsQAgEINhAnCyUCBA4Fh3EIDdEbEwSORzMHgySBFASYTZI0gy+CKw
X-IronPort-AV: E=Sophos;i="4.97,744,1389744000"; d="scan'208";a="30916025"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-2.cisco.com with ESMTP; 27 Mar 2014 18:36:20 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s2RIaKu9029353 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 27 Mar 2014 18:36:20 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.5]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Thu, 27 Mar 2014 13:36:19 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhBJKPOVBvPeUSLNNz5ik5Wcpr1Co+AgAA1L2CAAFomgA==
Date: Thu, 27 Mar 2014 18:36:19 +0000
Message-ID: <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>
References: <5331E601.8070605@cisco.com>, <53344BC7.3040409@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.234.45]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8FF01F9F9939B643854B4D787CE7736F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/_sygEGVlel9Vz1k6GmZG2HJxtY0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Mar 2014 18:36:26 -0000

On Mar 27, 2014, at 2:28 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> 
> Hi,
> 
>> Here are my comments based on a quick review of this draft:
>> 
>> Section 4.5:
>> 
>> nit: s/are unchanged are unchanged/are unchanged/
> 
> I'll fix that.
> 
> 
> ---------------------------
> 
> 
>> If a new DTLS association is to be established, is it well defined when
>> to cut over to it? ISTM that some procedures are required here to ensure
>> that data isn't lost, or replicated.
> 
> I don't think we can define any exact procedures for that. DTLS-SRTP doesn't define any exact procedures either. RFC 5763 only says:
> 
>  "Once the new session keys are established, the session can switch to using these and abandon the old keys."
> 
> ...and I don't think we can say much more.
> 
> In addition, I assume there are procedures on the fax application layer for avoiding lost data.
> 
> Also, I think it will be rare that the keys and/or transport parameters change during a fax transmission. Or, if they do, perhaps a fax transmission failure is acceptable?

Data loss prevention/recovery mechanisms are in place at the fax layer.

-G

> ---------------------------
> 
> 
>> Section A.2, Figure 3:
>> 
>> This shows the entire DTLS handshake taking place before the UAS sends
>> *any* sip response. I assume this is only for convenience, and isn't
>> intended to imply that this is how it should be done. In reality, it is
>> likely that *some* sip response will be sent and received before the
>> DTLS handshake completes - maybe before it starts.
>> 
>> It would be helpful to comment on this.
> 
> Flemming had a similar comment. We addressed that by adding the following paragraph to the description text for Message (4):
> 
>      "Note that, unlike in this example, it is not necessary to wait for
>      the DTLS handshake to finish before the SDP answer is sent.  If
>      Bob has sent the SIP 200 (OK) response and later detects that the
>      certificate fingerprints do not match, he will terminate the
>      session."
> 
> Regards,
> 
> Christer
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic