Re: [MMUSIC] Alvaro Retana's No Objection on draft-ietf-mmusic-rtsp-nat-evaluation-15: (with COMMENT)

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 13 May 2015 13:11 UTC

Return-Path: <aretana@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 5F55C1A873E; Wed, 13 May 2015 06:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, 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 n_imSdjqN-vZ; Wed, 13 May 2015 06:11:16 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 573611A87E7; Wed, 13 May 2015 06:11:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2203; q=dns/txt; s=iport; t=1431522675; x=1432732275; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LYoa5vqe7TDeOl92HStzNzqEfTXVC9h/IopjLu0xk9c=; b=ZNgFp9SxUTwx+47bHGZ0zwZcim7oGCm7aLUcloSynNJqpiMWZdWfxOEG fGfu8we5SliqudIQ/SW2i0XwCAd5qkxsX7oM+wy1/CjCY5n3qc7kHX/+P QHiFq18moW4A6Et5nye6+iRXZLTwjlcGkvU64NGUg2a2M/bHguqmNxwSY A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AQBQA9TVNV/4kNJK1cgw+BMgbMZwKBOTsRAQEBAQEBAYEKhCEBAQQ6PxACAQg2EDIlAgQBDQWILMgoAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4s6hDpLB4QtAQSLOoRmgjaKcIElg2ORbiNhgVmBPW+BRYEBAQEB
X-IronPort-AV: E=Sophos;i="5.13,420,1427760000"; d="scan'208";a="149571761"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-7.cisco.com with ESMTP; 13 May 2015 13:11:04 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t4DDB4h4025155 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 May 2015 13:11:04 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.199]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Wed, 13 May 2015 08:11:04 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, The IESG <iesg@ietf.org>
Thread-Topic: Alvaro Retana's No Objection on draft-ietf-mmusic-rtsp-nat-evaluation-15: (with COMMENT)
Thread-Index: AQHQjPrqwX6xhVzjkEywIRX5vTnjW516F7yA///blAA=
Date: Wed, 13 May 2015 13:11:03 +0000
Message-ID: <D178BC33.AFEDA%aretana@cisco.com>
References: <20150512213044.30495.51553.idtracker@ietfa.amsl.com> <555333B1.6050607@ericsson.com>
In-Reply-To: <555333B1.6050607@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1E1B3A5661755B4AB80EADDD536B3F4D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/eq3XJiWhzj6SlcYFhQxZjeQU0mM>
X-Mailman-Approved-At: Wed, 13 May 2015 08:32:00 -0700
Cc: "draft-ietf-mmusic-rtsp-nat-evaluation.all@tools.ietf.org" <draft-ietf-mmusic-rtsp-nat-evaluation.all@tools.ietf.org>, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Alvaro Retana's No Objection on draft-ietf-mmusic-rtsp-nat-evaluation-15: (with COMMENT)
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: Wed, 13 May 2015 13:11:18 -0000

On 5/13/15, 7:21 AM, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
wrote:

Magnus:

Hi!

>>
>>
>>
>>2. Section 8 (Security Considerations) mentions the fact that "three way
>>latching as well as ICE mitigates these security issues and performs the
>>important return-routability check".  Please add a reference to this
>>important check.  I looked at RFC5245 (ICE), but could not find that
>>check described (just connectivity checks); is that what you're referring
>>to with a different name?
>>
>
>So the word return-routability check (really procedure) comes from
>mobile IPv6. The point of these checks is that each side does perform a
>check that I can send you a packet with a token, and you prove that you
>received it by echoing it back. Thus, preventing off-path attacks. In
>ICE this is done by the double sided connectivity checks.
>
>I suggest the following clarifications:
>
>
>In Section 4.3.6:
>    The ICE
>    connectivity checks with their random transaction IDs from the server
>    to the client servers as return-routability check and prevents off-
>    path attacker to succeed with address spoofing.  Similar to Mobile
>    IPV6's return routability procedure (Section 5.2.5 of [RFC3775]).

For ICE, I would suggest pointing at RFC5245.  A small nit on the text
(serves, not servers).

NEW>
  The ICE
  connectivity checks [RFC5245] with their random transaction IDs from the
server
  to the client serves as return-routability check and prevents off-
  path attacker to succeed with address spoofing.
<NEW



>
>
>
>In Section 4.6.5
>
>    The client to server nonce and its echoing back does not protect
>    against on-patch attacker, including malicious clients.  However, the
>    server to client nonce and its echoing back prevents malicious
>    clients to divert the media stream by spoofing the source address and
>    port, as it can't echo back the nonce in these cases.  Similar to
>    the Mobile IPv6 return routability procedure (Section 5.2.5 of
>    [RFC3775])
>
>This way, the term is known to the reader by the time they come to the
>summary in the end.

Looks good.

Thanks!

Alvaro.