
From nobody Sun Jan  4 11:36:04 2015
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A3191A8ABD; Sun,  4 Jan 2015 11:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 HV1llmnWK56b; Sun,  4 Jan 2015 11:35:57 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 365851A8ABC; Sun,  4 Jan 2015 11:35:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1420400156; d=isode.com; s=selector; i=@isode.com; bh=zC9N4hlw2wmyeH7JezAiGPPvICAaol5t4IF40c2h3p0=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=KAJ7ocBwaK5X47wdoPL6ZyTKZirvXK5O58YKGRpHI9/ofjKD8dWvDGqFMWbpBp0miUL2OT NZHvjmCYZb16HQ8AsjeTnq4A98PHrXfvqE7topK9Ft/wx2sGehp0yezJYBBeibb6JLSU1C tvyBf1XRn8RigiYWc/NYmmgyU3Orb1o=;
Received: from [192.168.0.5] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <VKmWGwAKaF=n@waldorf.isode.com>; Sun, 4 Jan 2015 19:35:55 +0000
Message-ID: <54A990F4.9040509@isode.com>
Date: Sun, 04 Jan 2015 19:13:56 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
To: ietf@ietf.org
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com>
In-Reply-To: <20141208235619.4442.37821.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/7VJzlB3zN0qxb99Hyk7V1yWp5YA
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jan 2015 19:35:59 -0000

On 08/12/2014 23:56, The IESG wrote:
> The IESG has received a request from the Transport Area Working Group WG
> (tsvwg) to consider the following document:
> - 'Recommendations for Transport Port Number Uses'
>    <draft-ietf-tsvwg-port-use-06.txt> as Best Current Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-12-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document provides recommendations to application and service
>     designers on how to use the transport protocol port number space. IT
>     complements (but does not update) RFC6335, which focuses on IANA
>     process.
My apologies for late review of the document. I generally think that the 
document is well written and is nearly done, but I have some 
comments/concerns.

1. Introduction

    This document provides information and advice to system designers on
    the use of transport port numbers. It provides a detailed historical
    background of the evolution of transport port numbers and their
    multiple meanings. It also provides specific recommendations to
    system designers on how to use assigned port numbers. Note that this
    document provides information to potential port number applicants
    that complements the IANA process described in BCP165 [RFC6335], but
    it does not update that document.

I am a bit confused by the status and purpose of this document. It is a 
BCP, but the introducting
says that it is purely informational. But then the document has lots of 
RFC 2119 language.
Is there any intent for this document
to be of use to port expert reviewers, for example if they want to point
out why a particular port registration request is rejected?


In 7.1:

          Additional port numbers are not intended to replicate an
          existing service. For example, if a device is configured to
          use a typical web browser then it the port number used for
          that service is a copy of the http service that is already
          assigned to port number 80 and does not warrant a new
          assignment. However, an automated system that happens to use
          HTTP framing - but cannot be accessed by a browser - might be

I have some concerns about "be access by a browser".

One particular case I have in mind is when a service expose some data 
using JSON or ASN.1 (for example a certificate revocation list is 
returned), but also allow a browser to view certificate in a nice form 
using HTML (e.g. for debugging or convenience). I don't think the 
ability to return HTML automatically disqualify this from being an 
independent service, because the whole functionality supported by the 
service can't be implemented just by use of returned HTML.

Inserting "solely" before "by a browser" would address my concern.

          a new service. A good way to tell is "can an unmodified client
          of the existing service interact with the proposed service"?
          If so, that service would be a copy of an existing service and
          would not merit a new assignment.

In 7.4:

    Note however that a new service might not be eligible for IANA
    assignment of both an insecure and a secure variant of the same
    service, and similarly IANA might be skeptical of an assignment for

I don't think use of wording like "IANA might be skeptical" is correct 
here, because IANA doesn't define policy on this. IETF does. So let's 
call things with right names and don't misuse "IANA" here.

    an insecure port number for a secure service. In both cases,
    security of the service is compromised by adding the insecure port
    number assignment.

Similarly (in the same section): "IANA currently permits ..."


From nobody Mon Jan  5 01:34:39 2015
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149BA1A212D for <tsvwg@ietfa.amsl.com>; Mon,  5 Jan 2015 01:34:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 DlueiJ5m9nWa for <tsvwg@ietfa.amsl.com>; Mon,  5 Jan 2015 01:34:35 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101311A1F20 for <tsvwg@ietf.org>; Mon,  5 Jan 2015 01:34:34 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id t059YUS1011198 for <tsvwg@ietf.org>; Mon, 5 Jan 2015 10:34:30 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
References: <20150105091803.11731.27646.idtracker@ietfa.amsl.com>
In-Reply-To: <20150105091803.11731.27646.idtracker@ietfa.amsl.com>
Date: Mon, 5 Jan 2015 10:34:34 +0100
Message-ID: <006301d028ca$d09b7c20$71d27460$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHtA2yvfsmzmRAAqG9sGIcLqpBDupx3ikqA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/UMvjexlhRi7D1Egl_cUSzR8sKtM
Subject: [tsvwg] RV: New Version Notification for draft-saldana-tsvwg-simplemux-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 09:34:38 -0000

Hi all.

I have just uploaded an updated version of the Simplemux draft.
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/

In this version, you can include the =E2=80=9CProtocol=E2=80=9D field on =
each separator. This permits the inclusion of packets belonging to =
different protocols into a single bundle.

I have also modified the meaning of the =E2=80=9CSingle Protocol =
Bit=E2=80=9D. Now it is 1 (not 0) when all the packets belong to the =
same protocol.


An implementation for Linux, using IP/UDP as the multiplexing protocol, =
and IP and ROHC as multiplexed protocols is available here:=20
https://github.com/TCM-TF/simplemux

Some performance tests developed with it are reported here:
https://github.com/TCM-TF/simplemux/blob/master/Simplemux_VoIP&Quake3_res=
ults_v1.pdf?raw=3Dtrue

- 10 VoIP flows (G729a with 2 samples per packet):
Average BW reduction: 36.50%
Average PPS reduction: 78.83%
Average additional delay: 4.123 ms

- 10 flows of Quake3 (a First Person Shooter online game)
Average BW reduction: 22.23%
Average PPS reduction: 92.99%
Average additional delay: 5.148 ms


Best regards and happy new year!

Jose

> -----Mensaje original-----
> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Enviado el: lunes, 05 de enero de 2015 10:18
> Para: Jose Saldana; Jose Saldana
> Asunto: New Version Notification for =
draft-saldana-tsvwg-simplemux-01.txt
>=20
>=20
> A new version of I-D, draft-saldana-tsvwg-simplemux-01.txt
> has been successfully submitted by Jose Saldana and posted to the IETF
> repository.
>=20
> Name:		draft-saldana-tsvwg-simplemux
> Revision:	01
> Title:		Simplemux. A generic multiplexing protocol
> Document date:	2015-01-05
> Group:		Individual Submission
> Pages:		11
> URL:            =
http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-simplemux-01.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/
> Htmlized:       =
http://tools.ietf.org/html/draft-saldana-tsvwg-simplemux-01
> Diff:           =
http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-simplemux-01
>=20
> Abstract:
>    There are some situations in which multiplexing a number of small
>    packets into a bigger one is desirable.  For example, a number of
>    small packets can be sent together between a pair of machines if =
they
>    share a common network path.  Thus, the traffic profile can be
>    shifted from small to larger packets, reducing the network overhead
>    and the number of packets per second to be managed by intermediate
>    routers.
>=20
>    This document describes Simplemux, a protocol able to encapsulate a
>    number of packets belonging to different protocols into a single
>    packet.  It includes the "Protocol" field on each multiplexing
>    header, thus allowing the inclusion of a number of packets =
belonging
>    to different protocols on a packet of another protocol.
>=20
>    The size of the multiplexing headers is kept very low (it may be a
>    single byte when multiplexing small packets) in order to reduce the
>    overhead.
>=20
>=20
>=20
>=20
> 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.
>=20
> The IETF Secretariat



From nobody Sun Jan 11 01:30:57 2015
Return-Path: <fluffy@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 876CC1A1A97 for <tsvwg@ietfa.amsl.com>; Fri,  9 Jan 2015 14:12:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.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, USER_IN_WHITELIST=-100] 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 jdmf4gsRN29P for <tsvwg@ietfa.amsl.com>; Fri,  9 Jan 2015 14:12:01 -0800 (PST)
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 1A8161A0039 for <tsvwg@ietf.org>; Fri,  9 Jan 2015 14:12:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=822; q=dns/txt; s=iport; t=1420841521; x=1422051121; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=sFUNVilgTsVrtRxT0Jjs0x8etx+5jHMibt1kdTqLaAQ=; b=RY0vwHKp38Ras9PUIoIUse3zDA8Ljo/Dab7uZ4cYkPnDAzjcbfQTb66k XjRu8bF0LYfGmHmFHnikuX9DrNK0U7pD/IP9DPXo7xrou5g8sEUDmpI77 BIeZ0BY2hXNX1AXoe+n6tuuA3tubp51qmZ0UUWF6q2pVJ/9Fc6NL1PV7v A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAItRsFStJV2Q/2dsb2JhbABcgmQigR8LBMt0AoEVQwEBAQEBfYQMAQEBAwF5BQsCAQgYLjIlAgQOBYgkCAHKXAEBAQEBAQEBAQEBAQEBAQEBAQEBARePRjMHgxaBEwEEjjiJC5F0IoNub4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,733,1413244800"; d="scan'208";a="111942871"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-7.cisco.com with ESMTP; 09 Jan 2015 22:12:01 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t09MC0EY023533 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Fri, 9 Jan 2015 22:12:00 GMT
Received: from xmb-aln-x02.cisco.com ([fe80::8c1c:7b85:56de:ffd1]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Fri, 9 Jan 2015 16:12:00 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Thread-Topic: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft
Thread-Index: AQHQLFlIxHraldlX1E6Vd7Vv5azW0Q==
Date: Fri, 9 Jan 2015 22:11:58 +0000
Message-ID: <953011D7-0D9C-41CA-B13D-A823A18A9CF0@cisco.com>
References: <4AAB478A-442A-4A01-84D5-2B21EE63C7D4@cisco.com> <696AF7FE-4E14-4825-8B81-0EC5FB752342@cisco.com>
In-Reply-To: <696AF7FE-4E14-4825-8B81-0EC5FB752342@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <7695CE189E292D4F8E2841919D370031@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/TegiYT5vJjJ0cAXEosS5gh0RF6I>
X-Mailman-Approved-At: Sun, 11 Jan 2015 01:30:50 -0800
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jan 2015 22:12:04 -0000

> On Jul 2, 2014, at 11:50 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>=20
> As an additional comment, reflecting on comments in other quarters (dart)=
, it may be worthwhile pointing out in the draft that the DSCP indicates a =
minimum acceptable service level; if a network thinks it can achieve that s=
ervice level within some larger scheme (such as a traffic class described i=
n Ruediger=92s draft, RFC 5127, or simply by oversupplying bandwidth), that=
 is at the operator=92s discretion.

Fred, I think that from the point of view of this draft, the DSCP don't rea=
lly indicate any minimum that the network needs to provide. The network can=
 totally ignore the DSCP value  and whatever it might do based on the DSCP =
is out of scope of this draft and handled in the RFC that defined the DSCP.





From nobody Sun Jan 11 23:09:23 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41F171A1AEA; Sun, 11 Jan 2015 23:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 adMf5Hjht0-t; Sun, 11 Jan 2015 23:09:18 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28BAB1A8A5A; Sun, 11 Jan 2015 23:09:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150112070918.21324.30720.idtracker@ietfa.amsl.com>
Date: Sun, 11 Jan 2015 23:09:18 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/VxvQgSpfqhE2cVQEIzIZz_uysBc>
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 07:09:21 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : Stream Schedulers and a New Data Chunk for the Stream Control Transmission Protocol
        Authors         : Randall R. Stewart
                          Michael Tuexen
                          Salvatore Loreto
                          Robin Seggelmann
	Filename        : draft-ietf-tsvwg-sctp-ndata-02.txt
	Pages           : 11
	Date            : 2015-01-11

Abstract:
   The Stream Control Transmission Protocol (SCTP) is a message oriented
   transport protocol supporting arbitrary large user messages.
   However, the sender can not interleave different user messages which
   causes head of line blocking at the sender side.  To overcome this
   limitation, this document adds a new data chunk to SCTP.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-ndata-02


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 Sun Jan 11 23:24:25 2015
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB031A8A5A for <tsvwg@ietfa.amsl.com>; Sun, 11 Jan 2015 23:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 uVMFbFDikkOu for <tsvwg@ietfa.amsl.com>; Sun, 11 Jan 2015 23:24:20 -0800 (PST)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E762B1A8A59 for <tsvwg@ietf.org>; Sun, 11 Jan 2015 23:24:18 -0800 (PST)
Received: from qdezc2.de.t-internal.com ([10.125.181.10]) by tcmail11.telekom.de with ESMTP; 12 Jan 2015 08:24:15 +0100
X-IronPort-AV: E=Sophos;i="5.07,742,1413237600"; d="scan'208";a="195632719"
Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES128-SHA; 12 Jan 2015 08:24:15 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by he110890 ([10.134.92.131]) with mapi; Mon, 12 Jan 2015 08:24:14 +0100
From: <Ruediger.Geib@telekom.de>
To: <fluffy@cisco.com>
Date: Mon, 12 Jan 2015 08:24:13 +0100
Thread-Topic: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft
Thread-Index: AQHQLFlIxHraldlX1E6Vd7Vv5azW0Zy8F/yQ
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F50439CBA292@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <4AAB478A-442A-4A01-84D5-2B21EE63C7D4@cisco.com> <696AF7FE-4E14-4825-8B81-0EC5FB752342@cisco.com> <953011D7-0D9C-41CA-B13D-A823A18A9CF0@cisco.com>
In-Reply-To: <953011D7-0D9C-41CA-B13D-A823A18A9CF0@cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/f3yj-jFUYh9r0_B0b1PPxLrsUkA>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 07:24:23 -0000

Cullen,

that includes a DSCP rewrite to default/0 (and forwarding in default PHB)?

Regards,

Ruediger

----Urspr=FCngliche Nachricht-----
Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Cullen Jennings (=
fluffy)
Gesendet: Freitag, 9. Januar 2015 23:12
An: Fred Baker (fred)
Cc: tsvwg@ietf.org
Betreff: Re: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft


> On Jul 2, 2014, at 11:50 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>=20
> As an additional comment, reflecting on comments in other quarters (dart)=
, it may be worthwhile pointing out in the draft that the DSCP indicates a =
minimum acceptable service level; if a network thinks it can achieve that s=
ervice level within some larger scheme (such as a traffic class described i=
n Ruediger's draft, RFC 5127, or simply by oversupplying bandwidth), that i=
s at the operator's discretion.

Fred, I think that from the point of view of this draft, the DSCP don't rea=
lly indicate any minimum that the network needs to provide. The network can=
 totally ignore the DSCP value  and whatever it might do based on the DSCP =
is out of scope of this draft and handled in the RFC that defined the DSCP.





From nobody Mon Jan 12 01:22:59 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8525C1A8A84 for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 01:22:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level: 
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] 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 Tpnzt1GIN778 for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 01:22:55 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 330E51A1B2E for <tsvwg@ietf.org>; Mon, 12 Jan 2015 01:22:55 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id E57CE1B00BD5; Mon, 12 Jan 2015 09:22:47 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 12 Jan 2015 09:22:47 -0000
Message-ID: <4e39e811a3ebd1ca99a59cb2d416c1ea.squirrel@erg.abdn.ac.uk>
In-Reply-To: <20150112070918.21324.30720.idtracker@ietfa.amsl.com>
References: <20150112070918.21324.30720.idtracker@ietfa.amsl.com>
Date: Mon, 12 Jan 2015 09:22:47 -0000
From: gorry@erg.abdn.ac.uk
To: draft-ietf-tsvwg-sctp-ndata@tools.ietf.org
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/OBoYMh80jR14ZMrctLYYjOErhWw>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 09:22:57 -0000

Thanks for uploading a new draft, however this draft does not resolve the
issues that were noted previously:

• Name change proposed at IETF-90, but needs WG consensus (Interleaved data?)

–  Address comments received on the mailing list.
• Describe Stream Schedulers
• Clarification of use-case.
• Make clear what also applies when regular DATA chunks are used.

Last IETF it was suggested this would be ready for the IETF meeting in
March... Can you please propose text to address these issues on the list
asap, especially the name change?

Gorry

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Transport Area Working Group Working
> Group of the IETF.
>
>         Title           : Stream Schedulers and a New Data Chunk for the
> Stream Control Transmission Protocol
>         Authors         : Randall R. Stewart
>                           Michael Tuexen
>                           Salvatore Loreto
>                           Robin Seggelmann
> 	Filename        : draft-ietf-tsvwg-sctp-ndata-02.txt
> 	Pages           : 11
> 	Date            : 2015-01-11
>
> Abstract:
>    The Stream Control Transmission Protocol (SCTP) is a message oriented
>    transport protocol supporting arbitrary large user messages.
>    However, the sender can not interleave different user messages which
>    causes head of line blocking at the sender side.  To overcome this
>    limitation, this document adds a new data chunk to SCTP.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-02
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-ndata-02
>
>
> 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 rick.bellingar@reedelsevier.com  Sun Jan 11 09:01:51 2015
Return-Path: <rick.bellingar@reedelsevier.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E38331A70FD for <tsvwg@ietfa.amsl.com>; Sun, 11 Jan 2015 09:01:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level: 
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] 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 KXrW5u0yq4Rk for <tsvwg@ietfa.amsl.com>; Sun, 11 Jan 2015 09:01:49 -0800 (PST)
Received: from p02c12o145.mxlogic.net (p02c12o145.mxlogic.net [208.65.145.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E9AA1A7034 for <tsvwg@ietf.org>; Sun, 11 Jan 2015 09:01:49 -0800 (PST)
Received: from unknown [198.185.18.10] (EHLO retdayedgp002.reedelsevier.com) by p02c12o145.mxlogic.net(mxl_mta-8.2.0-3) with ESMTP id d7ca2b45.2b6b7ae2a940.55707.00-539.135824.p02c12o145.mxlogic.net (envelope-from <rick.bellingar@reedelsevier.com>);  Sun, 11 Jan 2015 10:01:49 -0700 (MST)
X-MXL-Hash: 54b2ac7d766135cf-127d717ed564d599bbb2571d9b5c2fe3434a1ddd
Received: from unknown [198.185.18.10] (EHLO retdayedgp002.reedelsevier.com) by p02c12o145.mxlogic.net(mxl_mta-8.2.0-3) over TLS secured channel with ESMTP id f5ca2b45.0.55642.00-376.135632.p02c12o145.mxlogic.net (envelope-from <rick.bellingar@reedelsevier.com>);  Sun, 11 Jan 2015 10:01:41 -0700 (MST)
X-MXL-Hash: 54b2ac756541b3f6-a74a995ece1eb063fc63da286126610cceb51024
Received: from RETDAYHUBP001.legal.regn.net (138.12.19.108) by retdayedgp002.reedelsevier.com (192.168.37.40) with Microsoft SMTP Server (TLS) id 14.3.181.6; Sun, 11 Jan 2015 12:00:42 -0500
Received: from retdayedgp001.reedelsevier.com (192.168.37.39) by RETDAYHUBP001.legal.regn.net (138.12.19.108) with Microsoft SMTP Server (TLS) id 14.3.123.3; Sun, 11 Jan 2015 12:01:16 -0500
Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.236) by retuso365smtp.reedelsevier.com (192.168.37.39) with Microsoft SMTP Server (TLS) id 14.3.181.6; Sun, 11 Jan 2015 12:01:06 -0500
Received: from BLUPR0801MB546.namprd08.prod.outlook.com (10.141.252.24) by BLUPR0801MB546.namprd08.prod.outlook.com (10.141.252.24) with Microsoft SMTP Server (TLS) id 15.1.53.17; Sun, 11 Jan 2015 17:01:14 +0000
Received: from BLUPR0801MB546.namprd08.prod.outlook.com ([10.141.252.24]) by BLUPR0801MB546.namprd08.prod.outlook.com ([10.141.252.24]) with mapi id 15.01.0053.000; Sun, 11 Jan 2015 17:01:14 +0000
From: "Bellingar, Richard J. (RET-DAY)" <Rick.Bellingar@reedelsevier.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "iana-questions@iana.org" <iana-questions@iana.org>
Thread-Topic: [IANA #800143] Port squatting
Thread-Index: AdAcChI6gE9sZ285QqiQjXL4eZYuzQOkcYGAAMix7dA=
Date: Sun, 11 Jan 2015 17:01:13 +0000
Message-ID: <BLUPR0801MB546416E2A87A6A4D243E765FD420@BLUPR0801MB546.namprd08.prod.outlook.com>
References: <RT-Ticket-800143@icann.org> <BLUPR0801MB54648E91525B7BFC05BE3C7FD680@BLUPR0801MB546.namprd08.prod.outlook.com> <rt-4.0.8-22959-1420650203-1117.800143-6-0@icann.org>
In-Reply-To: <rt-4.0.8-22959-1420650203-1117.800143-6-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [198.185.18.72]
x-dmarcaction-test: None
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(3005003);SRVR:BLUPR0801MB546;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BLUPR0801MB546;
x-forefront-prvs: 045315E1EE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(13464003)(377454003)(39064003)(189002)(24454002)(107886001)(122556002)(15975445007)(19580395003)(40100003)(106356001)(102836002)(33656002)(54206007)(2950100001)(77156002)(19580405001)(99286002)(66066001)(97736003)(76176999)(2501002)(54606007)(77096005)(54356999)(74316001)(2900100001)(76576001)(105586002)(87936001)(2656002)(64706001)(50986999)(68736005)(46102003)(86362001)(101416001)(92566002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0801MB546; H:BLUPR0801MB546.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: reedelsevier.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jan 2015 17:01:13.6645 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9274ee3f-9425-4109-a27f-9fb15c10675d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0801MB546
X-OrganizationHeadersPreserved: BLUPR0801MB546.namprd08.prod.outlook.com
X-CrossPremisesHeadersPromoted: retdayedgp001.reedelsevier.com
X-CrossPremisesHeadersFiltered: retdayedgp001.reedelsevier.com
X-OriginatorOrg: reedelsevier.com
X-AnalysisOut: [v=2.1 cv=JOQvsq6b c=1 sm=1 tr=0 a=VagdEOcV0bQO4x+H6ZmC5A==]
X-AnalysisOut: [:117 a=VagdEOcV0bQO4x+H6ZmC5A==:17 a=sEHMLM1fE0YA:10 a=46N]
X-AnalysisOut: [Al10togAA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:10 a=k3ev2J5]
X-AnalysisOut: [7AAAA:8 a=UqCG9HQmAAAA:8 a=YlVTAMxIAAAA:8 a=gRkuwbbrAAAA:8]
X-AnalysisOut: [ a=YNv0rlydsVwA:10 a=I0CVDw5ZAAAA:8 a=48vgC7mUAAAA:8 a=A0J]
X-AnalysisOut: [dtTlwXusdgrOhGh4A:9 a=QEXdDO2ut3YA:10 a=OB46QkFbDjsA:10 a=]
X-AnalysisOut: [vbnqrMM_esoA:10]
X-Spam: [F=0.5000000000; CM=0.500; MH=0.500(2015011105); S=0.200(2014051901)]
X-MAIL-FROM: <rick.bellingar@reedelsevier.com>
X-SOURCE-IP: [198.185.18.10]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/a8BTXt0_Ja_iY2I2oJk0y8l6YGQ>
X-Mailman-Approved-At: Mon, 12 Jan 2015 01:23:55 -0800
Subject: [tsvwg] FW: [IANA #800143] Port squatting
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jan 2015 17:04:42 -0000

SSByZWFsbHkgZG9uJ3QgdW5kZXJzdGFuZCBQZWFybCdzIGFuc3dlciAoYmVsb3cpLiBBdCBvbmUg
dGltZSwgSSBmb3VuZCBhIG1lYW5zIChhbiBlbWFpbCBhZGRyZXNzLCBJIHRoaW5rKSB0byByZXBv
cnQgY29tcGFuaWVzL2FwcGxpY2F0aW9ucyB0aGF0IHdlcmUgdXNpbmcgcG9ydHMgaW4gdGhlIFN5
c3RlbSAmIFJlZ2lzdGVyZWQgcmFuZ2VzIHRoYXQgd2VyZSBub3QgcmVzZXJ2ZWQgb3Igd2VyZSBy
ZXNlcnZlZCBieSBvdGhlciBjb21wYW5pZXMvYXBwcy4gVGhvc2UgdGhlbiwgcHJlc3VtYWJseSwg
d2VyZSBhZGRlZCB0byB0aGUgSUFOQSBkYXRhYmFzZSBhbmQgZGVwaWN0ZWQgaW4gdGhlICJLbm93
biBVbmF1dGhvcml6ZWQgVXNlcyIgY29sdW1uIG9mIGh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdu
bWVudHMvc2VydmljZS1uYW1lcy1wb3J0LW51bWJlcnMvc2VydmljZS1uYW1lcy1wb3J0LW51bWJl
cnMueGh0bWwgLiBIYXMgdGhhdCBwcmFjdGljZSBjZWFzZWQ/DQoNCi0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQpGcm9tOiBQZWFybCBMaWFuZyB2aWEgUlQgW21haWx0bzppYW5hLXF1ZXN0aW9u
c0BpYW5hLm9yZ10gDQpTZW50OiBXZWRuZXNkYXksIEphbnVhcnkgMDcsIDIwMTUgMTI6MDMgUE0N
ClRvOiBCZWxsaW5nYXIsIFJpY2hhcmQgSi4gKFJFVC1EQVkpDQpTdWJqZWN0OiBbSUFOQSAjODAw
MTQzXSBQb3J0IHNxdWF0dGluZw0KDQpIZWxsbywNCg0KVGhhbmsgeW91IGZvciBjb250YWN0aW5n
IHVzLg0KDQpPbiBTYXQgRGVjIDIwIDA0OjA1OjQ2IDIwMTQsIFJpY2suQmVsbGluZ2FyQHJlZWRl
bHNldmllci5jb20gd3JvdGU6DQo+IElzIHRoZXJlIHN0aWxsIGEgbWVhbnMgdG8gcmVwb3J0IHBv
cnQgc3F1YXR0aW5nPyBJIGZvdW5kIG9uZSBpbiB0aGUgDQo+IHBhc3QsIGJ1dCBjYW4ndCBmaW5k
IG9uZSBub3cuDQo+IA0KDQpGaXJzdCBvZiBhbGwsIHdlIGRvIG5vdCBtb25pdG9yIGFueSB0cmFm
ZmljIGZsb3dpbmcgdG8gb3IgZnJvbSBhbnkgYW5kIGFsbCBwb3J0IG51bWJlcnMsIHNwZWNpZmlj
YWxseSB1bmFzc2lnbmVkIHBvcnQgbnVtYmVycyAoMC00OTE1MS4pICBOb3IgZG8gd2UgaGF2ZSBr
bm93bGVkZ2Ugb2YgdHJhZmZpYyB0byBhbnkgcG9ydCBudW1iZXJzIDAtNDkxNTEuICBXZSBzb3Vn
aHQgc29tZSBhZHZpY2VzIGZyb20gdGhlIElFU0cgZGVzaWduYXRlZCBwb3J0IGV4cGVydCB3aG8g
aW5kaWNhdGVkIHRoYXQgd2UgKElFVEYpIGFyZSBub3QgcmVndWxhdGluZyB0aGUgcG9ydCB0cmFm
ZmljLg0KDQpZb3UgbWF5IGNvbnRhY3QgdGhlIElFVEYgVHJhbnNwb3J0IEFyZWEgV29ya2luZyBH
cm91cCBhdCB0c3Z3Z0BpZXRmLm9yZyBpZiB5b3UgcHJlZmVyLiAgDQoNClRoYW5rIHlvdSwNCg0K
UGVhcmwgTGlhbmcNCklDQU5ODQoNCg0K


From nobody Mon Jan 12 02:34:25 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F7E1A8AAE for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 02:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 k_5Emx17adkC for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 02:34:21 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7EDA1A8AAB for <tsvwg@ietf.org>; Mon, 12 Jan 2015 02:34:20 -0800 (PST)
Received: from [10.0.1.108] (unknown [212.201.121.94]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id AC2E61C10465E; Mon, 12 Jan 2015 11:34:17 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <tuexen@fh-muenster.de>
X-Priority: 3 (Normal)
In-Reply-To: <4e39e811a3ebd1ca99a59cb2d416c1ea.squirrel@erg.abdn.ac.uk>
Date: Mon, 12 Jan 2015 11:34:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB4E9CA8-B525-4D71-A0A1-DD655B997CA9@fh-muenster.de>
References: <20150112070918.21324.30720.idtracker@ietfa.amsl.com> <4e39e811a3ebd1ca99a59cb2d416c1ea.squirrel@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/E2S6CICEjKC3Vn86HUa5CTyxLfg>
Cc: draft-ietf-tsvwg-sctp-ndata@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 10:34:23 -0000

On 12 Jan 2015, at 10:22, gorry@erg.abdn.ac.uk wrote:
>=20
> Thanks for uploading a new draft, however this draft does not resolve =
the
> issues that were noted previously:
>=20
> =95 Name change proposed at IETF-90, but needs WG consensus =
(Interleaved data?)
>=20
> =96  Address comments received on the mailing list.
> =95 Describe Stream Schedulers
> =95 Clarification of use-case.
> =95 Make clear what also applies when regular DATA chunks are used.
>=20
> Last IETF it was suggested this would be ready for the IETF meeting in
> March... Can you please propose text to address these issues on the =
list
> asap, especially the name change?
Hi Gorry,

that is what I wanted to address before the submission, but didn't. I =
just
submitted it to have it alive again...

Best regards
Michael
>=20
> Gorry
>=20
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Transport Area Working Group Working
>> Group of the IETF.
>>=20
>>        Title           : Stream Schedulers and a New Data Chunk for =
the
>> Stream Control Transmission Protocol
>>        Authors         : Randall R. Stewart
>>                          Michael Tuexen
>>                          Salvatore Loreto
>>                          Robin Seggelmann
>> 	Filename        : draft-ietf-tsvwg-sctp-ndata-02.txt
>> 	Pages           : 11
>> 	Date            : 2015-01-11
>>=20
>> Abstract:
>>   The Stream Control Transmission Protocol (SCTP) is a message =
oriented
>>   transport protocol supporting arbitrary large user messages.
>>   However, the sender can not interleave different user messages =
which
>>   causes head of line blocking at the sender side.  To overcome this
>>   limitation, this document adds a new data chunk to SCTP.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>>=20
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-02
>>=20
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-ndata-02
>>=20
>>=20
>> 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.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>=20
>=20


From nobody Mon Jan 12 03:21:02 2015
Return-Path: <lars@netapp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72DDD1A8AE5 for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 03:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ia-FDOd-9J5O for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 03:20:58 -0800 (PST)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82E8E1A8ADF for <tsvwg@ietf.org>; Mon, 12 Jan 2015 03:20:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.07,743,1413270000";  d="asc'?scan'208";a="11124824"
Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx141-out.netapp.com with ESMTP; 12 Jan 2015 03:15:43 -0800
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.995.29; Mon, 12 Jan 2015 03:15:42 -0800
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::d8c:be2b:9e16:f915%21]) with mapi id 15.00.0995.031; Mon, 12 Jan 2015 03:15:42 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "Bellingar, Richard J. (RET-DAY)" <Rick.Bellingar@reedelsevier.com>
Thread-Topic: [tsvwg] [IANA #800143] Port squatting
Thread-Index: AdAcChI6gE9sZ285QqiQjXL4eZYuzQOkcYGAAMix7dAAN2HLAA==
Date: Mon, 12 Jan 2015 11:15:42 +0000
Message-ID: <38DA8A39-15B1-4E76-9265-24547E5CEBE3@netapp.com>
References: <RT-Ticket-800143@icann.org> <BLUPR0801MB54648E91525B7BFC05BE3C7FD680@BLUPR0801MB546.namprd08.prod.outlook.com> <rt-4.0.8-22959-1420650203-1117.800143-6-0@icann.org> <BLUPR0801MB546416E2A87A6A4D243E765FD420@BLUPR0801MB546.namprd08.prod.outlook.com>
In-Reply-To: <BLUPR0801MB546416E2A87A6A4D243E765FD420@BLUPR0801MB546.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.1993)
x-originating-ip: [10.122.56.79]
Content-Type: multipart/signed; boundary="Apple-Mail=_D5A24223-CA10-4813-8DA2-D1C7C9623743"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/pK9iM1nAT1PHIpUG5tZUuez2mic>
Cc: "iana-questions@iana.org" <iana-questions@iana.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] [IANA #800143] Port squatting
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 11:21:00 -0000

--Apple-Mail=_D5A24223-CA10-4813-8DA2-D1C7C9623743
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2015-1-11, at 18:01, Bellingar, Richard J. (RET-DAY) =
<Rick.Bellingar@reedelsevier.com> wrote:
>=20
> I really don't understand Pearl's answer (below). At one time, I found =
a means (an email address, I think) to report companies/applications =
that were using ports in the System & Registered ranges that were not =
reserved or were reserved by other companies/apps. Those then, =
presumably, were added to the IANA database and depicted in the "Known =
Unauthorized Uses" column of =
http://www.iana.org/assignments/service-names-port-numbers/service-names-p=
ort-numbers.xhtml . Has that practice ceased?

no, but it involves the IETF and the area director. So raising it on =
this list is the right thing to do, and then Martin and Spencer can =
instruct IANA via the IESG as needed.

Lars

>=20
> -----Original Message-----
> From: Pearl Liang via RT [mailto:iana-questions@iana.org]
> Sent: Wednesday, January 07, 2015 12:03 PM
> To: Bellingar, Richard J. (RET-DAY)
> Subject: [IANA #800143] Port squatting
>=20
> Hello,
>=20
> Thank you for contacting us.
>=20
> On Sat Dec 20 04:05:46 2014, Rick.Bellingar@reedelsevier.com wrote:
>> Is there still a means to report port squatting? I found one in the
>> past, but can't find one now.
>>=20
>=20
> First of all, we do not monitor any traffic flowing to or from any and =
all port numbers, specifically unassigned port numbers (0-49151.)  Nor =
do we have knowledge of traffic to any port numbers 0-49151.  We sought =
some advices from the IESG designated port expert who indicated that we =
(IETF) are not regulating the port traffic.
>=20
> You may contact the IETF Transport Area Working Group at =
tsvwg@ietf.org if you prefer.
>=20
> Thank you,
>=20
> Pearl Liang
> ICANN
>=20
>=20


--Apple-Mail=_D5A24223-CA10-4813-8DA2-D1C7C9623743
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBVLOs3NZcnpRveo1xAQI75AP/SGF8G4mt+/dW2WUHMMsgFjNHmrvJCoZ2
z3B8qLv+3LmsTvKdVeOFgACA0R/H9Ji/EbniGXWfH9o7bNR536tZZrQq4F10bwVL
CCe5sKEu/kCbl6GOeQmi6LbZwv1EnwKKDesCDx2mh1HTZK9aJukB7DuR+UuqfAYN
FoLbUzKmo1A=
=hS3H
-----END PGP SIGNATURE-----

--Apple-Mail=_D5A24223-CA10-4813-8DA2-D1C7C9623743--


From nobody Mon Jan 12 09:47:05 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA74D1AC3F6 for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 09:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 zy4pwAuBxwkT for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 09:47:01 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 147BB1AC3A9 for <tsvwg@ietf.org>; Mon, 12 Jan 2015 09:47:01 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 6CF341B00BFA; Mon, 12 Jan 2015 17:46:56 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 12 Jan 2015 17:46:55 -0000
Message-ID: <0650cdffedf63ea0ec66373dfbd449d0.squirrel@erg.abdn.ac.uk>
In-Reply-To: <1F0BEF14-720E-46D0-8EC7-80F79EB63EE8@fh-muenster.de>
References: <8C559303-B26F-41D7-8063-C3FC268E02B0@fh-muenster.de> <6946e413159a3427a0c344a577cdf653.squirrel@erg.abdn.ac.uk> <F1E96F4E-7E2E-4273-8D23-037B868C6F17@fh-muenster.de> <5358c9c78e6ad57ac44b558858b1ae42.squirrel@erg.abdn.ac.uk> <1F0BEF14-720E-46D0-8EC7-80F79EB63EE8@fh-muenster.de>
Date: Mon, 12 Jan 2015 17:46:55 -0000
From: gorry@erg.abdn.ac.uk
To: "Michael Tuexen" <tuexen@fh-muenster.de>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/tYh6ZVNNpYP1Xusb7n7SvPryLEs>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-sctp-dtls-encaps-08.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 17:47:03 -0000

It looks like we are getting towards a point where it would be useful to
issue a new draft, so with this in mind I have a few comments (no Chair's
hat yet), so please feel free to comment on these comments...


I think the abstract  could benefit from a little explanation of the need
for DTLS encapsulation, given RFC 6951, and  RTCweb wishes to use UDP with
security. That's implied right now, and I think should be explicit.

I'd really encourage you to add this diagram to the intro, this wouldn't
hurt, and it makes it obvious!

 "
                               +----------+
                               |   SCTP   |
                               +----------+
                               |   DTLS   |
                               +----------+
                               | ICE/UDP  |
                               +----------+

                       Figure 1: Basic stack diagram"

And suggest you follow with something like:

   This encapsulation of SCTP over DTLS over UDP or ICE/UDP (see [RFC5245])
   can provide a NAT traversal solution together with confidentiality,
   source authentication, and integrity protected transfers. "

 This new text:
 "In case of a window based congestion..."
 Maybe would be clearer as:
 "The window-based congestion control method specified in [RFC4960],
 resets the congestion window and slow start threshold to their initial
 values."

 In 6.2, is it perhaps clearer to say exactly what is done, to help the DTLS
 reader understand e.g.
 "and can be used to send probe packets (HEARTBEAT chunks
 bundled with PADDING chunks [RFC4960])."

 I think it would be useful to also mention: "Path MTU discovery
 is required by SCTP when SCTP over DTLS is used
 for data channels (section 4 of draft-ietf-rtcweb-data-channel-13]."

Best wishes,

Gorry


From nobody Tue Jan 13 01:08:49 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 352BD1A8A39 for <tsvwg@ietfa.amsl.com>; Tue, 13 Jan 2015 01:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level: 
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] 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 f_89hGBBorlZ for <tsvwg@ietfa.amsl.com>; Tue, 13 Jan 2015 01:08:43 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 42B251A8A45 for <tsvwg@ietf.org>; Tue, 13 Jan 2015 01:08:43 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 22D641B00BD5; Tue, 13 Jan 2015 09:08:36 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Tue, 13 Jan 2015 09:08:35 -0000
Message-ID: <902c762b6bdcf30f39515ca7262a097a.squirrel@erg.abdn.ac.uk>
In-Reply-To: <20150113085618.32459.57156.idtracker@ietfa.amsl.com>
References: <20150113085618.32459.57156.idtracker@ietfa.amsl.com>
Date: Tue, 13 Jan 2015 09:08:35 -0000
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/G69gcuFzdLN6w2wFX9jeVCMDfSk>
Subject: Re: [tsvwg] New Version Notification for draft-ietf-aqm-recommendation-09.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2015 09:08:46 -0000

Following feedback during LC , and a discussion following the GEN-ART
review, we have prepared a new revision of the document.

This version does not include specific discussion of the issues, pitfalls
or need to analyse paths with multiple AQM (possibly different)
controllers operating in series. If people think there are important
topics here we'd encourage this discussion on this list (and could perhaps
even provide input to the evaluation criteria for AQM algorithms?
Thoughts?

If you submitted comments, please check these have been resolved and send
any comments/corrections to the tsvwg list.

Gorry & Fred.

>
> A new version of I-D, draft-ietf-aqm-recommendation-09.txt
> has been successfully submitted by Godred Fairhurst and posted to the
> IETF repository.
>
> Name:		draft-ietf-aqm-recommendation
> Revision:	09
> Title:		IETF Recommendations Regarding Active Queue Management
> Document date:	2015-01-13
> Group:		aqm
> Pages:		29
> URL:
> http://www.ietf.org/internet-drafts/draft-ietf-aqm-recommendation-09.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
> Htmlized:
> http://tools.ietf.org/html/draft-ietf-aqm-recommendation-09
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-09
>
> Abstract:
>    This memo presents recommendations to the Internet community
>    concerning measures to improve and preserve Internet performance.  It
>    presents a strong recommendation for testing, standardization, and
>    widespread deployment of active queue management (AQM) in network
>    devices, to improve the performance of today's Internet.  It also
>    urges a concerted effort of research, measurement, and ultimate
>    deployment of AQM mechanisms to protect the Internet from flows that
>    are not sufficiently responsive to congestion notification.
>
>    The note largely repeats the recommendations of RFC 2309, and
>    replaces these after fifteen years of experience and new research.
>
>
>
>
> 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.
>
> The IETF Secretariat
>



From nobody Wed Jan 14 03:34:34 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 251B01B2C6D for <tsvwg@ietfa.amsl.com>; Wed, 14 Jan 2015 03:34:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 3qt9RjQhYIpJ for <tsvwg@ietfa.amsl.com>; Wed, 14 Jan 2015 03:34:32 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F34B71B2C7D for <tsvwg@ietf.org>; Wed, 14 Jan 2015 03:33:27 -0800 (PST)
Received: from [192.168.1.200] (p508F2A85.dip0.t-ipconnect.de [80.143.42.133]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id B8AE71C10437A; Wed, 14 Jan 2015 12:33:25 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <tuexen@fh-muenster.de>
X-Priority: 3 (Normal)
In-Reply-To: <0650cdffedf63ea0ec66373dfbd449d0.squirrel@erg.abdn.ac.uk>
Date: Wed, 14 Jan 2015 12:33:24 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <B4331CE7-F7CB-4BE4-8EF4-E346867106B7@fh-muenster.de>
References: <8C559303-B26F-41D7-8063-C3FC268E02B0@fh-muenster.de> <6946e413159a3427a0c344a577cdf653.squirrel@erg.abdn.ac.uk> <F1E96F4E-7E2E-4273-8D23-037B868C6F17@fh-muenster.de> <5358c9c78e6ad57ac44b558858b1ae42.squirrel@erg.abdn.ac.uk> <1F0BEF14-720E-46D0-8EC7-80F79EB63EE8@fh-muenster.de> <0650cdffedf63ea0ec66373dfbd449d0.squirrel@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/hGfwzw2BdQ3iITrbqI_d2QQ3G1s>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-sctp-dtls-encaps-08.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 11:34:34 -0000

On 12 Jan 2015, at 18:46, gorry@erg.abdn.ac.uk wrote:
> 
> It looks like we are getting towards a point where it would be useful to
> issue a new draft, so with this in mind I have a few comments (no Chair's
> hat yet), so please feel free to comment on these comments...
Hi Gorry,

thank you very much for your review. See my comments in-line.

Best regards
Michael
> 
> 
> I think the abstract  could benefit from a little explanation of the need
> for DTLS encapsulation, given RFC 6951, and  RTCweb wishes to use UDP with
> security. That's implied right now, and I think should be explicit.
> 
> I'd really encourage you to add this diagram to the intro, this wouldn't
> hurt, and it makes it obvious!
> 
> "
>                               +----------+
>                               |   SCTP   |
>                               +----------+
>                               |   DTLS   |
>                               +----------+
>                               | ICE/UDP  |
>                               +----------+
> 
>                       Figure 1: Basic stack diagram"
> 
> And suggest you follow with something like:
> 
>   This encapsulation of SCTP over DTLS over UDP or ICE/UDP (see [RFC5245])
>   can provide a NAT traversal solution together with confidentiality,
>   source authentication, and integrity protected transfers. "
Just the be clear:
Do you want to to add some clarifying text to the abstract and the stack
diagram followed up by the sentence added to the overview? There is no
section called intro...
> 
> This new text:
> "In case of a window based congestion..."
> Maybe would be clearer as:
> "The window-based congestion control method specified in [RFC4960],
> resets the congestion window and slow start threshold to their initial
> values."
OK. Taken.
> 
> In 6.2, is it perhaps clearer to say exactly what is done, to help the DTLS
> reader understand e.g.
> "and can be used to send probe packets (HEARTBEAT chunks
> bundled with PADDING chunks [RFC4960])."
What about:
<t>When the SCTP layer performs path MTU discovery as specified in
<xref target='RFC4821'/>, the padding extension defined in
<xref target='RFC4820'/> MUST be supported and used for probe packets
(HEARTBEAT chunks bundled with PADDING chunks <xref target='RFC4820'/>).</t>

Please note that I don't use "can be used" and that I changed the reference
the RFC 4820, since I don't know why you are referring to RFC 4960.
> 
> I think it would be useful to also mention: "Path MTU discovery
> is required by SCTP when SCTP over DTLS is used
> for data channels (section 4 of draft-ietf-rtcweb-data-channel-13]."
I added to section 6.2:
<t>Path MTU discovery is required by SCTP when SCTP over DTLS is used
for data channels
(see Section 4 of <xref target='I-D.ietf-rtcweb-data-channel'/>).</t>
Not sure this is the best place. I think a better place would be to add
this at the end of Section 4. OK?
> 
> Best wishes,
> 
> Gorry
> 
> 


From nobody Wed Jan 14 03:57:47 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A0631B2C72 for <tsvwg@ietfa.amsl.com>; Wed, 14 Jan 2015 03:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level: 
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] 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 WLrGFKQs03O6 for <tsvwg@ietfa.amsl.com>; Wed, 14 Jan 2015 03:57:43 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 003BA1B2C71 for <tsvwg@ietf.org>; Wed, 14 Jan 2015 03:57:42 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 618A61B0053A; Wed, 14 Jan 2015 11:57:38 +0000 (GMT)
Received: from 64.208.49.5 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Wed, 14 Jan 2015 11:57:37 -0000
Message-ID: <ec85e5c90df22010c40ad6cc21e1c2a0.squirrel@erg.abdn.ac.uk>
In-Reply-To: <B4331CE7-F7CB-4BE4-8EF4-E346867106B7@fh-muenster.de>
References: <8C559303-B26F-41D7-8063-C3FC268E02B0@fh-muenster.de> <6946e413159a3427a0c344a577cdf653.squirrel@erg.abdn.ac.uk> <F1E96F4E-7E2E-4273-8D23-037B868C6F17@fh-muenster.de> <5358c9c78e6ad57ac44b558858b1ae42.squirrel@erg.abdn.ac.uk> <1F0BEF14-720E-46D0-8EC7-80F79EB63EE8@fh-muenster.de> <0650cdffedf63ea0ec66373dfbd449d0.squirrel@erg.abdn.ac.uk> <B4331CE7-F7CB-4BE4-8EF4-E346867106B7@fh-muenster.de>
Date: Wed, 14 Jan 2015 11:57:37 -0000
From: gorry@erg.abdn.ac.uk
To: "Michael Tuexen" <tuexen@fh-muenster.de>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/poCPLULIwIeZXpyKJK3JQ3jQ5Zc>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-sctp-dtls-encaps-08.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 11:57:45 -0000

Please see comments in line.

> On 12 Jan 2015, at 18:46, gorry@erg.abdn.ac.uk wrote:
>>
>> It looks like we are getting towards a point where it would be useful to
>> issue a new draft, so with this in mind I have a few comments (no
>> Chair's
>> hat yet), so please feel free to comment on these comments...
> Hi Gorry,
>
> thank you very much for your review. See my comments in-line.
>
> Best regards
> Michael
>>
>>
>> I think the abstract  could benefit from a little explanation of the
>> need
>> for DTLS encapsulation, given RFC 6951, and  RTCweb wishes to use UDP
>> with
>> security. That's implied right now, and I think should be explicit.
>>
>> I'd really encourage you to add this diagram to the intro, this wouldn't
>> hurt, and it makes it obvious!
>>
>> "
>>                               +----------+
>>                               |   SCTP   |
>>                               +----------+
>>                               |   DTLS   |
>>                               +----------+
>>                               | ICE/UDP  |
>>                               +----------+
>>
>>                       Figure 1: Basic stack diagram"
>>
>> And suggest you follow with something like:
>>
>>   This encapsulation of SCTP over DTLS over UDP or ICE/UDP (see
>> [RFC5245])
>>   can provide a NAT traversal solution together with confidentiality,
>>   source authentication, and integrity protected transfers. "
>
> Just the be clear:
> Do you want to to add some clarifying text to the abstract and the stack
> diagram followed up by the sentence added to the overview? There is no
> section called intro...
>
The first section would be fine.

>> This new text:
>> "In case of a window based congestion..."
>> Maybe would be clearer as:
>> "The window-based congestion control method specified in [RFC4960],
>> resets the congestion window and slow start threshold to their initial
>> values."
> OK. Taken.
>>
>> In 6.2, is it perhaps clearer to say exactly what is done, to help the
>> DTLS
>> reader understand e.g.
>> "and can be used to send probe packets (HEARTBEAT chunks
>> bundled with PADDING chunks [RFC4960])."
> What about:
> <t>When the SCTP layer performs path MTU discovery as specified in
> <xref target='RFC4821'/>, the padding extension defined in
> <xref target='RFC4820'/> MUST be supported and used for probe packets
> (HEARTBEAT chunks bundled with PADDING chunks <xref
> target='RFC4820'/>).</t>
>
> Please note that I don't use "can be used" and that I changed the
> reference
> the RFC 4820, since I don't know why you are referring to RFC 4960.
>
The new text sounds good.

>>
>> I think it would be useful to also mention: "Path MTU discovery
>> is required by SCTP when SCTP over DTLS is used
>> for data channels (section 4 of draft-ietf-rtcweb-data-channel-13]."
> I added to section 6.2:
> <t>Path MTU discovery is required by SCTP when SCTP over DTLS is used
> for data channels
> (see Section 4 of <xref target='I-D.ietf-rtcweb-data-channel'/>).</t>
>
> Not sure this is the best place. I think a better place would be to add
> this at the end of Section 4. OK?
>
This looks good.

>>
>> Best wishes,
>>
>> Gorry
>>
>

Gorry


From nobody Wed Jan 14 08:56:37 2015
Return-Path: <fluffy@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED181ACD1A for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 09:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.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, USER_IN_WHITELIST=-100] 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 cfyCIVGfQFP5 for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 09:22:05 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A4661ACD0B for <tsvwg@ietf.org>; Mon, 12 Jan 2015 09:22:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1493; q=dns/txt; s=iport; t=1421083325; x=1422292925; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=b+paXEclzWkE8+1YrpLEQ93F4+vPm4OgM0f+CnFz7wk=; b=JTKVEzat9u51Y/n68Tk4mCRwCGZTV4PukVmocoB91l6BeErMBe+5bX49 Q7SILDp8EjKbSy3EfdIqMvGNI1YhY8RyZG+wIXzcWIJGNwr9HqRi4K1oB daygog3Jz2KQ2QwHA693c11Rncx5JCRGYwQaJdDZptfvcl8bBnocJqaoA E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAA4CtFStJA2N/2dsb2JhbABbgmQigS7LbwKBEEMBAQEBAX2EDAEBAQMBeQULAgEIGCcHMhQRAgQOBYgkCAHMdQEBAQEBAQEBAQEBAQEBAQEBAQEBARePRjMHgxaBEwEEiTuFAokNkXgig25vgUV+AQEB
X-IronPort-AV: E=Sophos;i="5.07,744,1413244800"; d="scan'208";a="112525959"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-8.cisco.com with ESMTP; 12 Jan 2015 17:22:04 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t0CHM4YR020235 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 Jan 2015 17:22:04 GMT
Received: from xmb-aln-x02.cisco.com ([fe80::8c1c:7b85:56de:ffd1]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Mon, 12 Jan 2015 11:22:04 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Thread-Topic: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft
Thread-Index: AQHQLFlIxHraldlX1E6Vd7Vv5azW0Zy8F/yQgAEMdIA=
Date: Mon, 12 Jan 2015 17:22:02 +0000
Message-ID: <8415F584-A773-45C0-A578-61BFE67F2DF5@cisco.com>
References: <4AAB478A-442A-4A01-84D5-2B21EE63C7D4@cisco.com> <696AF7FE-4E14-4825-8B81-0EC5FB752342@cisco.com> <953011D7-0D9C-41CA-B13D-A823A18A9CF0@cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F50439CBA292@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F50439CBA292@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <85B9F3428E74734BBCA6C863AD040AA5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/XuewrK9GpE6vDsaGX6yCUE3EY8g>
X-Mailman-Approved-At: Wed, 14 Jan 2015 08:56:33 -0800
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 17:22:07 -0000

Yes, definitely and we have text in the draft to warn folks not to be surpr=
ised by that as it is fairly common.=20


> On Jan 12, 2015, at 12:24 AM, Ruediger.Geib@telekom.de wrote:
>=20
> Cullen,
>=20
> that includes a DSCP rewrite to default/0 (and forwarding in default PHB)=
?
>=20
> Regards,
>=20
> Ruediger
>=20
> ----Urspr=FCngliche Nachricht-----
> Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Cullen Jennings=
 (fluffy)
> Gesendet: Freitag, 9. Januar 2015 23:12
> An: Fred Baker (fred)
> Cc: tsvwg@ietf.org
> Betreff: Re: [tsvwg] [OPS-DIR] Early Ops-Dir review for rtcweb-qos draft
>=20
>=20
>> On Jul 2, 2014, at 11:50 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>>=20
>> As an additional comment, reflecting on comments in other quarters (dart=
), it may be worthwhile pointing out in the draft that the DSCP indicates a=
 minimum acceptable service level; if a network thinks it can achieve that =
service level within some larger scheme (such as a traffic class described =
in Ruediger's draft, RFC 5127, or simply by oversupplying bandwidth), that =
is at the operator's discretion.
>=20
> Fred, I think that from the point of view of this draft, the DSCP don't r=
eally indicate any minimum that the network needs to provide. The network c=
an totally ignore the DSCP value  and whatever it might do based on the DSC=
P is out of scope of this draft and handled in the RFC that defined the DSC=
P.
>=20
>=20
>=20
>=20


From nobody Wed Jan 14 08:57:54 2015
Return-Path: <rick.bellingar@reedelsevier.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 594001A90CA for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 05:49:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level: 
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] 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 3YaK6aZDSKQM for <tsvwg@ietfa.amsl.com>; Mon, 12 Jan 2015 05:49:35 -0800 (PST)
Received: from p01c12o144.mxlogic.net (p01c12o144.mxlogic.net [208.65.145.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF0321A90E3 for <tsvwg@ietf.org>; Mon, 12 Jan 2015 05:49:34 -0800 (PST)
Received: from unknown [198.185.18.9] (EHLO p01c12o144.mxlogic.net) by p01c12o144.mxlogic.net(mxl_mta-8.2.0-3) with ESMTP id ee0d3b45.2ae6a560e940.72582.00-579.189363.p01c12o144.mxlogic.net (envelope-from <rick.bellingar@reedelsevier.com>);  Mon, 12 Jan 2015 06:49:34 -0700 (MST)
X-MXL-Hash: 54b3d0ee5717c45a-75ade129996ad5c192c20989ab25680c01deae1f
Received: from unknown [198.185.18.9] by p01c12o144.mxlogic.net(mxl_mta-8.2.0-3) with SMTP id 2d0d3b45.0.72022.00-377.188675.p01c12o144.mxlogic.net (envelope-from <rick.bellingar@reedelsevier.com>);  Mon, 12 Jan 2015 06:49:27 -0700 (MST)
X-MXL-Hash: 54b3d0e72dae3457-d22836fb0ee5f665cdf56cbafb8f295ad99bc3d0
Received: from RETDAYHUBP002.legal.regn.net (138.12.19.117) by retdayedgp001.reedelsevier.com (192.168.37.39) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 12 Jan 2015 08:48:13 -0500
Received: from retdayedgp001.reedelsevier.com (192.168.37.39) by RETDAYHUBP002.legal.regn.net (138.12.19.117) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 12 Jan 2015 08:48:22 -0500
Received: from na01-bl2-obe.outbound.protection.outlook.com (207.46.163.210) by retuso365smtp.reedelsevier.com (192.168.37.39) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 12 Jan 2015 08:48:13 -0500
Received: from BLUPR0801MB546.namprd08.prod.outlook.com (10.141.252.24) by BLUPR0801MB548.namprd08.prod.outlook.com (10.141.252.26) with Microsoft SMTP Server (TLS) id 15.1.53.17; Mon, 12 Jan 2015 13:48:21 +0000
Received: from BLUPR0801MB546.namprd08.prod.outlook.com ([10.141.252.24]) by BLUPR0801MB546.namprd08.prod.outlook.com ([10.141.252.24]) with mapi id 15.01.0053.000; Mon, 12 Jan 2015 13:48:21 +0000
From: "Bellingar, Richard J. (RET-DAY)" <Rick.Bellingar@reedelsevier.com>
To: "Eggert, Lars" <lars@netapp.com>
Thread-Topic: [tsvwg] [IANA #800143] Port squatting
Thread-Index: AdAcChI6gE9sZ285QqiQjXL4eZYuzQOkcYGAAMix7dAAN2HLAAALomsQ
Date: Mon, 12 Jan 2015 13:48:21 +0000
Message-ID: <BLUPR0801MB546AB8397874F9DE1DB9F5DFD430@BLUPR0801MB546.namprd08.prod.outlook.com>
References: <RT-Ticket-800143@icann.org> <BLUPR0801MB54648E91525B7BFC05BE3C7FD680@BLUPR0801MB546.namprd08.prod.outlook.com> <rt-4.0.8-22959-1420650203-1117.800143-6-0@icann.org> <BLUPR0801MB546416E2A87A6A4D243E765FD420@BLUPR0801MB546.namprd08.prod.outlook.com> <38DA8A39-15B1-4E76-9265-24547E5CEBE3@netapp.com>
In-Reply-To: <38DA8A39-15B1-4E76-9265-24547E5CEBE3@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [198.185.18.72]
x-dmarcaction-test: None
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(3005003);SRVR:BLUPR0801MB548;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BLUPR0801MB548;
x-forefront-prvs: 0454444834
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(51704005)(199003)(189002)(39064003)(51914003)(13464003)(24454002)(11905935001)(377424004)(377454003)(2656002)(33656002)(101416001)(86362001)(54206007)(76576001)(93886004)(54606007)(50986999)(54356999)(76176999)(19580395003)(19580405001)(105586002)(122556002)(68736005)(1720100001)(40100003)(15975445007)(2950100001)(97736003)(2900100001)(64706001)(106356001)(77096005)(74316001)(66066001)(110136001)(87936001)(46102003)(102836002)(99286002)(92566002)(62966003)(77156002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0801MB548; H:BLUPR0801MB546.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: reedelsevier.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2015 13:48:21.4759 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9274ee3f-9425-4109-a27f-9fb15c10675d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0801MB548
X-OrganizationHeadersPreserved: BLUPR0801MB548.namprd08.prod.outlook.com
X-CrossPremisesHeadersPromoted: retdayedgp001.reedelsevier.com
X-CrossPremisesHeadersFiltered: retdayedgp001.reedelsevier.com
X-OriginatorOrg: reedelsevier.com
X-AnalysisOut: [v=2.1 cv=DqJC+QP+ c=1 sm=1 tr=0 a=RnNbNtdpXsCS/37iQjHvNQ==]
X-AnalysisOut: [:117 a=RnNbNtdpXsCS/37iQjHvNQ==:17 a=sEHMLM1fE0YA:10 a=46N]
X-AnalysisOut: [Al10togAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=k3ev2J5]
X-AnalysisOut: [7AAAA:8 a=UqCG9HQmAAAA:8 a=YlVTAMxIAAAA:8 a=gRkuwbbrAAAA:8]
X-AnalysisOut: [ a=YNv0rlydsVwA:10 a=IsxHxj7WAAAA:8 a=JDjsHSkAAAAA:8 a=48v]
X-AnalysisOut: [gC7mUAAAA:8 a=I0CVDw5ZAAAA:8 a=N_G48U8nAYVBXJIpjEYA:9 a=Cj]
X-AnalysisOut: [uIK1q_8ugA:10 a=jOo1f2NL5OQA:10 a=OB46QkFbDjsA:10 a=vbnqrM]
X-AnalysisOut: [M_esoA:10]
X-Spam: [F=0.5000000000; CM=0.500; MH=0.500(2015011208); S=0.200(2014051901)]
X-MAIL-FROM: <rick.bellingar@reedelsevier.com>
X-SOURCE-IP: [198.185.18.9]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/3uqDcOTS5zsePaRzMnrw9DUnm-c>
X-Mailman-Approved-At: Wed, 14 Jan 2015 08:57:48 -0800
Cc: "iana-questions@iana.org" <iana-questions@iana.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] [IANA #800143] Port squatting
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 13:49:37 -0000

Lars,
	Thanks for the response.
	A recent firewall change request in support of a Progress database install=
ation that I challenged surfaced the following -

"Each remote server is assigned a port when it is initially spawned. By def=
ault, the remote servers use the first available port in the 1025-2000 rang=
e on UNIX (3000-5000 for Windows)."
http://knowledgebase.progress.com/articles/Article/P98541

	The article does also give instructions for assigning an "alternate" port =
range.

Rick Bellingar
Reed-Elsevier Information Security
937-865-7005

-----Original Message-----
From: Eggert, Lars [mailto:lars@netapp.com]=20
Sent: Monday, January 12, 2015 6:16 AM
To: Bellingar, Richard J. (RET-DAY)
Cc: tsvwg@ietf.org; iana-questions@iana.org
Subject: Re: [tsvwg] [IANA #800143] Port squatting

Hi,

On 2015-1-11, at 18:01, Bellingar, Richard J. (RET-DAY) <Rick.Bellingar@ree=
delsevier.com> wrote:
>=20
> I really don't understand Pearl's answer (below). At one time, I found a =
means (an email address, I think) to report companies/applications that wer=
e using ports in the System & Registered ranges that were not reserved or w=
ere reserved by other companies/apps. Those then, presumably, were added to=
 the IANA database and depicted in the "Known Unauthorized Uses" column of =
http://www.iana.org/assignments/service-names-port-numbers/service-names-po=
rt-numbers.xhtml . Has that practice ceased?

no, but it involves the IETF and the area director. So raising it on this l=
ist is the right thing to do, and then Martin and Spencer can instruct IANA=
 via the IESG as needed.

Lars

>=20
> -----Original Message-----
> From: Pearl Liang via RT [mailto:iana-questions@iana.org]
> Sent: Wednesday, January 07, 2015 12:03 PM
> To: Bellingar, Richard J. (RET-DAY)
> Subject: [IANA #800143] Port squatting
>=20
> Hello,
>=20
> Thank you for contacting us.
>=20
> On Sat Dec 20 04:05:46 2014, Rick.Bellingar@reedelsevier.com wrote:
>> Is there still a means to report port squatting? I found one in the=20
>> past, but can't find one now.
>>=20
>=20
> First of all, we do not monitor any traffic flowing to or from any and al=
l port numbers, specifically unassigned port numbers (0-49151.)  Nor do we =
have knowledge of traffic to any port numbers 0-49151.  We sought some advi=
ces from the IESG designated port expert who indicated that we (IETF) are n=
ot regulating the port traffic.
>=20
> You may contact the IETF Transport Area Working Group at tsvwg@ietf.org i=
f you prefer.
>=20
> Thank you,
>=20
> Pearl Liang
> ICANN
>=20
>=20


From nobody Wed Jan 14 13:39:25 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 920121AC3EC for <tsvwg@ietfa.amsl.com>; Wed, 14 Jan 2015 13:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 taLaKkklYN9W for <tsvwg@ietfa.amsl.com>; Wed, 14 Jan 2015 13:39:20 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A0321A90CC for <tsvwg@ietf.org>; Wed, 14 Jan 2015 13:39:19 -0800 (PST)
Received: from [192.168.1.200] (p508F28EF.dip0.t-ipconnect.de [80.143.40.239]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id B46461C104357; Wed, 14 Jan 2015 22:39:17 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <tuexen@fh-muenster.de>
X-Priority: 3 (Normal)
In-Reply-To: <ec85e5c90df22010c40ad6cc21e1c2a0.squirrel@erg.abdn.ac.uk>
Date: Wed, 14 Jan 2015 22:39:16 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <9C5D9011-B549-4CB2-B235-B550EBF36F0A@fh-muenster.de>
References: <8C559303-B26F-41D7-8063-C3FC268E02B0@fh-muenster.de> <6946e413159a3427a0c344a577cdf653.squirrel@erg.abdn.ac.uk> <F1E96F4E-7E2E-4273-8D23-037B868C6F17@fh-muenster.de> <5358c9c78e6ad57ac44b558858b1ae42.squirrel@erg.abdn.ac.uk> <1F0BEF14-720E-46D0-8EC7-80F79EB63EE8@fh-muenster.de> <0650cdffedf63ea0ec66373dfbd449d0.squirrel@erg.abdn.ac.uk> <B4331CE7-F7CB-4BE4-8EF4-E346867106B7@fh-muenster.de> <ec85e5c90df22010c40ad6cc21e1c2a0.squirrel@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/1kNrwWwVjiT_AfobonCYRcmdGFo>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-sctp-dtls-encaps-08.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 21:39:22 -0000

> On 14 Jan 2015, at 12:57, gorry@erg.abdn.ac.uk wrote:
> 
> Please see comments in line.
> 
>> On 12 Jan 2015, at 18:46, gorry@erg.abdn.ac.uk wrote:
>>> 
>>> It looks like we are getting towards a point where it would be useful to
>>> issue a new draft, so with this in mind I have a few comments (no
>>> Chair's
>>> hat yet), so please feel free to comment on these comments...
>> Hi Gorry,
>> 
>> thank you very much for your review. See my comments in-line.
>> 
>> Best regards
>> Michael
>>> 
>>> 
>>> I think the abstract  could benefit from a little explanation of the
>>> need
>>> for DTLS encapsulation, given RFC 6951, and  RTCweb wishes to use UDP
>>> with
>>> security. That's implied right now, and I think should be explicit.
>>> 
>>> I'd really encourage you to add this diagram to the intro, this wouldn't
>>> hurt, and it makes it obvious!
>>> 
>>> "
>>>                              +----------+
>>>                              |   SCTP   |
>>>                              +----------+
>>>                              |   DTLS   |
>>>                              +----------+
>>>                              | ICE/UDP  |
>>>                              +----------+
>>> 
>>>                      Figure 1: Basic stack diagram"
>>> 
>>> And suggest you follow with something like:
>>> 
>>>  This encapsulation of SCTP over DTLS over UDP or ICE/UDP (see
>>> [RFC5245])
>>>  can provide a NAT traversal solution together with confidentiality,
>>>  source authentication, and integrity protected transfers. "
>> 
>> Just the be clear:
>> Do you want to to add some clarifying text to the abstract and the stack
>> diagram followed up by the sentence added to the overview? There is no
>> section called intro...
>> 
> The first section would be fine.
Done.
> 
>>> This new text:
>>> "In case of a window based congestion..."
>>> Maybe would be clearer as:
>>> "The window-based congestion control method specified in [RFC4960],
>>> resets the congestion window and slow start threshold to their initial
>>> values."
>> OK. Taken.
>>> 
>>> In 6.2, is it perhaps clearer to say exactly what is done, to help the
>>> DTLS
>>> reader understand e.g.
>>> "and can be used to send probe packets (HEARTBEAT chunks
>>> bundled with PADDING chunks [RFC4960])."
>> What about:
>> <t>When the SCTP layer performs path MTU discovery as specified in
>> <xref target='RFC4821'/>, the padding extension defined in
>> <xref target='RFC4820'/> MUST be supported and used for probe packets
>> (HEARTBEAT chunks bundled with PADDING chunks <xref
>> target='RFC4820'/>).</t>
>> 
>> Please note that I don't use "can be used" and that I changed the
>> reference
>> the RFC 4820, since I don't know why you are referring to RFC 4960.
>> 
> The new text sounds good.
> 
>>> 
>>> I think it would be useful to also mention: "Path MTU discovery
>>> is required by SCTP when SCTP over DTLS is used
>>> for data channels (section 4 of draft-ietf-rtcweb-data-channel-13]."
>> I added to section 6.2:
>> <t>Path MTU discovery is required by SCTP when SCTP over DTLS is used
>> for data channels
>> (see Section 4 of <xref target='I-D.ietf-rtcweb-data-channel'/>).</t>
>> 
>> Not sure this is the best place. I think a better place would be to add
>> this at the end of Section 4. OK?
>> 
> This looks good.
I added at the end of section 4:
<t>The path MTU discovery is performed by SCTP when SCTP over DTLS is used
for data channels (see Section 4 of
<xref target='I-D.ietf-rtcweb-data-channel'/>).</t>
(some word smithing applied...) 

Best regards
Michael
> 
>>> 
>>> Best wishes,
>>> 
>>> Gorry
>>> 
>> 
> 
> Gorry
> 
> 


From nobody Thu Jan 15 05:49:20 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1AF1B2BE2; Thu, 15 Jan 2015 05:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 JrZddqb1Pz94; Thu, 15 Jan 2015 05:49:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E33B1B2BE0; Thu, 15 Jan 2015 05:49:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150115134913.4807.25584.idtracker@ietfa.amsl.com>
Date: Thu, 15 Jan 2015 05:49:13 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/8l7DPIZcPf8NuQD66I2uQSEk4a4>
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-08.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 13:49:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : DTLS Encapsulation of SCTP Packets
        Authors         : Michael Tuexen
                          Randall R. Stewart
                          Randell Jesup
                          Salvatore Loreto
	Filename        : draft-ietf-tsvwg-sctp-dtls-encaps-08.txt
	Pages           : 9
	Date            : 2015-01-15

Abstract:
   The Stream Control Transmission Protocol (SCTP) is a transport
   protocol originally defined to run on top of the network protocols
   IPv4 or IPv6.  This document specifies how SCTP can be used on top of
   the Datagram Transport Layer Security (DTLS) protocol.  Using the
   encapsulation method described in this document, SCTP is unaware of
   the protocols being used below DTLS; hence explicit IP addresses
   cannot be used in the SCTP control chunks.  As a consequence, the
   SCTP associations carried over DTLS can only be single homed.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-dtls-encaps-08


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 Fri Jan 16 10:55:13 2015
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2F81B2A4E for <tsvwg@ietfa.amsl.com>; Fri, 16 Jan 2015 10:55:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 8-GLovRFW0-m for <tsvwg@ietfa.amsl.com>; Fri, 16 Jan 2015 10:55:07 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A66701ACE72 for <tsvwg@ietf.org>; Fri, 16 Jan 2015 10:55:07 -0800 (PST)
Received: from [10.123.102.85] (usc-secure-wireless-206-085.usc.edu [68.181.206.85]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id t0GIsRZe019406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Jan 2015 10:54:30 -0800 (PST)
Message-ID: <54B95E64.1090101@isi.edu>
Date: Fri, 16 Jan 2015 10:54:28 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "Bellingar, Richard J. (RET-DAY)" <Rick.Bellingar@reedelsevier.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "iana-questions@iana.org" <iana-questions@iana.org>
References: <RT-Ticket-800143@icann.org> <BLUPR0801MB54648E91525B7BFC05BE3C7FD680@BLUPR0801MB546.namprd08.prod.outlook.com> <rt-4.0.8-22959-1420650203-1117.800143-6-0@icann.org> <BLUPR0801MB546416E2A87A6A4D243E765FD420@BLUPR0801MB546.namprd08.prod.outlook.com>
In-Reply-To: <BLUPR0801MB546416E2A87A6A4D243E765FD420@BLUPR0801MB546.namprd08.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/GKIhkQEaErRqErcxODVxHuYOl3o>
Subject: Re: [tsvwg] FW: [IANA #800143] Port squatting
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 18:55:10 -0000

Hi, Richard, et al.,

IANA currently indicates when a port is being squatted to help advise
applicants for new assignments, so they can decide for themselves
whether they want to deal with that.

But if IANA were to indicate the specific squatter, that could be taken
as endorsement of squatting. That's problematic - especially for
assigned ports.

I.e., if this was reporting squatting, that should still be supported by
IANA IMO (and I think it is, though the form to do so might need to be
restored). However, I don't think IANA should post the details of that
other than "Known unauthorized use".

Joe

On 1/11/2015 9:01 AM, Bellingar, Richard J. (RET-DAY) wrote:
> I really don't understand Pearl's answer (below). At one time, I found a means (an email address, I think) to report companies/applications that were using ports in the System & Registered ranges that were not reserved or were reserved by other companies/apps. Those then, presumably, were added to the IANA database and depicted in the "Known Unauthorized Uses" column of http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml . Has that practice ceased?
> 
> -----Original Message-----
> From: Pearl Liang via RT [mailto:iana-questions@iana.org] 
> Sent: Wednesday, January 07, 2015 12:03 PM
> To: Bellingar, Richard J. (RET-DAY)
> Subject: [IANA #800143] Port squatting
> 
> Hello,
> 
> Thank you for contacting us.
> 
> On Sat Dec 20 04:05:46 2014, Rick.Bellingar@reedelsevier.com wrote:
>> Is there still a means to report port squatting? I found one in the 
>> past, but can't find one now.
>>
> 
> First of all, we do not monitor any traffic flowing to or from any and all port numbers, specifically unassigned port numbers (0-49151.)  Nor do we have knowledge of traffic to any port numbers 0-49151.  We sought some advices from the IESG designated port expert who indicated that we (IETF) are not regulating the port traffic.
> 
> You may contact the IETF Transport Area Working Group at tsvwg@ietf.org if you prefer.  
> 
> Thank you,
> 
> Pearl Liang
> ICANN
> 
> 


From nobody Fri Jan 16 10:57:06 2015
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 668891B2A5F; Fri, 16 Jan 2015 10:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 d8vmx7KZORHB; Fri, 16 Jan 2015 10:57:01 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84F591B2A5A; Fri, 16 Jan 2015 10:57:01 -0800 (PST)
Received: from [10.123.102.85] (usc-secure-wireless-206-085.usc.edu [68.181.206.85]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id t0GIuRHp019780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Jan 2015 10:56:30 -0800 (PST)
Message-ID: <54B95EDC.9000905@isi.edu>
Date: Fri, 16 Jan 2015 10:56:28 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com>
In-Reply-To: <54A990F4.9040509@isode.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/nXAhss1ZGqJ4MDS_G52Shfo9zjg>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 18:57:03 -0000

Hi, Alexey (et al.),

Suggestions on how to address these concerns below.

On 1/4/2015 11:13 AM, Alexey Melnikov wrote:
> On 08/12/2014 23:56, The IESG wrote:
>> The IESG has received a request from the Transport Area Working Group WG
>> (tsvwg) to consider the following document:
>> - 'Recommendations for Transport Port Number Uses'
>>    <draft-ietf-tsvwg-port-use-06.txt> as Best Current Practice
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2014-12-22. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     This document provides recommendations to application and service
>>     designers on how to use the transport protocol port number space. IT
>>     complements (but does not update) RFC6335, which focuses on IANA
>>     process.
>
> My apologies for late review of the document. I generally think that the
> document is well written and is nearly done, but I have some
> comments/concerns.
> 
> 1. Introduction
> 
>    This document provides information and advice to system designers on
>    the use of transport port numbers. It provides a detailed historical
>    background of the evolution of transport port numbers and their
>    multiple meanings. It also provides specific recommendations to
>    system designers on how to use assigned port numbers. Note that this
>    document provides information to potential port number applicants
>    that complements the IANA process described in BCP165 [RFC6335], but
>    it does not update that document.
> 
> I am a bit confused by the status and purpose of this document. It is a
> BCP, but the introducting
> says that it is purely informational. But then the document has lots of
> RFC 2119 language.
> Is there any intent for this document
> to be of use to port expert reviewers, for example if they want to point
> out why a particular port registration request is rejected?

AFAICT, expert reviewers can use any reason they want to recommend an
approval or rejection; the same is true for IANA. There is an appeals
process to the IESG when a decision disagreement occurs, and they can
make decisions on a case-by-case basis.

The review team does try to provide a consistent set of responses, i.e.,
to treat similar requests as similarly as possible, but again that's not
scripted.

I don't think it's useful to closely or tightly constrain a process
which is both advisory and intended to deal with corner cases.

That's why I think it's appropriate for this doc to be BCP
recommendation to the user (which is how it's written), rather than
explicit constraints for expert review. However, I would expect that
recommendations for users from TSV would be taken as context for
reviews, as would any other TSV documents.

> In 7.1:
> 
>          Additional port numbers are not intended to replicate an
>          existing service. For example, if a device is configured to
>          use a typical web browser then it the port number used for
>          that service is a copy of the http service that is already
>          assigned to port number 80 and does not warrant a new
>          assignment. However, an automated system that happens to use
>          HTTP framing - but cannot be accessed by a browser - might be
> 
> I have some concerns about "be access by a browser".
> 
> One particular case I have in mind is when a service expose some data
> using JSON or ASN.1 (for example a certificate revocation list is
> returned), but also allow a browser to view certificate in a nice form
> using HTML (e.g. for debugging or convenience). I don't think the
> ability to return HTML automatically disqualify this from being an
> independent service, because the whole functionality supported by the
> service can't be implemented just by use of returned HTML.
> 
> Inserting "solely" before "by a browser" would address my concern.

Would "primarily" also work? It's hard to argue "solely" even for
conventional web access.

>          a new service. A good way to tell is "can an unmodified client
>          of the existing service interact with the proposed service"?
>          If so, that service would be a copy of an existing service and
>          would not merit a new assignment.
> 
> In 7.4:
> 
>    Note however that a new service might not be eligible for IANA
>    assignment of both an insecure and a secure variant of the same
>    service, and similarly IANA might be skeptical of an assignment for
> 
> I don't think use of wording like "IANA might be skeptical" is correct
> here, because IANA doesn't define policy on this. IETF does. So let's
> call things with right names and don't misuse "IANA" here.

The document isn't written by IANA. We recommend to IANA, and IANA makes
a decision that the IESG can override. I don't think it's outside the
scope of the doc to indicate this context.

Would it be preferable to say that "applications asking for both...
might not be approved when..."?

>    an insecure port number for a secure service. In both cases,
>    security of the service is compromised by adding the insecure port
>    number assignment.
> 
> Similarly (in the same section): "IANA currently permits ..."

Same solution here?

Joe


From nobody Fri Jan 16 11:19:39 2015
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 163EE1B2A91; Fri, 16 Jan 2015 11:19:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 PzbIIJL5qQK8; Fri, 16 Jan 2015 11:19:35 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7391B2A88; Fri, 16 Jan 2015 11:19:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1421435974; d=isode.com; s=selector; i=@isode.com; bh=q3QJtyaCUKY5jL/VVoih0S8CbqjcKtoOuHcFqOLt2zY=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=fde48ubN/N6h32JF2t82GZPt0V/5YOWMoohqke6lB638uL5nuiFJwhsy3Zx+EmXKd9zKJ7 hSzaNvyk2ZdmD5+Gf1Mqdwg41Su5nMK5FRqakYxmMdYQOiCJziqEfoKpp9qmDUdcXEFa0H /bPiFqsIN2VapCujoDjyYsKy4gk4nno=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <VLlkRQAKaFWm@waldorf.isode.com>; Fri, 16 Jan 2015 19:19:33 +0000
Message-ID: <54B9639F.7020905@isode.com>
Date: Fri, 16 Jan 2015 19:16:47 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Joe Touch <touch@isi.edu>, ietf@ietf.org
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu>
In-Reply-To: <54B95EDC.9000905@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/G_KPxbGVTCnIuUGTKnGhu3_3uKM>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 19:19:38 -0000

Hi Joe,

On 16/01/2015 18:56, Joe Touch wrote:
> Hi, Alexey (et al.),
>
> Suggestions on how to address these concerns below.
>
> On 1/4/2015 11:13 AM, Alexey Melnikov wrote:
>> On 08/12/2014 23:56, The IESG wrote:
>>> The IESG has received a request from the Transport Area Working Group WG
>>> (tsvwg) to consider the following document:
>>> - 'Recommendations for Transport Port Number Uses'
>>>     <draft-ietf-tsvwg-port-use-06.txt> as Best Current Practice
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2014-12-22. Exceptionally, comments may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>      This document provides recommendations to application and service
>>>      designers on how to use the transport protocol port number space. IT
>>>      complements (but does not update) RFC6335, which focuses on IANA
>>>      process.
>> My apologies for late review of the document. I generally think that the
>> document is well written and is nearly done, but I have some
>> comments/concerns.
>>
>> 1. Introduction
>>
>>     This document provides information and advice to system designers on
>>     the use of transport port numbers. It provides a detailed historical
>>     background of the evolution of transport port numbers and their
>>     multiple meanings. It also provides specific recommendations to
>>     system designers on how to use assigned port numbers. Note that this
>>     document provides information to potential port number applicants
>>     that complements the IANA process described in BCP165 [RFC6335], but
>>     it does not update that document.
>>
>> I am a bit confused by the status and purpose of this document. It is a
>> BCP, but the introducting
>> says that it is purely informational. But then the document has lots of
>> RFC 2119 language.
>> Is there any intent for this document
>> to be of use to port expert reviewers, for example if they want to point
>> out why a particular port registration request is rejected?
> AFAICT, expert reviewers can use any reason they want to recommend an
> approval or rejection; the same is true for IANA. There is an appeals
> process to the IESG when a decision disagreement occurs, and they can
> make decisions on a case-by-case basis.
>
> The review team does try to provide a consistent set of responses, i.e.,
> to treat similar requests as similarly as possible, but again that's not
> scripted.
>
> I don't think it's useful to closely or tightly constrain a process
> which is both advisory and intended to deal with corner cases.
>
> That's why I think it's appropriate for this doc to be BCP
> recommendation to the user (which is how it's written), rather than
> explicit constraints for expert review. However, I would expect that
> recommendations for users from TSV would be taken as context for
> reviews, as would any other TSV documents.
My concerns is that BCP are commonly used by ADs to enforce compliance. 
So I am wondering why this document is not just Informational?
>> In 7.1:
>>
>>           Additional port numbers are not intended to replicate an
>>           existing service. For example, if a device is configured to
>>           use a typical web browser then it the port number used for
>>           that service is a copy of the http service that is already
>>           assigned to port number 80 and does not warrant a new
>>           assignment. However, an automated system that happens to use
>>           HTTP framing - but cannot be accessed by a browser - might be
>>
>> I have some concerns about "be access by a browser".
>>
>> One particular case I have in mind is when a service expose some data
>> using JSON or ASN.1 (for example a certificate revocation list is
>> returned), but also allow a browser to view certificate in a nice form
>> using HTML (e.g. for debugging or convenience). I don't think the
>> ability to return HTML automatically disqualify this from being an
>> independent service, because the whole functionality supported by the
>> service can't be implemented just by use of returned HTML.
>>
>> Inserting "solely" before "by a browser" would address my concern.
> Would "primarily" also work? It's hard to argue "solely" even for
> conventional web access.
Yes, "primarily" is actually better.
>>           a new service. A good way to tell is "can an unmodified client
>>           of the existing service interact with the proposed service"?
>>           If so, that service would be a copy of an existing service and
>>           would not merit a new assignment.
>>
>> In 7.4:
>>
>>     Note however that a new service might not be eligible for IANA
>>     assignment of both an insecure and a secure variant of the same
>>     service, and similarly IANA might be skeptical of an assignment for
>>
>> I don't think use of wording like "IANA might be skeptical" is correct
>> here, because IANA doesn't define policy on this. IETF does. So let's
>> call things with right names and don't misuse "IANA" here.
> The document isn't written by IANA. We recommend to IANA, and IANA makes
> a decision that the IESG can override. I don't think it's outside the
> scope of the doc to indicate this context.
Actually I disagree. IANA is just following procedure prescribed by 
IETF. Experts are not really acting as advisors (although in practice 
there is always a dialogue, which is as it should be).
> Would it be preferable to say that "applications asking for both...
> might not be approved when..."?
Yes.
>>     an insecure port number for a secure service. In both cases,
>>     security of the service is compromised by adding the insecure port
>>     number assignment.
>>
>> Similarly (in the same section): "IANA currently permits ..."
> Same solution here?
Sure.


From nobody Fri Jan 16 11:27:23 2015
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 598D81B2A97; Fri, 16 Jan 2015 11:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 t-Z5w9sQxqJp; Fri, 16 Jan 2015 11:27:16 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26A301B2AC7; Fri, 16 Jan 2015 11:27:14 -0800 (PST)
Received: from [10.123.102.85] (usc-secure-wireless-206-085.usc.edu [68.181.206.85]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id t0GJQmxx026491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Jan 2015 11:26:51 -0800 (PST)
Message-ID: <54B965F9.6090704@isi.edu>
Date: Fri, 16 Jan 2015 11:26:49 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu> <54B9639F.7020905@isode.com>
In-Reply-To: <54B9639F.7020905@isode.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/BGkZRNHOlB4Q5UO7NEeaGlQLCgY>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 19:27:21 -0000

Hi, Alexey,

On 1/16/2015 11:16 AM, Alexey Melnikov wrote:
> Hi Joe,
> 
...
> My concerns is that BCP are commonly used by ADs to enforce compliance.
> So I am wondering why this document is not just Informational?

AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
protocol designers than would be an Informational doc.

However, the way expert review and the appeals process already allows
ADs to either use BCPs or override them anyway, so I don't see this as
unduly constraining them. Besides, all sorts of docs - including
standards-track - are contradictory, so there's no one way to ensure
they're all followed.

...
>>> In 7.4:
...
>>> Inserting "solely" before "by a browser" would address my concern.
>> Would "primarily" also work? It's hard to argue "solely" even for
>> conventional web access.
>
> Yes, "primarily" is actually better.

OK. Will do.

>>> In 7.4:
>>>
>>>     Note however that a new service might not be eligible for IANA
>>>     assignment of both an insecure and a secure variant of the same
>>>     service, and similarly IANA might be skeptical of an assignment for
>>>
>>> I don't think use of wording like "IANA might be skeptical" is correct
>>> here, because IANA doesn't define policy on this. IETF does. So let's
>>> call things with right names and don't misuse "IANA" here.
>>
>> The document isn't written by IANA. We recommend to IANA, and IANA makes
>> a decision that the IESG can override. I don't think it's outside the
>> scope of the doc to indicate this context.
>
> Actually I disagree. IANA is just following procedure prescribed by
> IETF. Experts are not really acting as advisors (although in practice
> there is always a dialogue, which is as it should be).

IANA doesn't have to agree with expert reviewer recommendations. There
isn't anything binding that, though - as you note - there's a dialogue
and it's not an issue in practice.

>> Would it be preferable to say that "applications asking for both...
>> might not be approved when..."?
>
> Yes.

OK - will do.

>>>     an insecure port number for a secure service. In both cases,
>>>     security of the service is compromised by adding the insecure port
>>>     number assignment.
>>>
>>> Similarly (in the same section): "IANA currently permits ..."
>> Same solution here?
>
> Sure.

OK - will do.

Joe


From nobody Sat Jan 17 08:51:19 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A96A1ACD73; Sat, 17 Jan 2015 08:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 JvHZG5hgyr6e; Sat, 17 Jan 2015 08:51:15 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id E77321ACD4A; Sat, 17 Jan 2015 08:51:14 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id D1D6B1B0028C; Sat, 17 Jan 2015 16:51:06 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Sat, 17 Jan 2015 16:51:06 -0000
Message-ID: <691f86d47ca683d48ab707d12e999534.squirrel@erg.abdn.ac.uk>
In-Reply-To: <54B965F9.6090704@isi.edu>
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu> <54B9639F.7020905@isode.com> <54B965F9.6090704@isi.edu>
Date: Sat, 17 Jan 2015 16:51:06 -0000
From: gorry@erg.abdn.ac.uk
To: "Joe Touch" <touch@isi.edu>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/HmjS9ZcDxblRDAEAklA7qorj0XA>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Jan 2015 16:51:17 -0000

HI,

I added a little history in-line to help inform comments on the intended
status.

> Hi, Alexey,
>
> On 1/16/2015 11:16 AM, Alexey Melnikov wrote:
>> Hi Joe,
>>
> ...
>> My concerns is that BCP are commonly used by ADs to enforce compliance.
>> So I am wondering why this document is not just Informational?
>
> AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
> protocol designers than would be an Informational doc.
>
Yes the document was marked BCP on 2011-01-26 after WG discussion and
advice from our ADs, but this was not based on offering advice to IANA (as
in RFC 6335), but rather guidance to protocol and applications designers
needing to use transport ports

Gorry

> However, the way expert review and the appeals process already allows
> ADs to either use BCPs or override them anyway, so I don't see this as
> unduly constraining them. Besides, all sorts of docs - including
> standards-track - are contradictory, so there's no one way to ensure
> they're all followed.
>
> ...
>>>> In 7.4:
> ...
>>>> Inserting "solely" before "by a browser" would address my concern.
>>> Would "primarily" also work? It's hard to argue "solely" even for
>>> conventional web access.
>>
>> Yes, "primarily" is actually better.
>
> OK. Will do.
>
>>>> In 7.4:
>>>>
>>>>     Note however that a new service might not be eligible for IANA
>>>>     assignment of both an insecure and a secure variant of the same
>>>>     service, and similarly IANA might be skeptical of an assignment
>>>> for
>>>>
>>>> I don't think use of wording like "IANA might be skeptical" is correct
>>>> here, because IANA doesn't define policy on this. IETF does. So let's
>>>> call things with right names and don't misuse "IANA" here.
>>>
>>> The document isn't written by IANA. We recommend to IANA, and IANA
>>> makes
>>> a decision that the IESG can override. I don't think it's outside the
>>> scope of the doc to indicate this context.
>>
>> Actually I disagree. IANA is just following procedure prescribed by
>> IETF. Experts are not really acting as advisors (although in practice
>> there is always a dialogue, which is as it should be).
>
> IANA doesn't have to agree with expert reviewer recommendations. There
> isn't anything binding that, though - as you note - there's a dialogue
> and it's not an issue in practice.
>
>>> Would it be preferable to say that "applications asking for both...
>>> might not be approved when..."?
>>
>> Yes.
>
> OK - will do.
>
>>>>     an insecure port number for a secure service. In both cases,
>>>>     security of the service is compromised by adding the insecure port
>>>>     number assignment.
>>>>
>>>> Similarly (in the same section): "IANA currently permits ..."
>>> Same solution here?
>>
>> Sure.
>
> OK - will do.
>
> Joe
>



From nobody Sat Jan 17 15:11:12 2015
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A681A89B5; Sat, 17 Jan 2015 15:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Auchq1Z0QzDm; Sat, 17 Jan 2015 15:11:05 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C079F1A6FD5; Sat, 17 Jan 2015 15:11:04 -0800 (PST)
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0HNAxn7026419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Jan 2015 18:10:59 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com t0HNAxn7026419
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1421536260; bh=G6dCZryoF3PIO0J96uJSNlRSbHk=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=Xelv10Nxf0htOR5cqJ0eyTCuHf1wX7EVRKVgy/jUlFdnD4pNmuzLqe1f1f4+/a66a 2HrvD22aaY29QiPNWZsUxlEmXoOUyGFkR8Ri8RpFu6RAVsVOrOpWblf4kKKsNZkFKU MleClLOfDrC1TsiPxmtBa8r+BwGSQ1K1z6PIe+Qw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com t0HNAxn7026419
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd51.lss.emc.com (RSA Interceptor); Sat, 17 Jan 2015 18:10:40 -0500
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0HNAnNE023905 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 17 Jan 2015 18:10:49 -0500
Received: from MXHUB203.corp.emc.com (10.253.68.29) by mxhub20.corp.emc.com (10.254.93.49) with Microsoft SMTP Server (TLS) id 8.3.327.1; Sat, 17 Jan 2015 18:10:48 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.208]) by MXHUB203.corp.emc.com ([10.253.68.29]) with mapi id 14.03.0195.001; Sat, 17 Jan 2015 18:10:48 -0500
From: "Black, David" <david.black@emc.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, Joe Touch <touch@isi.edu>
Thread-Topic: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
Thread-Index: AQHQE0Kfn+n1UWMmAEWD72ojfnwgBZyw0ngAgBLXGACAAAWtgIAAAs6AgAFm0wCAABATEA==
Date: Sat, 17 Jan 2015 23:10:47 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362E5919@MX104CL02.corp.emc.com>
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu> <54B9639F.7020905@isode.com> <54B965F9.6090704@isi.edu> <691f86d47ca683d48ab707d12e999534.squirrel@erg.abdn.ac.uk>
In-Reply-To: <691f86d47ca683d48ab707d12e999534.squirrel@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.96.43.91]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/JSwj_nR2wr_LYgpeEbr7E0o1-aw>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Jan 2015 23:11:08 -0000

> >> My concerns is that BCP are commonly used by ADs to enforce compliance=
.
> >> So I am wondering why this document is not just Informational?
> >
> > AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
> > protocol designers than would be an Informational doc.
> >
> Yes the document was marked BCP on 2011-01-26 after WG discussion and
> advice from our ADs, but this was not based on offering advice to IANA (a=
s
> in RFC 6335), but rather guidance to protocol and applications designers
> needing to use transport ports.

I concur with Gorry's summary, and believe that BCP status is appropriate.
I suggest teeing this concern (whether BCP vs. Informational is the right
status for this sort of guidance document) up to the IESG for a decision.

In its ordinary English (dictionary) meaning, "best current practice"
certainly applies to this draft.  OTOH, the IETF notion of BCP has a
rather specific meaning and some definite implications in practice.  FWIW,
Alexey is not the only person who's made note of that concern wrt this draf=
t.

In my view, the IESG owns the decision (and decision criteria) on what
should vs. should not be a BCP.  I think we should expand the draft writeup
to note this concern (BCP vs. Informational status) as one that needs IESG
attention and ask our ADs to ensure that it does get suitable IESG attentio=
n.

Much as I prefer to resolve open issues before IESG Evaluation, in this cas=
e,
I think the IESG needs to make a decision, and it is within reason for us t=
o
ask them to do so ;-).

Thanks,
--David (as Gorry's tsvwg WG co-chair)

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of gorry@erg.abdn.a=
c.uk
> Sent: Saturday, January 17, 2015 11:51 AM
> To: Joe Touch
> Cc: Alexey Melnikov; ietf@ietf.org; tsvwg@ietf.org
> Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt>
> (Recommendations for Transport Port Number Uses) to Best Current Practice
>=20
> HI,
>=20
> I added a little history in-line to help inform comments on the intended
> status.
>=20
> > Hi, Alexey,
> >
> > On 1/16/2015 11:16 AM, Alexey Melnikov wrote:
> >> Hi Joe,
> >>
> > ...
> >> My concerns is that BCP are commonly used by ADs to enforce compliance=
.
> >> So I am wondering why this document is not just Informational?
> >
> > AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
> > protocol designers than would be an Informational doc.
> >
> Yes the document was marked BCP on 2011-01-26 after WG discussion and
> advice from our ADs, but this was not based on offering advice to IANA (a=
s
> in RFC 6335), but rather guidance to protocol and applications designers
> needing to use transport ports
>=20
> Gorry
>=20
> > However, the way expert review and the appeals process already allows
> > ADs to either use BCPs or override them anyway, so I don't see this as
> > unduly constraining them. Besides, all sorts of docs - including
> > standards-track - are contradictory, so there's no one way to ensure
> > they're all followed.
> >
> > ...
> >>>> In 7.4:
> > ...
> >>>> Inserting "solely" before "by a browser" would address my concern.
> >>> Would "primarily" also work? It's hard to argue "solely" even for
> >>> conventional web access.
> >>
> >> Yes, "primarily" is actually better.
> >
> > OK. Will do.
> >
> >>>> In 7.4:
> >>>>
> >>>>     Note however that a new service might not be eligible for IANA
> >>>>     assignment of both an insecure and a secure variant of the same
> >>>>     service, and similarly IANA might be skeptical of an assignment
> >>>> for
> >>>>
> >>>> I don't think use of wording like "IANA might be skeptical" is corre=
ct
> >>>> here, because IANA doesn't define policy on this. IETF does. So let'=
s
> >>>> call things with right names and don't misuse "IANA" here.
> >>>
> >>> The document isn't written by IANA. We recommend to IANA, and IANA
> >>> makes
> >>> a decision that the IESG can override. I don't think it's outside the
> >>> scope of the doc to indicate this context.
> >>
> >> Actually I disagree. IANA is just following procedure prescribed by
> >> IETF. Experts are not really acting as advisors (although in practice
> >> there is always a dialogue, which is as it should be).
> >
> > IANA doesn't have to agree with expert reviewer recommendations. There
> > isn't anything binding that, though - as you note - there's a dialogue
> > and it's not an issue in practice.
> >
> >>> Would it be preferable to say that "applications asking for both...
> >>> might not be approved when..."?
> >>
> >> Yes.
> >
> > OK - will do.
> >
> >>>>     an insecure port number for a secure service. In both cases,
> >>>>     security of the service is compromised by adding the insecure po=
rt
> >>>>     number assignment.
> >>>>
> >>>> Similarly (in the same section): "IANA currently permits ..."
> >>> Same solution here?
> >>
> >> Sure.
> >
> > OK - will do.
> >
> > Joe
> >
>=20


From nobody Sat Jan 17 15:16:55 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFE8E1A8A84; Sat, 17 Jan 2015 15:16:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 mEgLiL24Iown; Sat, 17 Jan 2015 15:16:48 -0800 (PST)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C5011A8A1D; Sat, 17 Jan 2015 15:16:47 -0800 (PST)
Received: by mail-la0-f52.google.com with SMTP id hs14so23888366lab.11; Sat, 17 Jan 2015 15:16:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Wk17WR33kFeA12GMCgoh4GnqL9zU9Ti6MoYUQzqBC2A=; b=eItrspLOfuiK5gNk00OLjq8DQWSB4Az9QbnLrR25xNRv6roJYXFsWP4orrxHfDPzCl Svt0XCsHOU/7n1SOmG98D0SQXxkl1qy08ID8SKmoPUAWm5Ct0cku5YsTM5f3DIH3MK0u OHvS4FvvI7ahRHqaNP09BBsRcf8F1RjJl6PKPwmzXXEAb24vrhF5bOm44U3A+XIRATDp iHjg+FBWQXMPFT4JtPNOU7/QgnjVnYBkARplgIG9EmAG4C6Z9U7Hk3IOgIfI0FElthdv aOFIiNAcSEcIjZHv4i5JkCXoN2QWuh3ajRxrIYF7Hypcueaj/xrrSKlM/tIpU2xF8d7W eT0A==
MIME-Version: 1.0
X-Received: by 10.112.188.201 with SMTP id gc9mr16794585lbc.6.1421536606411; Sat, 17 Jan 2015 15:16:46 -0800 (PST)
Received: by 10.152.108.45 with HTTP; Sat, 17 Jan 2015 15:16:46 -0800 (PST)
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362E5919@MX104CL02.corp.emc.com>
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu> <54B9639F.7020905@isode.com> <54B965F9.6090704@isi.edu> <691f86d47ca683d48ab707d12e999534.squirrel@erg.abdn.ac.uk> <CE03DB3D7B45C245BCA0D243277949362E5919@MX104CL02.corp.emc.com>
Date: Sat, 17 Jan 2015 17:16:46 -0600
Message-ID: <CAKKJt-eBYdFsvweoLY3k8WzuN2kTXALonGdzwbepdXORT7PmZQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: multipart/alternative; boundary=001a11c3736675de9f050ce1489a
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/_gihodN38ymD6n-G85UTw7x_-wQ>
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, Alexey Melnikov <alexey.melnikov@isode.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Joe Touch <touch@isi.edu>
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Jan 2015 23:16:50 -0000

--001a11c3736675de9f050ce1489a
Content-Type: text/plain; charset=UTF-8

David and Gorry,

On Sat, Jan 17, 2015 at 5:10 PM, Black, David <david.black@emc.com> wrote:

> > >> My concerns is that BCP are commonly used by ADs to enforce
> compliance.
> > >> So I am wondering why this document is not just Informational?
> > >
> > > AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
> > > protocol designers than would be an Informational doc.
> > >
> > Yes the document was marked BCP on 2011-01-26 after WG discussion and
> > advice from our ADs, but this was not based on offering advice to IANA
> (as
> > in RFC 6335), but rather guidance to protocol and applications designers
> > needing to use transport ports.
>
> I concur with Gorry's summary, and believe that BCP status is appropriate.
> I suggest teeing this concern (whether BCP vs. Informational is the right
> status for this sort of guidance document) up to the IESG for a decision.
>
> In its ordinary English (dictionary) meaning, "best current practice"
> certainly applies to this draft.  OTOH, the IETF notion of BCP has a
> rather specific meaning and some definite implications in practice.  FWIW,
> Alexey is not the only person who's made note of that concern wrt this
> draft.
>
> In my view, the IESG owns the decision (and decision criteria) on what
> should vs. should not be a BCP.  I think we should expand the draft writeup
> to note this concern (BCP vs. Informational status) as one that needs IESG
> attention and ask our ADs to ensure that it does get suitable IESG
> attention.
>
> Much as I prefer to resolve open issues before IESG Evaluation, in this
> case,
> I think the IESG needs to make a decision, and it is within reason for us
> to
> ask them to do so ;-).
>
> Thanks,
> --David (as Gorry's tsvwg WG co-chair)
>


That sounds exactly right. I'll wait until you are happy with the shepherd
writeup before I proceed.

Spencer

--001a11c3736675de9f050ce1489a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">David and Gorry,<br><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Sat, Jan 17, 2015 at 5:10 PM, Black, David <span dir=
=3D"ltr">&lt;<a href=3D"mailto:david.black@emc.com" target=3D"_blank">david=
.black@emc.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><spa=
n class=3D"">&gt; &gt;&gt; My concerns is that BCP are commonly used by ADs=
 to enforce compliance.<br>
&gt; &gt;&gt; So I am wondering why this document is not just Informational=
?<br>
&gt; &gt;<br>
&gt; &gt; AFAIR, the WG wanted it to be BCP to be a stronger recommendation=
 to<br>
&gt; &gt; protocol designers than would be an Informational doc.<br>
&gt; &gt;<br>
&gt; Yes the document was marked BCP on 2011-01-26 after WG discussion and<=
br>
&gt; advice from our ADs, but this was not based on offering advice to IANA=
 (as<br>
&gt; in RFC 6335), but rather guidance to protocol and applications designe=
rs<br>
</span>&gt; needing to use transport ports.<br>
<br>
I concur with Gorry&#39;s summary, and believe that BCP status is appropria=
te.<br>
I suggest teeing this concern (whether BCP vs. Informational is the right<b=
r>
status for this sort of guidance document) up to the IESG for a decision.<b=
r>
<br>
In its ordinary English (dictionary) meaning, &quot;best current practice&q=
uot;<br>
certainly applies to this draft.=C2=A0 OTOH, the IETF notion of BCP has a<b=
r>
rather specific meaning and some definite implications in practice.=C2=A0 F=
WIW,<br>
Alexey is not the only person who&#39;s made note of that concern wrt this =
draft.<br>
<br>
In my view, the IESG owns the decision (and decision criteria) on what<br>
should vs. should not be a BCP.=C2=A0 I think we should expand the draft wr=
iteup<br>
to note this concern (BCP vs. Informational status) as one that needs IESG<=
br>
attention and ask our ADs to ensure that it does get suitable IESG attentio=
n.<br>
<br>
Much as I prefer to resolve open issues before IESG Evaluation, in this cas=
e,<br>
I think the IESG needs to make a decision, and it is within reason for us t=
o<br>
ask them to do so ;-).<br>
<br>
Thanks,<br>
--David (as Gorry&#39;s tsvwg WG co-chair)<br></blockquote><div><br></div><=
div>=C2=A0</div><div>That sounds exactly right. I&#39;ll wait until you are=
 happy with the shepherd writeup before I proceed.</div><div><br></div><div=
>Spencer=C2=A0</div></div><br></div></div>

--001a11c3736675de9f050ce1489a--


From nobody Mon Jan 19 01:02:33 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015C61AD355; Mon, 19 Jan 2015 01:02:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level: 
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] 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 jxNxEuLZ-x5n; Mon, 19 Jan 2015 01:02:29 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 834181AD338; Mon, 19 Jan 2015 01:02:27 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 875B51B00537; Mon, 19 Jan 2015 09:02:12 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 19 Jan 2015 09:02:16 -0000
Message-ID: <cb46e9b1a7aafed84df6177bb63462b8.squirrel@erg.abdn.ac.uk>
In-Reply-To: <CAKKJt-eBYdFsvweoLY3k8WzuN2kTXALonGdzwbepdXORT7PmZQ@mail.gmail.com>
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu> <54B9639F.7020905@isode.com> <54B965F9.6090704@isi.edu> <691f86d47ca683d48ab707d12e999534.squirrel@erg.abdn.ac.uk> <CE03DB3D7B45C245BCA0D243277949362E5919@MX104CL02.corp.emc.com> <CAKKJt-eBYdFsvweoLY3k8WzuN2kTXALonGdzwbepdXORT7PmZQ@mail.gmail.com>
Date: Mon, 19 Jan 2015 09:02:16 -0000
From: gorry@erg.abdn.ac.uk
To: "Spencer Dawkins at IETF" <spencerdawkins.ietf@gmail.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/hWGbp9J-_udEGjasCYdagMaL9p4>
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Joe Touch <touch@isi.edu>, Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 09:02:31 -0000

I submitted a new shepherd writeup, based on this and what I found on the
list.

Gorry

> David and Gorry,
>
> On Sat, Jan 17, 2015 at 5:10 PM, Black, David <david.black@emc.com> wrote:
>
>> > >> My concerns is that BCP are commonly used by ADs to enforce
>> compliance.
>> > >> So I am wondering why this document is not just Informational?
>> > >
>> > > AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
>> > > protocol designers than would be an Informational doc.
>> > >
>> > Yes the document was marked BCP on 2011-01-26 after WG discussion and
>> > advice from our ADs, but this was not based on offering advice to IANA
>> (as
>> > in RFC 6335), but rather guidance to protocol and applications
>> designers
>> > needing to use transport ports.
>>
>> I concur with Gorry's summary, and believe that BCP status is
>> appropriate.
>> I suggest teeing this concern (whether BCP vs. Informational is the
>> right
>> status for this sort of guidance document) up to the IESG for a
>> decision.
>>
>> In its ordinary English (dictionary) meaning, "best current practice"
>> certainly applies to this draft.  OTOH, the IETF notion of BCP has a
>> rather specific meaning and some definite implications in practice.
>> FWIW,
>> Alexey is not the only person who's made note of that concern wrt this
>> draft.
>>
>> In my view, the IESG owns the decision (and decision criteria) on what
>> should vs. should not be a BCP.  I think we should expand the draft
>> writeup
>> to note this concern (BCP vs. Informational status) as one that needs
>> IESG
>> attention and ask our ADs to ensure that it does get suitable IESG
>> attention.
>>
>> Much as I prefer to resolve open issues before IESG Evaluation, in this
>> case,
>> I think the IESG needs to make a decision, and it is within reason for
>> us
>> to
>> ask them to do so ;-).
>>
>> Thanks,
>> --David (as Gorry's tsvwg WG co-chair)
>>
>
>
> That sounds exactly right. I'll wait until you are happy with the shepherd
> writeup before I proceed.
>
> Spencer
>



From nobody Mon Jan 19 03:54:22 2015
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7991D1B2A3B; Mon, 19 Jan 2015 03:54:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 nUlNG46Cf3Hu; Mon, 19 Jan 2015 03:54:18 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id DDD331B2A3A; Mon, 19 Jan 2015 03:54:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1421668456; d=isode.com; s=selector; i=@isode.com; bh=amAAHG6ByLkCv7d9zAEO8/y5p4+wew/FJkm67hzA01U=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=jyRf24kU+9ap8q7VF06vF3JwJg0X8AhGUqOi7n9rCiL0rY3PwnI/24yC4LF5g3Mnju24aF z2urYzHIyiyLj7yp0N6XZJDEPc42CyiEWKYJmdDN3ikiyTsIkX50urSoFCKwxVob65WESo 4ZxMalTSqHM8sPlqYmwaA/YEOKhNYro=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <VLzwZgAKaCy1@waldorf.isode.com>; Mon, 19 Jan 2015 11:54:15 +0000
Message-ID: <54BCEFB1.8030802@isode.com>
Date: Mon, 19 Jan 2015 11:51:13 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: gorry@erg.abdn.ac.uk, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, "Black, David" <david.black@emc.com>, Joe Touch <touch@isi.edu>
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu> <54B9639F.7020905@isode.com> <54B965F9.6090704@isi.edu> <691f86d47ca683d48ab707d12e999534.squirrel@erg.abdn.ac.uk> <CE03DB3D7B45C245BCA0D243277949362E5919@MX104CL02.corp.emc.com> <CAKKJt-eBYdFsvweoLY3k8WzuN2kTXALonGdzwbepdXORT7PmZQ@mail.gmail.com> <cb46e9b1a7aafed84df6177bb63462b8.squirrel@erg.abdn.ac.uk>
In-Reply-To: <cb46e9b1a7aafed84df6177bb63462b8.squirrel@erg.abdn.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/oMOTSqVeofIf2VAs440pIZpjYIw>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 11:54:19 -0000

On 19/01/2015 09:02, gorry@erg.abdn.ac.uk wrote:
> I submitted a new shepherd writeup, based on this and what I found on the
> list.
Sounds fair. Thank you for discussing this further in the write-up.
> Gorry
>
>> David and Gorry,
>>
>> On Sat, Jan 17, 2015 at 5:10 PM, Black, David <david.black@emc.com> wrote:
>>
>>>>>> My concerns is that BCP are commonly used by ADs to enforce
>>> compliance.
>>>>>> So I am wondering why this document is not just Informational?
>>>>> AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
>>>>> protocol designers than would be an Informational doc.
>>>>>
>>>> Yes the document was marked BCP on 2011-01-26 after WG discussion and
>>>> advice from our ADs, but this was not based on offering advice to IANA
>>> (as
>>>> in RFC 6335), but rather guidance to protocol and applications
>>> designers
>>>> needing to use transport ports.
>>> I concur with Gorry's summary, and believe that BCP status is
>>> appropriate.
>>> I suggest teeing this concern (whether BCP vs. Informational is the
>>> right
>>> status for this sort of guidance document) up to the IESG for a
>>> decision.
>>>
>>> In its ordinary English (dictionary) meaning, "best current practice"
>>> certainly applies to this draft.  OTOH, the IETF notion of BCP has a
>>> rather specific meaning and some definite implications in practice.
>>> FWIW,
>>> Alexey is not the only person who's made note of that concern wrt this
>>> draft.
>>>
>>> In my view, the IESG owns the decision (and decision criteria) on what
>>> should vs. should not be a BCP.  I think we should expand the draft
>>> writeup
>>> to note this concern (BCP vs. Informational status) as one that needs
>>> IESG
>>> attention and ask our ADs to ensure that it does get suitable IESG
>>> attention.
>>>
>>> Much as I prefer to resolve open issues before IESG Evaluation, in this
>>> case,
>>> I think the IESG needs to make a decision, and it is within reason for
>>> us
>>> to
>>> ask them to do so ;-).
>>>
>>> Thanks,
>>> --David (as Gorry's tsvwg WG co-chair)
>>>
>>
>> That sounds exactly right. I'll wait until you are happy with the shepherd
>> writeup before I proceed.
>>
>> Spencer


From nobody Mon Jan 19 11:44:19 2015
Return-Path: <dwing@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 844901ACDEA for <tsvwg@ietfa.amsl.com>; Mon, 19 Jan 2015 11:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, 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 mp6lNy6wYlo3 for <tsvwg@ietfa.amsl.com>; Mon, 19 Jan 2015 11:44:14 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39C5C1B2C2D for <tsvwg@ietf.org>; Mon, 19 Jan 2015 11:44:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1003; q=dns/txt; s=iport; t=1421696655; x=1422906255; h=from:content-transfer-encoding:subject:message-id:date: to:mime-version; bh=rcKxQ/GnYo4jC7v5kk+sZUOxuy0vpllgAZmSAgUb65Y=; b=N7fj4F7McNIc1TlkSz44626tI5apKA1NtT2dMCaZWizgQdXlzwRQ1Rcv 0NsPib0XIi9XTQb2RFcKxeKiVYGTOJh1tYt6ja9G7vzzE3ybaYphVJxWH KURoKhL2S3toNnOCc/V7GiXCGaHQKFjl8GX3RKNZcUN268qNi7NRNS2UJ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFADpevVStJV2R/2dsb2JhbABbgwbPCEMBAQEBAX2PCasBo20LAQEBHpAWgwCBEwWJdY17hi+LeyKEDx2BNiSBGgEBAQ
X-IronPort-AV: E=Sophos;i="5.09,428,1418083200"; d="scan'208";a="114626358"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-1.cisco.com with ESMTP; 19 Jan 2015 19:43:51 +0000
Received: from [10.24.238.22] ([10.24.238.22]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t0JJhoeM031789 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <tsvwg@ietf.org>; Mon, 19 Jan 2015 19:43:51 GMT
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FFBC79D-AE0A-4B44-B11F-7A2D6EA00347@cisco.com>
Date: Mon, 19 Jan 2015 11:43:51 -0800
To: tsvwg@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/lZlK-rVhloqxY6Qx_MElwcnXhIk>
Subject: [tsvwg] sanity checking DTLS ICMP errors
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 19:44:17 -0000

To reduce the attack surface, TCP implementations have been validating =
ICMP error messages to be in-window (RFC5927).

On a thread over on RTCWEB with Michael T=FCxen, it seems DTLS-encrypted =
packets might benefit from a similar validation.  There are some fields =
early in the packet that might be useful for such validation,

      struct {
        ContentType type;
        ProtocolVersion version;
        uint16 epoch;                                     // New field
        uint48 sequence_number;                           // New field
        uint16 length;
        select (CipherSpec.cipher_type) {
          case block:  GenericBlockCipher;
        } fragment;
      } DTLSCiphertext;

however, both the Epoch and Sequence Number start at zero (unlike TCP's =
initial sequence number which has been random for nearly 20 years). =20


Do we want to validate ICMP error messages for DTLS packets?  If so, can =
DTLS have a randomized initial sequence number?

-d


From nobody Mon Jan 19 14:26:57 2015
Return-Path: <barryleiba@computer.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C641B2CF6; Mon, 19 Jan 2015 14:26:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 B3aW01D3K0Qw; Mon, 19 Jan 2015 14:26:39 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C5A561B2CF1; Mon, 19 Jan 2015 14:26:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Barry Leiba" <barryleiba@computer.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150119222638.5078.45177.idtracker@ietfa.amsl.com>
Date: Mon, 19 Jan 2015 14:26:38 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/5n_kUx-QxMvidDLCbAZzX5BFjqY>
Cc: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
Subject: [tsvwg] Barry Leiba's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 22:26:47 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree that Stephen's DISCUSS needs to be sorted out.

I've a couple of minor comments on a paragraph in Section 1:

   This encapsulation of SCTP over DTLS over or UDP or ICE/UDP (see
   [RFC5245]) can provide a NAT traversal solution together with
   confidentiality, source authentication, and integrity protected
   transfers.

Is there a protocol missing before the first "or", or does the first "or"
need to be deleted (the latter, I think)?

The phrase "together with" implies that something else is needed (as in
"X, together with Y, provides Z").  Does the sentence mean to say that
<this encapsulation> can provide [a NAT traversal solution that includes
confidentiality, source authentication, and integrity-protected
transfers]?  Or does it mean to say that <this encapsulation> can provide
a NAT traversal solution, as well as confidentiality, source
authentication, and integrity-protected transfers]?  I think it's one of
those.



From nobody Mon Jan 19 14:36:51 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 292D41B2CFB for <tsvwg@ietfa.amsl.com>; Mon, 19 Jan 2015 14:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gHGt7CLtHr-4 for <tsvwg@ietfa.amsl.com>; Mon, 19 Jan 2015 14:36:47 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EC7C1B2CF3 for <tsvwg@ietf.org>; Mon, 19 Jan 2015 14:36:47 -0800 (PST)
Received: from [192.168.1.200] (p508F3E81.dip0.t-ipconnect.de [80.143.62.129]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 14E4A1C104371; Mon, 19 Jan 2015 23:36:45 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5FFBC79D-AE0A-4B44-B11F-7A2D6EA00347@cisco.com>
Date: Mon, 19 Jan 2015 23:36:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <372D50B7-4AF4-41EC-A6E8-97E00C4F5FE8@lurchi.franken.de>
References: <5FFBC79D-AE0A-4B44-B11F-7A2D6EA00347@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/HzxnZ4aIwhorGGWJKUYrXptJfxM>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] sanity checking DTLS ICMP errors
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 22:36:49 -0000

> On 19 Jan 2015, at 20:43, =F0=9F=94=93Dan Wing <dwing@cisco.com> =
wrote:
>=20
> To reduce the attack surface, TCP implementations have been validating =
ICMP error messages to be in-window (RFC5927).
>=20
> On a thread over on RTCWEB with Michael T=C3=BCxen, it seems =
DTLS-encrypted packets might benefit from a similar validation. =20
Just to add some information:
Dan was asking why we couldn't just process incoming ICMP packets =
indicating that a packet
sent was too big by SCTP when running over DTLS. My point was that we =
can't the validation
of the verification tag as we do normally for SCTP. That is why we use =
PMTUD as described
in RFC4821 for
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-08
> There are some fields early in the packet that might be useful for =
such validation,
>=20
>      struct {
>        ContentType type;
>        ProtocolVersion version;
>        uint16 epoch;                                     // New field
>        uint48 sequence_number;                           // New field
>        uint16 length;
>        select (CipherSpec.cipher_type) {
>          case block:  GenericBlockCipher;
>        } fragment;
>      } DTLSCiphertext;
>=20
> however, both the Epoch and Sequence Number start at zero (unlike =
TCP's initial sequence number which has been random for nearly 20 =
years). =20
One difference is that the TCP initial sequence number is negotiated =
during the TCP handshake.
DTLS doesn't do this.
>=20
>=20
> Do we want to validate ICMP error messages for DTLS packets?  If so, =
can DTLS have a randomized initial sequence number?
At least you need to change the specification. So it is something one =
might consider when working on DTLS 1.3, I guess.

Best regards
Michael
>=20
> -d
>=20
>=20


From nobody Mon Jan 19 14:41:35 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F4D1B2D05; Mon, 19 Jan 2015 14:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 CiKq3eMR94fm; Mon, 19 Jan 2015 14:41:18 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF401B2CF9; Mon, 19 Jan 2015 14:41:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150119224118.1160.58499.idtracker@ietfa.amsl.com>
Date: Mon, 19 Jan 2015 14:41:18 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/0bCprcRPMxOAVDyEiHf4AValKbc>
Cc: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
Subject: [tsvwg] Stephen Farrell's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 22:41:24 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


- I had a discuss on DTLS1.0 as the MTI. I'm told that 
was decided by the WG last Nov in consultation with 
WebRTC and TLS WG chairs, so while I'd prefer to
see DTLS1.2 as the MTI, I've cleared the DISCUSS.

- Figure 1: Couldn't ICE/UDP be somewhat confusing for
someone unaware that ICE is more of an algorithm than a
wire protocol? Might be nice to clarify that here in
the intro. (If you want to be nice, if you don't that's
ok too and can be the right decision.)

- section 3: Isn't "complete SCTP packet" a teeny bit
ambiguous? It could mean including the IP and other
lower headers but I guess you do not. But that's a nit
since it's probably clear enough that you don't put an
IP or layer 2 header into the DTLS payload:-)

- Given heartbleed, and the use here of RFC6520 I think
some note of that famous implementation bug would be
wise. Just to a pointer to how to not have that
problem. But it's not a protocol bug so I'm not trying
to insist, i.e. no need for us to argue the toss on
this:-)

- I'm also wondering if the text here on 6520 is
sufficiently clear given this week's discussion of that
on the rtcweb list. (I'm not on tsvwg@ so would
appreciate an update on how the thread [1] pans out on
the tsvwg list before we approve this.)

  [1] https://www.ietf.org/mail-archive/web/rtcweb/current/msg14069.html



From nobody Mon Jan 19 14:55:41 2015
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 240BA1B2D0A for <tsvwg@ietfa.amsl.com>; Mon, 19 Jan 2015 14:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 YHrOhY4yxFTs for <tsvwg@ietfa.amsl.com>; Mon, 19 Jan 2015 14:55:23 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09DA71B2CF1 for <tsvwg@ietf.org>; Mon, 19 Jan 2015 14:55:22 -0800 (PST)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0JMtJDC014454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 19 Jan 2015 17:55:21 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com t0JMtJDC014454
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1421708121; bh=2/mhE5aUJRxIWIHRF35NW9A0NX0=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=Ogxig1ZtzIfRttIrz4JfooYq5bRNyP3NRs9BwwEcXHB8Txk4Bh7PEvN003LdEK40M Vp+X51JxrWBgE4ojEWVF88ueZg145Ivw/mlrmSxtzqhJBUbRKagMVzYj9hBUThPnl8 7l1zS27SnDT9268qYtpvIx/BxOHsUGXJWy779DOk=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com t0JMtJDC014454
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd01.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Mon, 19 Jan 2015 17:54:37 -0500
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0JMt9LP029025 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Mon, 19 Jan 2015 17:55:10 -0500
Received: from MXHUB203.corp.emc.com (10.253.68.29) by mxhub24.corp.emc.com (128.222.70.136) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 19 Jan 2015 17:55:09 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.208]) by MXHUB203.corp.emc.com ([10.253.68.29]) with mapi id 14.03.0195.001; Mon, 19 Jan 2015 17:55:08 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Re Stephen Farrell's Discuss on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with DISCUSS and COMMENT)
Thread-Index: AdA0NHib7FaS+y1cTUq5Rh1C9IHrrgAK3BuAAAlF9VA=
Date: Mon, 19 Jan 2015 22:55:08 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362E7915@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949362E77AC@MX104CL02.corp.emc.com> <jiorx0.nig3co.2vaesb-qmf@mercury.scss.tcd.ie>
In-Reply-To: <jiorx0.nig3co.2vaesb-qmf@mercury.scss.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.73]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/lM5_ZHVMRFm6d9xb5COZwpdl3_k>
Subject: [tsvwg] FW: Re Stephen Farrell's Discuss on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with DISCUSS and COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 22:55:31 -0000

SGVyZSBhcmUgdGhlIGRldGFpbHMgb24gU3RlcGhlbidzIG9yaWdpbmFsIERpc2N1c3MgYW5kIHdo
YXQgbGVhZCB0byBjbGVhcmluZyBpdCAuLi4gVGhhbmtzLCAtLURhdmlkDQoNCi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllIFttYWlsdG86
c3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZV0gDQpTZW50OiBNb25kYXksIEphbnVhcnkgMTksIDIw
MTUgNToyMCBQTQ0KVG86IEJsYWNrLCBEYXZpZA0KQ2M6IHRzdndnLWNoYWlyc0B0b29scy5pZXRm
Lm9yZzsgcnRjd2ViLWNoYWlyc0B0b29scy5pZXRmLm9yZzsgZHJhZnQtaWV0Zi10c3Z3Zy1zY3Rw
LWR0bHMtZW5jYXBzQHRvb2xzLmlldGYub3JnOyBpZXNnQGlldGYub3JnDQpTdWJqZWN0OiBSZTog
UmUgU3RlcGhlbiBGYXJyZWxsJ3MgRGlzY3VzcyBvbiBkcmFmdC1pZXRmLXRzdndnLXNjdHAtZHRs
cy1lbmNhcHMtMDg6ICh3aXRoIERJU0NVU1MgYW5kIENPTU1FTlQpDQoNCkFoIHRoYW5rcyAtIGlm
IGl0cyB0aGF0IHJlY2VudCB3ZSdyZSBkb25lLiBJJ2xsIGNsZWFyIGluIGEgYml0LiANCg0KUw0K
DQoNCk9uIE1vbiBKYW4gMTkgMjI6MDg6MzYgMjAxNSBHTVQsIEJsYWNrLCBEYXZpZCB3cm90ZToN
Cj4gU3RlcGhlbiwNCj4gDQo+IFlvdSB3cml0ZToNCj4gDQo+IC0tLS0tLS0tLS0tLS0NCj4gCUkn
bGwgY2xlYXIgb25jZSB3ZSd2ZSBjaGVja2VkIG9uIHRoaXMuIFNlY3Rpb24gNSBzYXlzDQo+IAlE
VExTMS4wIChmcm9tIDIwMDYpIGlzIE1USSBhbmQgRFRMUzEuMiAoMjAxMikgaXMgYQ0KPiAJU0hP
VUxELiBJIGNvdWxkIGltYWdpbmUgdGhhdCBiZWluZyByZWFzb25hYmxlIHdoZW4NCj4gCURUTFMx
LjIgd2FzIG5ld2lzaCwgc2F5IHdoZW4gdGhpcyB3b3JrIHdhcyBnZXR0aW5nDQo+IAlzdGFydGVk
IDIgeWVhcnMgYWdvLCBidXQgbm93IGEgY291cGxlIG9mIHllYXJzIGhhdmUNCj4gCXBhc3NlZCwg
aXQgbWlnaHQgd2VsbCBiZSBqdXN0IGZpbmUgdG8gcmVxdWlyZSBEVExTMS4yIC0NCj4gCWEgbG90
IGhhcyBoYXBwZW5lZCBzaW5jZSBhbmQgVExTMS4yIGRlcGxveW1lbnQgaXMgbm93DQo+IAlmYXIg
YWhlYWQgb2Ygd2hlcmUgaXQgd2FzIGluIDIwMTIsIGFuZCBtb3N0IHNwZWNzIGhhdmUNCj4gCXRl
bmRlZCB0byBpbmNsdWRlIHRleHQgbGlrZSB0aGlzIGJlY2F1c2Ugc29tZQ0KPiAJaW1wbGVtZW50
ZXJzIG9ubHkgaGFkIHRoZSBvbGRlciBUTFMgdmVyc2lvbi4gU28gdGhlDQo+IAlESVNDVVNTIGlz
IC0gaXMgdGhlIDkgeWVhciBvbGQgUkZDIHN0aWxsIG5lZWRlZCBhcyBNVEkNCj4gCS0gY2FuIHdl
IG5vdCBqdXN0IHNheSB0byB1c2UgMS4yIG5vdz8gIChOb3RlOiBzaW5jZQ0KPiAJdGhpcyBpcyBz
b3J0LW9mIGEgV2ViUlRDIHNwZWMsIEkgdGhpbmsgaXQncyB3b3J0aA0KPiAJcXVpY2tseSByZS12
aXNpdGluZyB0aGlzIHF1ZXN0aW9uIG5vdyB0byBiZSBzdXJlIHdlJ3JlDQo+IAl0YWtpbmcgdGhl
IHJpZ2h0IGFwcHJvYWNoLCBhcyB0aGUgYW5zd2VyIHdlIHBpY2sgaGVyZQ0KPiAJaXMgcXVpdGUg
bGlrZWx5IHRvIGJlIGZvbGxvd2VkIGJ5IG90aGVyIFdlYlJUQyBkb2NzDQo+IAlvdmVyIHRoZSBu
ZXh0IHllYXIgb3Igc28uIEkgdGhpbmsgdGhpcyBpcyB0aGUgZmlyc3QNCj4gCXJlbGV2YW50IFdl
YlJUQyBwcm90b2NvbCBzcGVjIHdpdGggdGhpcyBiaXQgb2YgdGV4dA0KPiAJaXNuJ3QgaXQ/ICBB
cG9sb2dpZXMgdG8gdGhlIGF1dGhvcnMgb2YgdGhpcyBvbmUgZm9yDQo+IAlsYW5kaW5nIHRoZSBk
aXNjdXNzIG9uIHRoZW06LSkNCj4gLS0tLS0tLS0tLS0tLQ0KPiANCj4gQW5kIEkgbGlrZXdpc2Ug
YXBvbG9naXplIGZvciBib3VuY2luZyB0aGlzIG9uZSBiYWNrIG9udG8geW91IC4uLg0KPiBiZWNh
dXNlIHlvdXIgaW5mZXJlbmNlIG9uIHdoYXQgaGFwcGVuZWQgaGVyZSBpcyBjb3JyZWN0IDotKS4N
Cj4gDQo+IFRoZSBEVExTIHZlcnNpb24gd2FzICp0aGUqIGJsb2NraW5nIGlzc3VlIGhvbGRpbmcg
dXAgdGhpcyBkcmFmdCwgYW5kDQo+IHRoZSB0ZXh0IHRoYXQgeW91IGFyZSBsb29raW5nIGF0IGlz
IHRoZSByZXN1bHQgb2YgYW4gUlRDV0VCIFdHIGRlY2lzaW9uDQo+IGluIEhvbm9sdWx1IC0gU2Vh
biBUdXJuZXIgZ2V0cyB0aGUgY3JlZGl0IChhbmQgb3VyIHRoYW5rcykgZm9yIG1ha2luZw0KPiB0
aGF0IGRlY2lzaW9uIGhhcHBlbiAoYW5kIHRoZXJlYnkgdW5ibG9ja2luZyB0aGlzIGRyYWZ0KS4N
Cj4gDQo+IFBsZWFzZSB3b3JrIHRoaXMgRGlzY3VzcyBvdXQgd2l0aCB0aGUgUlRDV0VCIFdHIGNo
YWlycyBhbmQvb3IgUkFJDQo+IEFEcyAuLi4gYW5kIGRvIGxldCB1cyBrbm93IHdoYXQgdGhlIGZp
bmFsIGFuc3dlciBpcyA7LSkuDQo+IA0KPiBUaGFua3MsDQo+IC0tRGF2aWQgKFRTVldHIFdHIGNv
LWNoYWlyLCB3aG8gd2FzIGluIEhvbm9sdWx1KQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IERhdmlkIEwuIEJsYWNrLCBEaXN0aW5ndWlz
aGVkIEVuZ2luZWVyDQo+IEVNQyBDb3Jwb3JhdGlvbiwgMTc2IFNvdXRoIFN0LiwgSG9wa2ludG9u
LCBNQSAgMDE3NDgNCj4gKzEgKDUwOCkgMjkzLTc5NTMgICAgICAgICAgICAgRkFYOiArMSAoNTA4
KSAyOTMtNzc4Ng0KPiBkYXZpZC5ibGFja0BlbWMuY29tICAgICAgICBNb2JpbGU6ICsxICg5Nzgp
IDM5NC03NzU0DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj4gDQo+DQo=


From nobody Tue Jan 20 09:07:27 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D691B2B0C for <tsvwg@ietfa.amsl.com>; Tue, 20 Jan 2015 09:07:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 2BoZ6bBHD1Gz; Tue, 20 Jan 2015 09:06:49 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 81F401B2ADC; Tue, 20 Jan 2015 09:06:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150120170636.15674.37984.idtracker@ietfa.amsl.com>
Date: Tue, 20 Jan 2015 09:06:36 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/BOSlzfFZ8eSmVrhYvYxCiuhXEE0>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-08.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 17:07:03 -0000

IANA review state changed to IANA OK - No Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


From nobody Tue Jan 20 13:34:10 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C27541A0021; Tue, 20 Jan 2015 13:34:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 hsBn7Kdm2cf7; Tue, 20 Jan 2015 13:34:05 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A04B1A0015; Tue, 20 Jan 2015 13:34:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150120213405.4542.64355.idtracker@ietfa.amsl.com>
Date: Tue, 20 Jan 2015 13:34:05 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/bjDMxW7TLt-D63SxI7rn9_Kv1io>
Cc: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
Subject: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 21:34:07 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

 The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
   support the most recently published version of DTLS, which is DTLS
   1.2 [RFC6347] as of December 2014.

December 2014 is wrong.



From nobody Tue Jan 20 13:48:05 2015
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE9B1A0027; Tue, 20 Jan 2015 13:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 XVTxvxlP_TzZ; Tue, 20 Jan 2015 13:47:56 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7E4E1A0022; Tue, 20 Jan 2015 13:47:56 -0800 (PST)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0KLlnlb017674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2015 16:47:51 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com t0KLlnlb017674
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1421790471; bh=lX6nC8Dv3YDILPPbBQBPUBlaGP4=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=KMK6cNLgLd3E5GEFwmYSASHA76vF8qgBO5ZZgKszJHrtsaahAyZh3Q3I1LAP8d6Cp o3QYTbUD0lByaW1EUPyTegGAg5nEeyCiCV4e3JR3xQTPNPCog6wR0f9Wxp4XfOenaY 094uTWSuQBYJqW41gg12zg9HK7x2OH8/hCLmC7Cw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com t0KLlnlb017674
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd56.lss.emc.com (RSA Interceptor); Tue, 20 Jan 2015 16:45:44 -0500
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0KLlWpM015958 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 20 Jan 2015 16:47:33 -0500
Received: from MXHUB210.corp.emc.com (10.253.68.36) by mxhub01.corp.emc.com (10.254.141.103) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 20 Jan 2015 16:47:32 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.208]) by MXHUB210.corp.emc.com ([10.253.68.36]) with mapi id 14.03.0195.001; Tue, 20 Jan 2015 16:47:32 -0500
From: "Black, David" <david.black@emc.com>
To: Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
Thread-Topic: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
Thread-Index: AQHQNPjfXezGEief1UKql1cJy8uz1ZzJiMkg
Date: Tue, 20 Jan 2015 21:47:31 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362E97F4@MX104CL02.corp.emc.com>
References: <20150120213405.4542.64355.idtracker@ietfa.amsl.com>
In-Reply-To: <20150120213405.4542.64355.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.73]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/dUnJX0-kobLAAwFl9vxuEsJQTO4>
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org>
Subject: Re: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 21:47:58 -0000

QmVub2l0LA0KDQo+ICBUaGUgRFRMUyBpbXBsZW1lbnRhdGlvbiBNVVNUIHN1cHBvcnQgRFRMUyAx
LjAgW1JGQzQzNDddIGFuZCBTSE9VTEQNCj4gICAgc3VwcG9ydCB0aGUgbW9zdCByZWNlbnRseSBw
dWJsaXNoZWQgdmVyc2lvbiBvZiBEVExTLCB3aGljaCBpcyBEVExTDQo+ICAgIDEuMiBbUkZDNjM0
N10gYXMgb2YgRGVjZW1iZXIgMjAxNC4NCj4gDQo+IERlY2VtYmVyIDIwMTQgaXMgd3JvbmcuDQoN
Ck5pdHBpY2sgZGVwYXJ0bWVudCA7LSkgLSBhcyBvZiBEZWMgMjAxNCwgRFRMUyAxLjIgW1JGQzYz
NDddIGlzIHRoZSBtb3N0DQpyZWNlbnRseSBwdWJsaXNoZWQgKGFzIGFuIFJGQykgdmVyc2lvbiBv
ZiBEVExTLCBldmVuIHRob3VnaCB0aGF0IFJGQyB3YXMNCnB1Ymxpc2hlZCBpbiBKYW4gMjAxMiwg
c28gdGhlIHF1b3RlZCB0ZXh0IGlzIGFjdHVhbGx5IGNvcnJlY3QgOy0pLg0KDQpOb25ldGhlbGVz
cywgaGVyZSdzIGEgY2xlYXJlciBzdWdnZXN0aW9uOg0KDQpPTEQNCiAgICAgc3VwcG9ydCB0aGUg
bW9zdCByZWNlbnRseSBwdWJsaXNoZWQgdmVyc2lvbiBvZiBEVExTLCB3aGljaCBpcyBEVExTDQog
ICAgIDEuMiBbUkZDNjM0N10gYXMgb2YgRGVjZW1iZXIgMjAxNC4NCk5FVw0KICAgICBzdXBwb3J0
IHRoZSBtb3N0IHJlY2VudGx5IHB1Ymxpc2hlZCB2ZXJzaW9uIG9mIERUTFMsIHdoaWNoIHdhcyBE
VExTDQogICAgIDEuMiBbUkZDNjM0N10gd2hlbiB0aGlzIFJGQyB3YXMgcHVibGlzaGVkIChYWFhY
WFhYWFggMjAxNSkuDQoNCiAgICAgUkZDIEVkaXRvcjogcGxlYXNlIGZpbGwgaW4gcHVibGljYXRp
b24gbW9udGggb2YgdGhpcyBSRkMgYW5kIGVuc3VyZQ0KICAgICB0aGF0IGNvcnJlY3RuZXNzIG9m
IHRoZSBhYm92ZSBzdGF0ZW1lbnQgaXMgY2hlY2tlZCBkdXJpbmcgQVVUSDQ4Lg0KRU5EDQoNClRo
YW5rcywNCi0tRGF2aWQNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206
IHRzdndnIFttYWlsdG86dHN2d2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEJlbm9p
dCBDbGFpc2UNCj4gU2VudDogVHVlc2RheSwgSmFudWFyeSAyMCwgMjAxNSA0OjM0IFBNDQo+IFRv
OiBUaGUgSUVTRw0KPiBDYzogZ29ycnlAZXJnLmFiZG4uYWMudWs7IHRzdndnLWNoYWlyc0B0b29s
cy5pZXRmLm9yZzsgdHN2d2dAaWV0Zi5vcmc7IGRyYWZ0LQ0KPiBpZXRmLXRzdndnLXNjdHAtZHRs
cy1lbmNhcHMuYWxsQHRvb2xzLmlldGYub3JnDQo+IFN1YmplY3Q6IFt0c3Z3Z10gQmVub2l0IENs
YWlzZSdzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLXRzdndnLXNjdHAtZHRscy0NCj4gZW5j
YXBzLTA4OiAod2l0aCBDT01NRU5UKQ0KPiANCj4gQmVub2l0IENsYWlzZSBoYXMgZW50ZXJlZCB0
aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCj4gZHJhZnQtaWV0Zi10c3Z3Zy1zY3Rw
LWR0bHMtZW5jYXBzLTA4OiBObyBPYmplY3Rpb24NCj4gDQo+IFdoZW4gcmVzcG9uZGluZywgcGxl
YXNlIGtlZXAgdGhlIHN1YmplY3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbA0KPiBlbWFp
bCBhZGRyZXNzZXMgaW5jbHVkZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJlZSB0
byBjdXQgdGhpcw0KPiBpbnRyb2R1Y3RvcnkgcGFyYWdyYXBoLCBob3dldmVyLikNCj4gDQo+IA0K
PiBQbGVhc2UgcmVmZXIgdG8gaHR0cDovL3d3dy5pZXRmLm9yZy9pZXNnL3N0YXRlbWVudC9kaXNj
dXNzLWNyaXRlcmlhLmh0bWwNCj4gZm9yIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQgSUVTRyBESVND
VVNTIGFuZCBDT01NRU5UIHBvc2l0aW9ucy4NCj4gDQo+IA0KPiBUaGUgZG9jdW1lbnQsIGFsb25n
IHdpdGggb3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZvdW5kIGhlcmU6DQo+IGh0dHA6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10c3Z3Zy1zY3RwLWR0bHMtZW5j
YXBzLw0KPiANCj4gDQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IENPTU1FTlQ6DQo+IC0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NCj4gDQo+ICBUaGUgRFRMUyBpbXBsZW1lbnRhdGlvbiBNVVNUIHN1cHBvcnQgRFRMUyAx
LjAgW1JGQzQzNDddIGFuZCBTSE9VTEQNCj4gICAgc3VwcG9ydCB0aGUgbW9zdCByZWNlbnRseSBw
dWJsaXNoZWQgdmVyc2lvbiBvZiBEVExTLCB3aGljaCBpcyBEVExTDQo+ICAgIDEuMiBbUkZDNjM0
N10gYXMgb2YgRGVjZW1iZXIgMjAxNC4NCj4gDQo+IERlY2VtYmVyIDIwMTQgaXMgd3JvbmcuDQo+
IA0KDQo=


From nobody Tue Jan 20 13:56:58 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F94D1A0033; Tue, 20 Jan 2015 13:56:55 -0800 (PST)
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 0pxEAKssI82J; Tue, 20 Jan 2015 13:56:53 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D765D1A0027; Tue, 20 Jan 2015 13:56:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2619; q=dns/txt; s=iport; t=1421791012; x=1423000612; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=t7z7fwkGLrSI9f+itzCX3mYa68A6sY6OFt2lRu6mH+I=; b=dQGBB4eB9gkvzEvAIQSgpM53YXUfoAiIf0IV0xviIMjrN03dqfNo9CQR AsiT9L++tEoOnxFH4Uh+ICJNRvT8ItirusygxE/NPHmJTfCTjnaDVz3IR N0UZ85pvREdFrX4tfMDgpBZZsSRXDi7i6QTizb0R7BiSVmgetgD535D9y 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArsEAAvOvlStJssW/2dsb2JhbABbg1hYgwe5eok8hXECgWwBAQEBAX2EDAEBAQQjFUABDAQLEQQBAQMCBRYIAwICCQMCAQIBNAkIBgEMAQUCAQEFiCMNvEKUUgEBAQEBAQEBAQEBAQEBAQEBAQEBAReBIY1rCxEBUAcGgmKBQQEEhTqMZoVQgRQ2gkaCHyGLWiKCMoE9PTEBgQuBNwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,437,1418083200"; d="scan'208";a="315462470"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 20 Jan 2015 21:56:49 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t0KLun6p018788; Tue, 20 Jan 2015 21:56:49 GMT
Message-ID: <54BECF21.5000806@cisco.com>
Date: Tue, 20 Jan 2015 22:56:49 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>, The IESG <iesg@ietf.org>
References: <20150120213405.4542.64355.idtracker@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362E97F4@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362E97F4@MX104CL02.corp.emc.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/v-19usCJNHJ60tjXuvXfcLMRgXo>
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org>
Subject: Re: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 21:56:55 -0000

Hi David,

Do what's right/what you want. I believe we have spent enough time 
already on this one :-)

Regards, 
Benoit-who-filed-a-stupid-editorial-comment-to-show-the-world-he-read-the-draft.
> Benoit,
>
>>   The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
>>     support the most recently published version of DTLS, which is DTLS
>>     1.2 [RFC6347] as of December 2014.
>>
>> December 2014 is wrong.
> Nitpick department ;-) - as of Dec 2014, DTLS 1.2 [RFC6347] is the most
> recently published (as an RFC) version of DTLS, even though that RFC was
> published in Jan 2012, so the quoted text is actually correct ;-).
>
> Nonetheless, here's a clearer suggestion:
>
> OLD
>       support the most recently published version of DTLS, which is DTLS
>       1.2 [RFC6347] as of December 2014.
> NEW
>       support the most recently published version of DTLS, which was DTLS
>       1.2 [RFC6347] when this RFC was published (XXXXXXXXX 2015).
>
>       RFC Editor: please fill in publication month of this RFC and ensure
>       that correctness of the above statement is checked during AUTH48.
> END
>
> Thanks,
> --David
>
>
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Benoit Claise
>> Sent: Tuesday, January 20, 2015 4:34 PM
>> To: The IESG
>> Cc: gorry@erg.abdn.ac.uk; tsvwg-chairs@tools.ietf.org; tsvwg@ietf.org; draft-
>> ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
>> Subject: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-
>> encaps-08: (with COMMENT)
>>
>> Benoit Claise has entered the following ballot position for
>> draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>>   The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
>>     support the most recently published version of DTLS, which is DTLS
>>     1.2 [RFC6347] as of December 2014.
>>
>> December 2014 is wrong.
>>


From nobody Thu Jan 22 00:35:02 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB7E41A01EA for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 00:35:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.221
X-Spam-Level: *
X-Spam-Status: No, score=1.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 sJwqrH8RIQqC for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 00:34:59 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D85FD1A01D8 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 00:34:58 -0800 (PST)
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id A2F7427818D for <tsvwg@ietf.org>; Thu, 22 Jan 2015 17:34:56 +0900 (JST)
Received: by mail-we0-f171.google.com with SMTP id q58so350687wes.2 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 00:34:54 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.203.199 with SMTP id ks7mr241825wjc.105.1421915694335; Thu, 22 Jan 2015 00:34:54 -0800 (PST)
Received: by 10.194.187.48 with HTTP; Thu, 22 Jan 2015 00:34:54 -0800 (PST)
In-Reply-To: <372D50B7-4AF4-41EC-A6E8-97E00C4F5FE8@lurchi.franken.de>
References: <5FFBC79D-AE0A-4B44-B11F-7A2D6EA00347@cisco.com> <372D50B7-4AF4-41EC-A6E8-97E00C4F5FE8@lurchi.franken.de>
Date: Thu, 22 Jan 2015 00:34:54 -0800
Message-ID: <CAO249ycaf8Q-AyTcp4cx3xhocyNzPEZzVO148XQfBJwhiKjWSw@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: multipart/alternative; boundary=047d7b6d9bf2dc8fca050d398b4a
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/sT7-eg3v_eHDDyoW-GuvMhT-Gcc>
Cc: tsvwg <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [tsvwg] sanity checking DTLS ICMP errors
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 08:35:00 -0000

--047d7b6d9bf2dc8fca050d398b4a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 19, 2015 at 2:36 PM, Michael Tuexen <
Michael.Tuexen@lurchi.franken.de> wrote:

> > On 19 Jan 2015, at 20:43, =F0=9F=94=93Dan Wing <dwing@cisco.com> wrote:
> >
> > To reduce the attack surface, TCP implementations have been validating
> ICMP error messages to be in-window (RFC5927).
> >
> > On a thread over on RTCWEB with Michael T=C3=BCxen, it seems DTLS-encry=
pted
> packets might benefit from a similar validation.
> Just to add some information:
> Dan was asking why we couldn't just process incoming ICMP packets
> indicating that a packet
> sent was too big by SCTP when running over DTLS. My point was that we
> can't the validation
> of the verification tag as we do normally for SCTP. That is why we use
> PMTUD as described
> in RFC4821 for
> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-08


Sorry if I miss something..
I'm just curious after reading the following texts.

 Incoming ICMP or ICMPv6 messages can't be processed by the SCTP
   layer, since there is no way to identify the corresponding
   association.


If the socket used for UDP encap is connected and if only one SCTP
association over DTLS is mapped to the socket, is it still impossible for
SCTP layer to know if it receives ICMP errors?

Thanks,
--
Yoshi

--047d7b6d9bf2dc8fca050d398b4a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jan 19, 2015 at 2:36 PM, Michael Tuexen <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:Michael.Tuexen@lurchi.franken.de" target=3D"_blank">Michael.Tu=
exen@lurchi.franken.de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>&gt;=
 On 19 Jan 2015, at 20:43, =F0=9F=94=93Dan Wing &lt;<a href=3D"mailto:dwing=
@cisco.com" target=3D"_blank">dwing@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; To reduce the attack surface, TCP implementations have been validating=
 ICMP error messages to be in-window (RFC5927).<br>
&gt;<br>
&gt; On a thread over on RTCWEB with Michael T=C3=BCxen, it seems DTLS-encr=
ypted packets might benefit from a similar validation.<br>
</span>Just to add some information:<br>
Dan was asking why we couldn&#39;t just process incoming ICMP packets indic=
ating that a packet<br>
sent was too big by SCTP when running over DTLS. My point was that we can&#=
39;t the validation<br>
of the verification tag as we do normally for SCTP. That is why we use PMTU=
D as described<br>
in RFC4821 for<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-08"=
 target=3D"_blank">http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-en=
caps-08</a></blockquote><div><br></div><div>Sorry if I miss something..=C2=
=A0</div><div>I&#39;m just curious after reading the following texts.<br></=
div><div><br></div><div><pre class=3D"" style=3D"font-size:1em;margin-top:0=
px;margin-bottom:0px;color:rgb(0,0,0)"> Incoming ICMP or ICMPv6 messages ca=
n&#39;t be processed by the SCTP
   layer, since there is no way to identify the corresponding
   association. </pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px=
;margin-bottom:0px;color:rgb(0,0,0)"><br></pre></div><div>If the socket use=
d for UDP encap is connected and if only one SCTP association over DTLS is =
mapped to the socket, is it still impossible for SCTP layer to know if it r=
eceives ICMP errors? =C2=A0</div><div><br></div><div>Thanks,</div><div>--<b=
r></div><div>Yoshi=C2=A0</div></div></div></div>

--047d7b6d9bf2dc8fca050d398b4a--


From nobody Thu Jan 22 10:16:30 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDCA1ACEF7 for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 10:16:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 3U1X3zC02s8S; Thu, 22 Jan 2015 10:16:28 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E4C1ACEAA; Thu, 22 Jan 2015 10:16:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150122181627.5439.5283.idtracker@ietfa.amsl.com>
Date: Thu, 22 Jan 2015 10:16:27 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/dV6rQI_IGEbOpIWQ09A1gaZT_4Y>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-08.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 18:16:29 -0000

IESG state changed to Approved-announcement to be sent::Revised I-D Needed from IESG Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


From nobody Thu Jan 22 10:34:52 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0DD41AD0C4 for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 10:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 YEbDQaEg0SMk for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 10:34:37 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (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 433201AD0C7 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 10:34:37 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id pv20so3262955lab.7 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 10:34:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+BUEW71Xc2OvdJcipPkSIhpqlgl6rZwu8TrfoanmHAw=; b=vJ0FYqttWDLkDYIwJKY2HmmwvQOKb4onakrLKUB+oVrq/qB7y2dheu8rJseKo3YTAW WECEn3i4s94XtH907n7zTSTEupJaQtjswtM185yKHV4xCqtGo1BvzdQNUP39J5VMHKdI VLkKV6dX3sapVZ2Rvtx0xviTKHboGVFY3nk435kOYugLd4QWdgPwGB+7j0/QGufgi0Kf qjaIeX4dIwUXs/hc2hLq6QMZE+2M1WxvkC3vPRIaoa19kolKMHARwk1WRWC1YXoH7uYr LyLoVvhbapkjmkxeuXAz3YwYDzDU5DBuaehRGVcyc0nB/yBm+Fvgsc6chd9NGR5VCKQ6 FiBw==
MIME-Version: 1.0
X-Received: by 10.112.72.197 with SMTP id f5mr3225451lbv.21.1421951675728; Thu, 22 Jan 2015 10:34:35 -0800 (PST)
Received: by 10.152.1.6 with HTTP; Thu, 22 Jan 2015 10:34:35 -0800 (PST)
In-Reply-To: <20150122181627.5439.5283.idtracker@ietfa.amsl.com>
References: <20150122181627.5439.5283.idtracker@ietfa.amsl.com>
Date: Thu, 22 Jan 2015 12:34:35 -0600
Message-ID: <CAKKJt-e-+HvmRYyyA5+=NNv1DV8Ek8o=LVmV1SH42jYQJh2QTA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary=001a11c23d8a85088f050d41ec93
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/HyHvoKF5XoNO8teraHPPSKdUZ7w>
Cc: "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
Subject: Re: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-08.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 18:34:42 -0000

--001a11c23d8a85088f050d41ec93
Content-Type: text/plain; charset=UTF-8

Hi, Gorry,

On Thu, Jan 22, 2015 at 12:16 PM, IETF Secretariat <
ietf-secretariat-reply@ietf.org> wrote:

> IESG state changed to Approved-announcement to be sent::Revised I-D Needed
> from IESG Evaluation
> ID Tracker URL:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


Congratulations to all who worked on this one.

Gorry, could you work with the authors to respond to the comments that you
received during IESG evaluation?

Spencer

--001a11c23d8a85088f050d41ec93
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Gorry,<div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Thu, Jan 22, 2015 at 12:16 PM, IETF Secretariat <span dir=3D"l=
tr">&lt;<a href=3D"mailto:ietf-secretariat-reply@ietf.org" target=3D"_blank=
">ietf-secretariat-reply@ietf.org</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">IESG state changed to Approved-announcement to be sent::Revi=
sed I-D Needed from IESG Evaluation<br>
ID Tracker URL: <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-tsvwg=
-sctp-dtls-encaps/" target=3D"_blank">http://datatracker.ietf.org/doc/draft=
-ietf-tsvwg-sctp-dtls-encaps/</a></blockquote><div><br></div><div>Congratul=
ations to all who worked on this one.</div><div><br></div><div>Gorry, could=
 you work with the authors to respond to the comments that you received dur=
ing IESG evaluation?</div><div><br></div><div>Spencer=C2=A0</div></div></di=
v></div>

--001a11c23d8a85088f050d41ec93--


From nobody Thu Jan 22 10:52:25 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC2C1B29B3 for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 10:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 YY_MlsFCLNFR; Thu, 22 Jan 2015 10:52:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7121AD49D; Thu, 22 Jan 2015 10:52:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150122185221.27564.7850.idtracker@ietfa.amsl.com>
Date: Thu, 22 Jan 2015 10:52:21 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/-qsT0GWK0NHUg2QGKGuW2OP-uEE>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-06.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 18:52:22 -0000

IESG state changed to IESG Evaluation from Waiting for Writeup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Thu Jan 22 10:52:53 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDAE71B29C3; Thu, 22 Jan 2015 10:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 3HVb5gNYTVbA; Thu, 22 Jan 2015 10:52:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D86861AD49D; Thu, 22 Jan 2015 10:52:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, iesg-secretary@ietf.org,  iesg@ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150122185242.28991.39079.idtracker@ietfa.amsl.com>
Date: Thu, 22 Jan 2015 10:52:42 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/5T_wnmO712z5TyY3Dww_C-iiVCc>
Subject: [tsvwg] Telechat update notice: <draft-ietf-tsvwg-sctp-prpolicies-06.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 18:52:47 -0000

Placed on agenda for telechat - 2015-01-22
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Thu Jan 22 10:55:00 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B481B29B6; Thu, 22 Jan 2015 10:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 B0LYx65bCnY9; Thu, 22 Jan 2015 10:54:54 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3521B29B3; Thu, 22 Jan 2015 10:54:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, iesg-secretary@ietf.org,  iesg@ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150122185454.26288.36209.idtracker@ietfa.amsl.com>
Date: Thu, 22 Jan 2015 10:54:54 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/MFyyiHZajrob4c8NqzuR2ik9VW0>
Subject: [tsvwg] Telechat update notice: <draft-ietf-tsvwg-sctp-prpolicies-06.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 18:54:55 -0000

Telechat date has been changed to 2015-02-05 from 2015-01-22
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Thu Jan 22 12:02:18 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B101A6FBB for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 12:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 kqDMQryehHd3 for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 12:02:08 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E5A01A6F34 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 12:02:08 -0800 (PST)
Received: from [192.168.1.200] (p508F118A.dip0.t-ipconnect.de [80.143.17.138]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 3726A1C0E985B; Thu, 22 Jan 2015 21:02:05 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CAKKJt-e-+HvmRYyyA5+=NNv1DV8Ek8o=LVmV1SH42jYQJh2QTA@mail.gmail.com>
Date: Thu, 22 Jan 2015 21:02:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B5866A0-683B-4AA5-A48C-FC449BCDEEDC@fh-muenster.de>
References: <20150122181627.5439.5283.idtracker@ietfa.amsl.com> <CAKKJt-e-+HvmRYyyA5+=NNv1DV8Ek8o=LVmV1SH42jYQJh2QTA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/4McBQEmLLkUQ1Ey-6YKjN8aT2tM>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
Subject: Re: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-08.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 20:02:13 -0000

On 22 Jan 2015, at 19:34, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> Hi, Gorry,
>=20
> On Thu, Jan 22, 2015 at 12:16 PM, IETF Secretariat =
<ietf-secretariat-reply@ietf.org> wrote:
> IESG state changed to Approved-announcement to be sent::Revised I-D =
Needed from IESG Evaluation
> ID Tracker URL: =
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
>=20
> Congratulations to all who worked on this one.
>=20
> Gorry, could you work with the authors to respond to the comments that =
you received during IESG evaluation?
I'll go through them tomorrow.

Best regards
Michael
>=20
> Spencer=20


From nobody Thu Jan 22 12:04:04 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1319D1A8546 for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 12:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 WRUKObTJsCXo for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 12:03:59 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D409A1A6F34 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 12:03:58 -0800 (PST)
Received: from [192.168.1.200] (p508F118A.dip0.t-ipconnect.de [80.143.17.138]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 2CAAD1C0E985B; Thu, 22 Jan 2015 21:03:57 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <CAO249ycaf8Q-AyTcp4cx3xhocyNzPEZzVO148XQfBJwhiKjWSw@mail.gmail.com>
Date: Thu, 22 Jan 2015 21:03:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E49B9AC9-90F8-4158-9DFE-99B2ECCC1140@lurchi.franken.de>
References: <5FFBC79D-AE0A-4B44-B11F-7A2D6EA00347@cisco.com> <372D50B7-4AF4-41EC-A6E8-97E00C4F5FE8@lurchi.franken.de> <CAO249ycaf8Q-AyTcp4cx3xhocyNzPEZzVO148XQfBJwhiKjWSw@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/aTPmh8_iIYoMCmqCQ_KDBnviD3M>
Cc: tsvwg <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [tsvwg] sanity checking DTLS ICMP errors
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 20:04:01 -0000

> On 22 Jan 2015, at 09:34, Yoshifumi Nishida <nishida@sfc.wide.ad.jp> =
wrote:
>=20
>=20
> On Mon, Jan 19, 2015 at 2:36 PM, Michael Tuexen =
<Michael.Tuexen@lurchi.franken.de> wrote:
> > On 19 Jan 2015, at 20:43, =F0=9F=94=93Dan Wing <dwing@cisco.com> =
wrote:
> >
> > To reduce the attack surface, TCP implementations have been =
validating ICMP error messages to be in-window (RFC5927).
> >
> > On a thread over on RTCWEB with Michael T=C3=BCxen, it seems =
DTLS-encrypted packets might benefit from a similar validation.
> Just to add some information:
> Dan was asking why we couldn't just process incoming ICMP packets =
indicating that a packet
> sent was too big by SCTP when running over DTLS. My point was that we =
can't the validation
> of the verification tag as we do normally for SCTP. That is why we use =
PMTUD as described
> in RFC4821 for
> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-08
>=20
> Sorry if I miss something..=20
> I'm just curious after reading the following texts.
>=20
>  Incoming ICMP or ICMPv6 messages can't be processed by the SCTP
>    layer, since there is no way to identify the corresponding
>    association.=20
>=20
>=20
> If the socket used for UDP encap is connected and if only one SCTP =
association over DTLS is mapped to the socket, is it still impossible =
for SCTP layer to know if it receives ICMP errors? =20
Please note that the ICMP processing of SCTP requires to check the =
verification tag. Since we use DTLS, this
is not present in cleartext in the ICMP message (if it is present at =
all).

Best regards
Michael
>=20
> Thanks,
> --
> Yoshi=20


From nobody Thu Jan 22 16:05:11 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C5D21A8A79 for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 16:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 xTQXWvf7Bjpd; Thu, 22 Jan 2015 16:05:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 393811A8A45; Thu, 22 Jan 2015 16:05:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150123000507.32531.91405.idtracker@ietfa.amsl.com>
Date: Thu, 22 Jan 2015 16:05:07 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/oe-yKl74Ubk2beaM6HAdpkGtb0U>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-06.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 00:05:08 -0000

IANA review state changed to IANA OK - No Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Thu Jan 22 23:40:22 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE7571A036F for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 23:40:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.215
X-Spam-Level: **
X-Spam-Status: No, score=2.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 2bseqHm3NmLz for <tsvwg@ietfa.amsl.com>; Thu, 22 Jan 2015 23:40:15 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AE0F1A01F4 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 23:40:15 -0800 (PST)
Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 0BD1C2781F2 for <tsvwg@ietf.org>; Fri, 23 Jan 2015 16:40:13 +0900 (JST)
Received: by mail-we0-f169.google.com with SMTP id u56so6014512wes.0 for <tsvwg@ietf.org>; Thu, 22 Jan 2015 23:40:10 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.93.5 with SMTP id cq5mr4642010wjb.84.1421998810777; Thu, 22 Jan 2015 23:40:10 -0800 (PST)
Received: by 10.194.187.48 with HTTP; Thu, 22 Jan 2015 23:40:10 -0800 (PST)
In-Reply-To: <E49B9AC9-90F8-4158-9DFE-99B2ECCC1140@lurchi.franken.de>
References: <5FFBC79D-AE0A-4B44-B11F-7A2D6EA00347@cisco.com> <372D50B7-4AF4-41EC-A6E8-97E00C4F5FE8@lurchi.franken.de> <CAO249ycaf8Q-AyTcp4cx3xhocyNzPEZzVO148XQfBJwhiKjWSw@mail.gmail.com> <E49B9AC9-90F8-4158-9DFE-99B2ECCC1140@lurchi.franken.de>
Date: Thu, 22 Jan 2015 23:40:10 -0800
Message-ID: <CAO249ye9mQtLLuFJzvBOuzXxehKVmRB6C4enPVPT33TjRT_zDw@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: multipart/alternative; boundary=047d7bb04da6fcd289050d4ce5be
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/Tjqw7mvdDhhGW86n3X4MKrtKal0>
Cc: tsvwg <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [tsvwg] sanity checking DTLS ICMP errors
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 07:40:18 -0000

--047d7bb04da6fcd289050d4ce5be
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Michael,

On Thu, Jan 22, 2015 at 12:03 PM, Michael Tuexen <
Michael.Tuexen@lurchi.franken.de> wrote:

>
> > On 22 Jan 2015, at 09:34, Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
> wrote:
> >
> >
> > On Mon, Jan 19, 2015 at 2:36 PM, Michael Tuexen <
> Michael.Tuexen@lurchi.franken.de> wrote:
> > > On 19 Jan 2015, at 20:43, =F0=9F=94=93Dan Wing <dwing@cisco.com> wrot=
e:
> > >
> > > To reduce the attack surface, TCP implementations have been validatin=
g
> ICMP error messages to be in-window (RFC5927).
> > >
> > > On a thread over on RTCWEB with Michael T=C3=BCxen, it seems DTLS-enc=
rypted
> packets might benefit from a similar validation.
> > Just to add some information:
> > Dan was asking why we couldn't just process incoming ICMP packets
> indicating that a packet
> > sent was too big by SCTP when running over DTLS. My point was that we
> can't the validation
> > of the verification tag as we do normally for SCTP. That is why we use
> PMTUD as described
> > in RFC4821 for
> > http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-08
> >
> > Sorry if I miss something..
> > I'm just curious after reading the following texts.
> >
> >  Incoming ICMP or ICMPv6 messages can't be processed by the SCTP
> >    layer, since there is no way to identify the corresponding
> >    association.
> >
> >
> > If the socket used for UDP encap is connected and if only one SCTP
> association over DTLS is mapped to the socket, is it still impossible for
> SCTP layer to know if it receives ICMP errors?
> Please note that the ICMP processing of SCTP requires to check the
> verification tag. Since we use DTLS, this
> is not present in cleartext in the ICMP message (if it is present at all)=
.
>

What I meant was that an SCTP association might be able to know if it
receives ICMP errors, even though it cannot examine it.
I just felt that the texts "there is no way to identify the corresponding
association" might be a bit ambiguous expression. Sorry for picking up a
minor point.

Thanks,
--
Yoshi

--047d7bb04da6fcd289050d4ce5be
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Michael,<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Jan 22, 2015 at 12:03 PM, Michael Tuexen <span dir=
=3D"ltr">&lt;<a href=3D"mailto:Michael.Tuexen@lurchi.franken.de" target=3D"=
_blank">Michael.Tuexen@lurchi.franken.de</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div><div><br>
&gt; On 22 Jan 2015, at 09:34, Yoshifumi Nishida &lt;<a href=3D"mailto:nish=
ida@sfc.wide.ad.jp" target=3D"_blank">nishida@sfc.wide.ad.jp</a>&gt; wrote:=
<br>
&gt;<br>
&gt;<br>
&gt; On Mon, Jan 19, 2015 at 2:36 PM, Michael Tuexen &lt;<a href=3D"mailto:=
Michael.Tuexen@lurchi.franken.de" target=3D"_blank">Michael.Tuexen@lurchi.f=
ranken.de</a>&gt; wrote:<br>
&gt; &gt; On 19 Jan 2015, at 20:43, =F0=9F=94=93Dan Wing &lt;<a href=3D"mai=
lto:dwing@cisco.com" target=3D"_blank">dwing@cisco.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; To reduce the attack surface, TCP implementations have been valid=
ating ICMP error messages to be in-window (RFC5927).<br>
&gt; &gt;<br>
&gt; &gt; On a thread over on RTCWEB with Michael T=C3=BCxen, it seems DTLS=
-encrypted packets might benefit from a similar validation.<br>
&gt; Just to add some information:<br>
&gt; Dan was asking why we couldn&#39;t just process incoming ICMP packets =
indicating that a packet<br>
&gt; sent was too big by SCTP when running over DTLS. My point was that we =
can&#39;t the validation<br>
&gt; of the verification tag as we do normally for SCTP. That is why we use=
 PMTUD as described<br>
&gt; in RFC4821 for<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encap=
s-08" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dt=
ls-encaps-08</a><br>
&gt;<br>
&gt; Sorry if I miss something..<br>
&gt; I&#39;m just curious after reading the following texts.<br>
&gt;<br>
&gt;=C2=A0 Incoming ICMP or ICMPv6 messages can&#39;t be processed by the S=
CTP<br>
&gt;=C2=A0 =C2=A0 layer, since there is no way to identify the correspondin=
g<br>
&gt;=C2=A0 =C2=A0 association.<br>
&gt;<br>
&gt;<br>
&gt; If the socket used for UDP encap is connected and if only one SCTP ass=
ociation over DTLS is mapped to the socket, is it still impossible for SCTP=
 layer to know if it receives ICMP errors?<br>
</div></div>Please note that the ICMP processing of SCTP requires to check =
the verification tag. Since we use DTLS, this<br>
is not present in cleartext in the ICMP message (if it is present at all).<=
br></blockquote><div><br></div><div>What I meant was that an SCTP associati=
on might be able to know if it receives ICMP errors, even though it cannot =
examine it.=C2=A0</div><div>I just felt that the texts &quot;there is no wa=
y to identify the corresponding association&quot; might be a bit ambiguous =
expression. Sorry for picking up a minor point.</div><div><br></div><div>Th=
anks,</div><div>--</div><div>Yoshi</div></div></div></div>

--047d7bb04da6fcd289050d4ce5be--


From nobody Fri Jan 23 10:33:59 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7AE61ACDB1 for <tsvwg@ietfa.amsl.com>; Fri, 23 Jan 2015 10:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.031
X-Spam-Level: 
X-Spam-Status: No, score=0.031 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 QsMlp5wTPu_d for <tsvwg@ietfa.amsl.com>; Fri, 23 Jan 2015 10:33:38 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 104251ACDBD for <tsvwg@ietf.org>; Fri, 23 Jan 2015 10:33:34 -0800 (PST)
Received: from [192.168.1.200] (p508F3076.dip0.t-ipconnect.de [80.143.48.118]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 6A3F91C104DD5; Fri, 23 Jan 2015 19:33:16 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <CAO249ye9mQtLLuFJzvBOuzXxehKVmRB6C4enPVPT33TjRT_zDw@mail.gmail.com>
Date: Fri, 23 Jan 2015 15:41:21 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E293F8C1-0F4B-47B5-8FD4-EDAFE050B8A8@lurchi.franken.de>
References: <5FFBC79D-AE0A-4B44-B11F-7A2D6EA00347@cisco.com> <372D50B7-4AF4-41EC-A6E8-97E00C4F5FE8@lurchi.franken.de> <CAO249ycaf8Q-AyTcp4cx3xhocyNzPEZzVO148XQfBJwhiKjWSw@mail.gmail.com> <E49B9AC9-90F8-4158-9DFE-99B2ECCC1140@lurchi.franken.de> <CAO249ye9mQtLLuFJzvBOuzXxehKVmRB6C4enPVPT33TjRT_zDw@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/SuV_YkWYH7aDvKCt1v7TT1NB_s8>
Cc: tsvwg <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [tsvwg] sanity checking DTLS ICMP errors
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 18:33:40 -0000

> On 23 Jan 2015, at 08:40, Yoshifumi Nishida <nishida@sfc.wide.ad.jp> =
wrote:
>=20
> Hi Michael,
>=20
> On Thu, Jan 22, 2015 at 12:03 PM, Michael Tuexen =
<Michael.Tuexen@lurchi.franken.de> wrote:
>=20
>> On 22 Jan 2015, at 09:34, Yoshifumi Nishida <nishida@sfc.wide.ad.jp> =
wrote:
>>=20
>>=20
>> On Mon, Jan 19, 2015 at 2:36 PM, Michael Tuexen =
<Michael.Tuexen@lurchi.franken.de> wrote:
>>> On 19 Jan 2015, at 20:43, =F0=9F=94=93Dan Wing <dwing@cisco.com> =
wrote:
>>>=20
>>> To reduce the attack surface, TCP implementations have been =
validating ICMP error messages to be in-window (RFC5927).
>>>=20
>>> On a thread over on RTCWEB with Michael T=C3=BCxen, it seems =
DTLS-encrypted packets might benefit from a similar validation.
>> Just to add some information:
>> Dan was asking why we couldn't just process incoming ICMP packets =
indicating that a packet
>> sent was too big by SCTP when running over DTLS. My point was that we =
can't the validation
>> of the verification tag as we do normally for SCTP. That is why we =
use PMTUD as described
>> in RFC4821 for
>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-08
>>=20
>> Sorry if I miss something..
>> I'm just curious after reading the following texts.
>>=20
>> Incoming ICMP or ICMPv6 messages can't be processed by the SCTP
>>   layer, since there is no way to identify the corresponding
>>   association.
>>=20
>>=20
>> If the socket used for UDP encap is connected and if only one SCTP =
association over DTLS is mapped to the socket, is it still impossible =
for SCTP layer to know if it receives ICMP errors?
> Please note that the ICMP processing of SCTP requires to check the =
verification tag. Since we use DTLS, this
> is not present in cleartext in the ICMP message (if it is present at =
all).
>=20
> What I meant was that an SCTP association might be able to know if it =
receives ICMP errors, even though it cannot examine it.=20
> I just felt that the texts "there is no way to identify the =
corresponding association" might be a bit ambiguous expression. Sorry =
for picking up a minor point.
Well, if you can't. You could only apply the handling to all =
associations running over the the DTLS connection
and bypass the verification tag checking. So you can't figure out which =
association triggered the sending
of the ICMP packet, since the reflected packet is the DTLS cipher text.

Best regards
Michael
>=20
> Thanks,
> --
> Yoshi


From nobody Fri Jan 23 11:51:14 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 197F81A000C; Fri, 23 Jan 2015 11:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 5I2318obOO0H; Fri, 23 Jan 2015 11:50:46 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F55F1A017C; Fri, 23 Jan 2015 11:50:44 -0800 (PST)
Received: from [192.168.1.200] (p508F3076.dip0.t-ipconnect.de [80.143.48.118]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 16B6C1C104DFA; Fri, 23 Jan 2015 20:50:26 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <20150119222638.5078.45177.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jan 2015 20:50:00 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <96363547-D993-41A8-A131-D78250510AD1@fh-muenster.de>
References: <20150119222638.5078.45177.idtracker@ietfa.amsl.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/4EkUp7t9dG40z9JsnegWECnwvDQ>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg-chairs@tools.ietf.org, The IESG <iesg@ietf.org>, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Barry Leiba's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 19:50:48 -0000

On 19 Jan 2015, at 23:26, Barry Leiba <barryleiba@computer.org> wrote:
> 
> Barry Leiba has entered the following ballot position for
> draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
Hi Barry,

thank you very much for your review. Please see my comments in-line.

Best regards
Michael
> I agree that Stephen's DISCUSS needs to be sorted out.
That has been done.
> 
> I've a couple of minor comments on a paragraph in Section 1:
> 
>   This encapsulation of SCTP over DTLS over or UDP or ICE/UDP (see
>   [RFC5245]) can provide a NAT traversal solution together with
>   confidentiality, source authentication, and integrity protected
>   transfers.
> 
> Is there a protocol missing before the first "or", or does the first "or"
> need to be deleted (the latter, I think)?
It needs to be deleted.
> 
> The phrase "together with" implies that something else is needed (as in
> "X, together with Y, provides Z").  Does the sentence mean to say that
> <this encapsulation> can provide [a NAT traversal solution that includes
> confidentiality, source authentication, and integrity-protected
> transfers]?  Or does it mean to say that <this encapsulation> can provide
> a NAT traversal solution, as well as confidentiality, source
> authentication, and integrity-protected transfers]?  I think it's one of
> those.
What about:

<t>This encapsulation of SCTP over DTLS over UDP or ICE/UDP
(see <xref target='RFC5245'/>) can provide a NAT traversal
solution in addition to confidentiality, source authentication, and
integrity protected transfers.</t>
> 
> 
> 


From nobody Fri Jan 23 11:57:11 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 072641A017C; Fri, 23 Jan 2015 11:56:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 o9o8Bk0cLG1W; Fri, 23 Jan 2015 11:56:49 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 934FA1A017A; Fri, 23 Jan 2015 11:56:49 -0800 (PST)
Received: from [192.168.1.200] (p508F3076.dip0.t-ipconnect.de [80.143.48.118]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 8998A1C10461D; Fri, 23 Jan 2015 20:56:32 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362E97F4@MX104CL02.corp.emc.com>
Date: Fri, 23 Jan 2015 20:56:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <836DF41F-E152-4C9A-A52D-26BA14FD1DE7@fh-muenster.de>
References: <20150120213405.4542.64355.idtracker@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362E97F4@MX104CL02.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/E5X8Ux29j-EqRkectL1G7JzGpuk>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, Benoit Claise <bclaise@cisco.com>
Subject: Re: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 19:56:51 -0000

> On 20 Jan 2015, at 22:47, Black, David <david.black@emc.com> wrote:
>=20
> Benoit,
>=20
>> The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
>>   support the most recently published version of DTLS, which is DTLS
>>   1.2 [RFC6347] as of December 2014.
>>=20
>> December 2014 is wrong.
>=20
> Nitpick department ;-) - as of Dec 2014, DTLS 1.2 [RFC6347] is the =
most
> recently published (as an RFC) version of DTLS, even though that RFC =
was
> published in Jan 2012, so the quoted text is actually correct ;-).
>=20
> Nonetheless, here's a clearer suggestion:
>=20
> OLD
>     support the most recently published version of DTLS, which is DTLS
>     1.2 [RFC6347] as of December 2014.
> NEW
>     support the most recently published version of DTLS, which was =
DTLS
>     1.2 [RFC6347] when this RFC was published (XXXXXXXXX 2015).
>=20
>     RFC Editor: please fill in publication month of this RFC and =
ensure
>     that correctness of the above statement is checked during AUTH48.
> END
What about:

NEW
    support the most recently published version of DTLS, which was DTLS
    1.2 [RFC6347] when this RFC was published.
END

This provides the same information and is simpler. OK?

Best regards
Michael
>=20
> Thanks,
> --David
>=20
>=20
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Benoit =
Claise
>> Sent: Tuesday, January 20, 2015 4:34 PM
>> To: The IESG
>> Cc: gorry@erg.abdn.ac.uk; tsvwg-chairs@tools.ietf.org; =
tsvwg@ietf.org; draft-
>> ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
>> Subject: [tsvwg] Benoit Claise's No Objection on =
draft-ietf-tsvwg-sctp-dtls-
>> encaps-08: (with COMMENT)
>>=20
>> Benoit Claise has entered the following ballot position for
>> draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut =
this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to =
http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
>>   support the most recently published version of DTLS, which is DTLS
>>   1.2 [RFC6347] as of December 2014.
>>=20
>> December 2014 is wrong.
>>=20
>=20


From nobody Fri Jan 23 12:16:22 2015
Return-Path: <barryleiba@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB101A1A04; Fri, 23 Jan 2015 12:16:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, 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 Qc2oztk6Nk9a; Fri, 23 Jan 2015 12:16:01 -0800 (PST)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (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 389221A0263; Fri, 23 Jan 2015 12:16:01 -0800 (PST)
Received: by mail-lb0-f173.google.com with SMTP id p9so4625769lbv.4; Fri, 23 Jan 2015 12:15:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UdZPgIh2Dp9fPq3VqgFYECuhxMuRkzHMdsD6R0pCAfU=; b=CmJxga+9GkPV3kKV8kHiy/2rBS2i2XXAiwlnjhDEuHjZIeA5tshCy03i38ZPEZz3Mn 4LP4cm1/Sj6TapVJEfiX2+Df2+g0vA/1W0gtiedsyf1KMFCdUgiX45qHM0U/3HgdzCEL 1EqxUJBRSLXMMBQzj9biY53SSdn9dqftCS93M+Xt3ImOq+q8S6GpkPJ1JrmyViGQCMCM Jc09d7dawTbxdZ7GPdF82E0xUrWKLVLrLkPjpZsyqMuJi9orzbfppvqjY0XX7kKsThwp JJg5tnIpIeLxpKPIYsr7McwLrUPTKVtTXGf/4duz8AbJdYPspz39WK/jHk3UH1LZpy9g KVvw==
MIME-Version: 1.0
X-Received: by 10.152.44.193 with SMTP id g1mr9169124lam.15.1422044159699; Fri, 23 Jan 2015 12:15:59 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.168 with HTTP; Fri, 23 Jan 2015 12:15:59 -0800 (PST)
In-Reply-To: <96363547-D993-41A8-A131-D78250510AD1@fh-muenster.de>
References: <20150119222638.5078.45177.idtracker@ietfa.amsl.com> <96363547-D993-41A8-A131-D78250510AD1@fh-muenster.de>
Date: Fri, 23 Jan 2015 15:15:59 -0500
X-Google-Sender-Auth: upVH1xJsG9TxoA19LJJPjUCN_xs
Message-ID: <CALaySJLOmAodZzXHgMaUKsLs2KRu4V7zBf4R9GaMBwnbOv1p-w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/c4zzM3jAiM9l09mjOSa5EuWsrnM>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg chair <tsvwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Barry Leiba's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 20:16:02 -0000

Hi, Michael.  Thanks for the response.

>>   This encapsulation of SCTP over DTLS over or UDP or ICE/UDP (see
>>   [RFC5245]) can provide a NAT traversal solution together with
>>   confidentiality, source authentication, and integrity protected
>>   transfers.
...
>> The phrase "together with" implies that something else is needed (as in
>> "X, together with Y, provides Z").  Does the sentence mean to say that
>> <this encapsulation> can provide [a NAT traversal solution that includes
>> confidentiality, source authentication, and integrity-protected
>> transfers]?  Or does it mean to say that <this encapsulation> can provide
>> a NAT traversal solution, as well as confidentiality, source
>> authentication, and integrity-protected transfers]?  I think it's one of
>> those.
>
> What about:
>
> <t>This encapsulation of SCTP over DTLS over UDP or ICE/UDP
> (see <xref target='RFC5245'/>) can provide a NAT traversal
> solution in addition to confidentiality, source authentication, and
> integrity protected transfers.</t>

Yep, that looks fine.  Thanks.

Barry


From nobody Fri Jan 23 14:10:01 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FFA91AC3C6; Fri, 23 Jan 2015 14:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Qy48G4VNbBaK; Fri, 23 Jan 2015 14:09:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B74E61AC3CA; Fri, 23 Jan 2015 14:09:11 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150123220911.26781.11988.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jan 2015 14:09:11 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/OuqIjqn9MhXDBlvP5plftmwf8AY>
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 22:09:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : Recommendations for Transport Port Number Uses
        Author          : Joe Touch
	Filename        : draft-ietf-tsvwg-port-use-07.txt
	Pages           : 22
	Date            : 2015-01-23

Abstract:
   This document provides recommendations to application and service
   designers on how to use the transport protocol port number space. It
   complements (but does not update) RFC6335, which focuses on IANA
   process.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-port-use-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-07


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 Fri Jan 23 14:11:25 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1246E1A884D; Fri, 23 Jan 2015 14:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 0HGDeTWA0VWm; Fri, 23 Jan 2015 14:11:09 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A14B1AC3C7; Fri, 23 Jan 2015 14:09:59 -0800 (PST)
Received: from [192.168.1.200] (p508F3076.dip0.t-ipconnect.de [80.143.48.118]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id BE6B21C0B4606; Fri, 23 Jan 2015 23:09:41 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <20150119224118.1160.58499.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jan 2015 23:09:14 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D113DD81-923D-4E02-B051-8EE0571AB335@fh-muenster.de>
References: <20150119224118.1160.58499.idtracker@ietfa.amsl.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/UJCKiamD4AANt-EOW-8zuXkX-ZQ>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg-chairs@tools.ietf.org, The IESG <iesg@ietf.org>, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Stephen Farrell's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 22:11:11 -0000

> On 19 Jan 2015, at 23:41, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
>=20
> Stephen Farrell has entered the following ballot position for
> draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
Hi Stephen,

thank you very much for your review. Please see my comments in-line.

Best regards
Michael
>=20
> - I had a discuss on DTLS1.0 as the MTI. I'm told that=20
> was decided by the WG last Nov in consultation with=20
> WebRTC and TLS WG chairs, so while I'd prefer to
> see DTLS1.2 as the MTI, I've cleared the DISCUSS.
OK.
>=20
> - Figure 1: Couldn't ICE/UDP be somewhat confusing for
> someone unaware that ICE is more of an algorithm than a
> wire protocol? Might be nice to clarify that here in
> the intro. (If you want to be nice, if you don't that's
> ok too and can be the right decision.)
We are actually using text very similar to the text in
https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-13

Using ICE might not change the packet format on the wire,
just some TURN messages are multiplexed. However, if a
TURN server is involved, the wire format changes. However,
all that is described in RFC 5245.

However, what about adding to

   This encapsulation of SCTP over DTLS over UDP or ICE/UDP (see
   [RFC5245]) can provide a NAT traversal solution in addition to
   confidentiality, source authentication, and integrity protected
   transfers.

the following sentence:
   Please note that using ICE does not necessarily imply
   that a different packet format is used on the wire.

Would that address your comment?
>=20
> - section 3: Isn't "complete SCTP packet" a teeny bit
> ambiguous? It could mean including the IP and other
> lower headers but I guess you do not. But that's a nit
> since it's probably clear enough that you don't put an
> IP or layer 2 header into the DTLS payload:-)
I agree that "complete SCTP packet" might not be as clear as possible.
That is the reason why the text reads:
the complete SCTP packet, consisting of the SCTP common header and
a number of SCTP chunks,
Doesn't that make it clear?
>=20
> - Given heartbleed, and the use here of RFC6520 I think
> some note of that famous implementation bug would be
> wise. Just to a pointer to how to not have that
> problem. But it's not a protocol bug so I'm not trying
> to insist, i.e. no need for us to argue the toss on
> this:-)
I'm not sure if this document is the right place to discuss this.
I completely agree that heartbleed is an implementation bug.
There is already explicit text in
https://tools.ietf.org/html/rfc6520#section-4
which tells an implementer how to avoid it:

   If the payload_length of a received HeartbeatMessage is too large,
   the received HeartbeatMessage MUST be discarded silently.

I can add text stressing this again, but I'm not sure if it helps, since
an implementer should read RFC 6520 and implement the appropriate
input validation as written in the RFC using normative language.
>=20
> - I'm also wondering if the text here on 6520 is
> sufficiently clear given this week's discussion of that
> on the rtcweb list. (I'm not on tsvwg@ so would
> appreciate an update on how the thread [1] pans out on
> the tsvwg list before we approve this.)
I think it is clear how to implement PMTUD according to
RFC4821 and using RFC6520 for probe packets.=20
The question in the thread was about which of the two
option allowed by this document is used in the RTCWeb
context:
1. DTLS does the PMTUD
2. SCTP does the PMTUD
It was concluded in that discussion that it is clear
in the WebRTC document that option 2 is used.
The other question was why ICMP can't be processed by SCTP.

So I can add some explanation to Section 6.1:

OLD:
   o  The implementation MUST NOT rely on processing ICMP or ICMPv6
      packets.  This applies in particular to path MTU discovery when
      performed by SCTP.

NEW:
   o  The implementation MUST NOT rely on processing ICMP or ICMPv6
      packets, since the SCTP layer most likely can't access the
      SCTP common header in plain text of the packet, which triggered
      the sending of the ICMP or ICMPv6 packet. This applies in
      particular to path MTU discovery when performed by SCTP.

Does that address the issue?
>=20
>  [1] =
https://www.ietf.org/mail-archive/web/rtcweb/current/msg14069.html
>=20
>=20
>=20


From nobody Fri Jan 23 14:29:30 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C798C1AD05E; Fri, 23 Jan 2015 14:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 cUsWT6AKT4DU; Fri, 23 Jan 2015 14:29:19 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C1E21A874F; Fri, 23 Jan 2015 14:29:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 613F0BEB6; Fri, 23 Jan 2015 22:29:17 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71dv0NibO0Dj; Fri, 23 Jan 2015 22:29:15 +0000 (GMT)
Received: from [127.0.0.1] (unknown [86.42.29.136]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 75DC6BEB3; Fri, 23 Jan 2015 22:29:15 +0000 (GMT)
X-Priority: 3
To: tuexen@fh-muenster.de
From: stephen.farrell@cs.tcd.ie
In-Reply-To: <D113DD81-923D-4E02-B051-8EE0571AB335@fh-muenster.de>
References: <20150119224118.1160.58499.idtracker@ietfa.amsl.com> <D113DD81-923D-4E02-B051-8EE0571AB335@fh-muenster.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Date: Fri, 23 Jan 2015 22:29:13 +0000
Message-ID: <eb4tji.ninigr.2vaesf-qmf@mercury.scss.tcd.ie>
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/TmYBAzAUmQmxbfxZK-dD9PNnNeU>
Cc: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [tsvwg] Stephen Farrell's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 22:29:25 -0000

SGkgTWljaGFlbCwNCg0KVGhhbmtzIHRob3NlIGFsbCBsb29rIGdvb2QgDQoNClMNCg0KDQpPbiBG
cmkgSmFuIDIzIDIyOjA5OjE0IDIwMTUgR01ULCBNaWNoYWVsIFR1ZXhlbiB3cm90ZToNCj4gPiBP
biAxOSBKYW4gMjAxNSwgYXQgMjM6NDEsIFN0ZXBoZW4gRmFycmVsbCA8c3RlcGhlbi5mYXJyZWxs
QGNzLnRjZC5pZT4gd3JvdGU6DQo+ID4gDQo+ID4gU3RlcGhlbiBGYXJyZWxsIGhhcyBlbnRlcmVk
IHRoZSBmb2xsb3dpbmcgYmFsbG90IHBvc2l0aW9uIGZvcg0KPiA+IGRyYWZ0LWlldGYtdHN2d2ct
c2N0cC1kdGxzLWVuY2Fwcy0wODogTm8gT2JqZWN0aW9uDQo+ID4gDQo+ID4gV2hlbiByZXNwb25k
aW5nLCBwbGVhc2Uga2VlcCB0aGUgc3ViamVjdCBsaW5lIGludGFjdCBhbmQgcmVwbHkgdG8gYWxs
DQo+ID4gZW1haWwgYWRkcmVzc2VzIGluY2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChG
ZWVsIGZyZWUgdG8gY3V0IHRoaXMNCj4gPiBpbnRyb2R1Y3RvcnkgcGFyYWdyYXBoLCBob3dldmVy
LikNCj4gPiANCj4gPiANCj4gPiBQbGVhc2UgcmVmZXIgdG8gaHR0cDovL3d3dy5pZXRmLm9yZy9p
ZXNnL3N0YXRlbWVudC9kaXNjdXNzLWNyaXRlcmlhLmh0bWwNCj4gPiBmb3IgbW9yZSBpbmZvcm1h
dGlvbiBhYm91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRpb25zLg0KPiA+IA0KPiA+
IA0KPiA+IFRoZSBkb2N1bWVudCwgYWxvbmcgd2l0aCBvdGhlciBiYWxsb3QgcG9zaXRpb25zLCBj
YW4gYmUgZm91bmQgaGVyZToNCj4gPiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtdHN2d2ctc2N0cC1kdGxzLWVuY2Fwcy8NCj4gPiANCj4gPiANCj4gPiANCj4gPiAt
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQo+ID4gQ09NTUVOVDoNCj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4gDQo+IEhp
IFN0ZXBoZW4sDQo+IA0KPiB0aGFuayB5b3UgdmVyeSBtdWNoIGZvciB5b3VyIHJldmlldy4gUGxl
YXNlIHNlZSBteSBjb21tZW50cyBpbi1saW5lLg0KPiANCj4gQmVzdCByZWdhcmRzDQo+IE1pY2hh
ZWwNCj4gPiANCj4gPiAtIEkgaGFkIGEgZGlzY3VzcyBvbiBEVExTMS4wIGFzIHRoZSBNVEkuIEkn
bSB0b2xkIHRoYXQgDQo+ID4gd2FzIGRlY2lkZWQgYnkgdGhlIFdHIGxhc3QgTm92IGluIGNvbnN1
bHRhdGlvbiB3aXRoIA0KPiA+IFdlYlJUQyBhbmQgVExTIFdHIGNoYWlycywgc28gd2hpbGUgSSdk
IHByZWZlciB0bw0KPiA+IHNlZSBEVExTMS4yIGFzIHRoZSBNVEksIEkndmUgY2xlYXJlZCB0aGUg
RElTQ1VTUy4NCj4gT0suDQo+ID4gDQo+ID4gLSBGaWd1cmUgMTogQ291bGRuJ3QgSUNFL1VEUCBi
ZSBzb21ld2hhdCBjb25mdXNpbmcgZm9yDQo+ID4gc29tZW9uZSB1bmF3YXJlIHRoYXQgSUNFIGlz
IG1vcmUgb2YgYW4gYWxnb3JpdGhtIHRoYW4gYQ0KPiA+IHdpcmUgcHJvdG9jb2w/IE1pZ2h0IGJl
IG5pY2UgdG8gY2xhcmlmeSB0aGF0IGhlcmUgaW4NCj4gPiB0aGUgaW50cm8uIChJZiB5b3Ugd2Fu
dCB0byBiZSBuaWNlLCBpZiB5b3UgZG9uJ3QgdGhhdCdzDQo+ID4gb2sgdG9vIGFuZCBjYW4gYmUg
dGhlIHJpZ2h0IGRlY2lzaW9uLikNCj4gV2UgYXJlIGFjdHVhbGx5IHVzaW5nIHRleHQgdmVyeSBz
aW1pbGFyIHRvIHRoZSB0ZXh0IGluDQo+IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLXJ0Y3dlYi1kYXRhLWNoYW5uZWwtMTMNCj4gDQo+IFVzaW5nIElDRSBtaWdodCBub3Qg
Y2hhbmdlIHRoZSBwYWNrZXQgZm9ybWF0IG9uIHRoZSB3aXJlLA0KPiBqdXN0IHNvbWUgVFVSTiBt
ZXNzYWdlcyBhcmUgbXVsdGlwbGV4ZWQuIEhvd2V2ZXIsIGlmIGENCj4gVFVSTiBzZXJ2ZXIgaXMg
aW52b2x2ZWQsIHRoZSB3aXJlIGZvcm1hdCBjaGFuZ2VzLiBIb3dldmVyLA0KPiBhbGwgdGhhdCBp
cyBkZXNjcmliZWQgaW4gUkZDIDUyNDUuDQo+IA0KPiBIb3dldmVyLCB3aGF0IGFib3V0IGFkZGlu
ZyB0bw0KPiANCj4gICAgVGhpcyBlbmNhcHN1bGF0aW9uIG9mIFNDVFAgb3ZlciBEVExTIG92ZXIg
VURQIG9yIElDRS9VRFAgKHNlZQ0KPiAgICBbUkZDNTI0NV0pIGNhbiBwcm92aWRlIGEgTkFUIHRy
YXZlcnNhbCBzb2x1dGlvbiBpbiBhZGRpdGlvbiB0bw0KPiAgICBjb25maWRlbnRpYWxpdHksIHNv
dXJjZSBhdXRoZW50aWNhdGlvbiwgYW5kIGludGVncml0eSBwcm90ZWN0ZWQNCj4gICAgdHJhbnNm
ZXJzLg0KPiANCj4gdGhlIGZvbGxvd2luZyBzZW50ZW5jZToNCj4gICAgUGxlYXNlIG5vdGUgdGhh
dCB1c2luZyBJQ0UgZG9lcyBub3QgbmVjZXNzYXJpbHkgaW1wbHkNCj4gICAgdGhhdCBhIGRpZmZl
cmVudCBwYWNrZXQgZm9ybWF0IGlzIHVzZWQgb24gdGhlIHdpcmUuDQo+IA0KPiBXb3VsZCB0aGF0
IGFkZHJlc3MgeW91ciBjb21tZW50Pw0KPiA+IA0KPiA+IC0gc2VjdGlvbiAzOiBJc24ndCAiY29t
cGxldGUgU0NUUCBwYWNrZXQiIGEgdGVlbnkgYml0DQo+ID4gYW1iaWd1b3VzPyBJdCBjb3VsZCBt
ZWFuIGluY2x1ZGluZyB0aGUgSVAgYW5kIG90aGVyDQo+ID4gbG93ZXIgaGVhZGVycyBidXQgSSBn
dWVzcyB5b3UgZG8gbm90LiBCdXQgdGhhdCdzIGEgbml0DQo+ID4gc2luY2UgaXQncyBwcm9iYWJs
eSBjbGVhciBlbm91Z2ggdGhhdCB5b3UgZG9uJ3QgcHV0IGFuDQo+ID4gSVAgb3IgbGF5ZXIgMiBo
ZWFkZXIgaW50byB0aGUgRFRMUyBwYXlsb2FkOi0pDQo+IEkgYWdyZWUgdGhhdCAiY29tcGxldGUg
U0NUUCBwYWNrZXQiIG1pZ2h0IG5vdCBiZSBhcyBjbGVhciBhcyBwb3NzaWJsZS4NCj4gVGhhdCBp
cyB0aGUgcmVhc29uIHdoeSB0aGUgdGV4dCByZWFkczoNCj4gdGhlIGNvbXBsZXRlIFNDVFAgcGFj
a2V0LCBjb25zaXN0aW5nIG9mIHRoZSBTQ1RQIGNvbW1vbiBoZWFkZXIgYW5kDQo+IGEgbnVtYmVy
IG9mIFNDVFAgY2h1bmtzLA0KPiBEb2Vzbid0IHRoYXQgbWFrZSBpdCBjbGVhcj8NCj4gPiANCj4g
PiAtIEdpdmVuIGhlYXJ0YmxlZWQsIGFuZCB0aGUgdXNlIGhlcmUgb2YgUkZDNjUyMCBJIHRoaW5r
DQo+ID4gc29tZSBub3RlIG9mIHRoYXQgZmFtb3VzIGltcGxlbWVudGF0aW9uIGJ1ZyB3b3VsZCBi
ZQ0KPiA+IHdpc2UuIEp1c3QgdG8gYSBwb2ludGVyIHRvIGhvdyB0byBub3QgaGF2ZSB0aGF0DQo+
ID4gcHJvYmxlbS4gQnV0IGl0J3Mgbm90IGEgcHJvdG9jb2wgYnVnIHNvIEknbSBub3QgdHJ5aW5n
DQo+ID4gdG8gaW5zaXN0LCBpLmUuIG5vIG5lZWQgZm9yIHVzIHRvIGFyZ3VlIHRoZSB0b3NzIG9u
DQo+ID4gdGhpczotKQ0KPiBJJ20gbm90IHN1cmUgaWYgdGhpcyBkb2N1bWVudCBpcyB0aGUgcmln
aHQgcGxhY2UgdG8gZGlzY3VzcyB0aGlzLg0KPiBJIGNvbXBsZXRlbHkgYWdyZWUgdGhhdCBoZWFy
dGJsZWVkIGlzIGFuIGltcGxlbWVudGF0aW9uIGJ1Zy4NCj4gVGhlcmUgaXMgYWxyZWFkeSBleHBs
aWNpdCB0ZXh0IGluDQo+IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2NTIwI3NlY3Rp
b24tNA0KPiB3aGljaCB0ZWxscyBhbiBpbXBsZW1lbnRlciBob3cgdG8gYXZvaWQgaXQ6DQo+IA0K
PiAgICBJZiB0aGUgcGF5bG9hZF9sZW5ndGggb2YgYSByZWNlaXZlZCBIZWFydGJlYXRNZXNzYWdl
IGlzIHRvbyBsYXJnZSwNCj4gICAgdGhlIHJlY2VpdmVkIEhlYXJ0YmVhdE1lc3NhZ2UgTVVTVCBi
ZSBkaXNjYXJkZWQgc2lsZW50bHkuDQo+IA0KPiBJIGNhbiBhZGQgdGV4dCBzdHJlc3NpbmcgdGhp
cyBhZ2FpbiwgYnV0IEknbSBub3Qgc3VyZSBpZiBpdCBoZWxwcywgc2luY2UNCj4gYW4gaW1wbGVt
ZW50ZXIgc2hvdWxkIHJlYWQgUkZDIDY1MjAgYW5kIGltcGxlbWVudCB0aGUgYXBwcm9wcmlhdGUN
Cj4gaW5wdXQgdmFsaWRhdGlvbiBhcyB3cml0dGVuIGluIHRoZSBSRkMgdXNpbmcgbm9ybWF0aXZl
IGxhbmd1YWdlLg0KPiA+IA0KPiA+IC0gSSdtIGFsc28gd29uZGVyaW5nIGlmIHRoZSB0ZXh0IGhl
cmUgb24gNjUyMCBpcw0KPiA+IHN1ZmZpY2llbnRseSBjbGVhciBnaXZlbiB0aGlzIHdlZWsncyBk
aXNjdXNzaW9uIG9mIHRoYXQNCj4gPiBvbiB0aGUgcnRjd2ViIGxpc3QuIChJJ20gbm90IG9uIHRz
dndnQCBzbyB3b3VsZA0KPiA+IGFwcHJlY2lhdGUgYW4gdXBkYXRlIG9uIGhvdyB0aGUgdGhyZWFk
IFsxXSBwYW5zIG91dCBvbg0KPiA+IHRoZSB0c3Z3ZyBsaXN0IGJlZm9yZSB3ZSBhcHByb3ZlIHRo
aXMuKQ0KPiBJIHRoaW5rIGl0IGlzIGNsZWFyIGhvdyB0byBpbXBsZW1lbnQgUE1UVUQgYWNjb3Jk
aW5nIHRvDQo+IFJGQzQ4MjEgYW5kIHVzaW5nIFJGQzY1MjAgZm9yIHByb2JlIHBhY2tldHMuIA0K
PiBUaGUgcXVlc3Rpb24gaW4gdGhlIHRocmVhZCB3YXMgYWJvdXQgd2hpY2ggb2YgdGhlIHR3bw0K
PiBvcHRpb24gYWxsb3dlZCBieSB0aGlzIGRvY3VtZW50IGlzIHVzZWQgaW4gdGhlIFJUQ1dlYg0K
PiBjb250ZXh0Og0KPiAxLiBEVExTIGRvZXMgdGhlIFBNVFVEDQo+IDIuIFNDVFAgZG9lcyB0aGUg
UE1UVUQNCj4gSXQgd2FzIGNvbmNsdWRlZCBpbiB0aGF0IGRpc2N1c3Npb24gdGhhdCBpdCBpcyBj
bGVhcg0KPiBpbiB0aGUgV2ViUlRDIGRvY3VtZW50IHRoYXQgb3B0aW9uIDIgaXMgdXNlZC4NCj4g
VGhlIG90aGVyIHF1ZXN0aW9uIHdhcyB3aHkgSUNNUCBjYW4ndCBiZSBwcm9jZXNzZWQgYnkgU0NU
UC4NCj4gDQo+IFNvIEkgY2FuIGFkZCBzb21lIGV4cGxhbmF0aW9uIHRvIFNlY3Rpb24gNi4xOg0K
PiANCj4gT0xEOg0KPiAgICBvICBUaGUgaW1wbGVtZW50YXRpb24gTVVTVCBOT1QgcmVseSBvbiBw
cm9jZXNzaW5nIElDTVAgb3IgSUNNUHY2DQo+ICAgICAgIHBhY2tldHMuICBUaGlzIGFwcGxpZXMg
aW4gcGFydGljdWxhciB0byBwYXRoIE1UVSBkaXNjb3Zlcnkgd2hlbg0KPiAgICAgICBwZXJmb3Jt
ZWQgYnkgU0NUUC4NCj4gDQo+IE5FVzoNCj4gICAgbyAgVGhlIGltcGxlbWVudGF0aW9uIE1VU1Qg
Tk9UIHJlbHkgb24gcHJvY2Vzc2luZyBJQ01QIG9yIElDTVB2Ng0KPiAgICAgICBwYWNrZXRzLCBz
aW5jZSB0aGUgU0NUUCBsYXllciBtb3N0IGxpa2VseSBjYW4ndCBhY2Nlc3MgdGhlDQo+ICAgICAg
IFNDVFAgY29tbW9uIGhlYWRlciBpbiBwbGFpbiB0ZXh0IG9mIHRoZSBwYWNrZXQsIHdoaWNoIHRy
aWdnZXJlZA0KPiAgICAgICB0aGUgc2VuZGluZyBvZiB0aGUgSUNNUCBvciBJQ01QdjYgcGFja2V0
LiBUaGlzIGFwcGxpZXMgaW4NCj4gICAgICAgcGFydGljdWxhciB0byBwYXRoIE1UVSBkaXNjb3Zl
cnkgd2hlbiBwZXJmb3JtZWQgYnkgU0NUUC4NCj4gDQo+IERvZXMgdGhhdCBhZGRyZXNzIHRoZSBp
c3N1ZT8NCj4gPiANCj4gPiAgWzFdIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93
ZWIvcnRjd2ViL2N1cnJlbnQvbXNnMTQwNjkuaHRtbA0KPiA+IA0KPiA+IA0KPiA+IA0KPiANCj4=


From nobody Fri Jan 23 15:24:48 2015
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93F471A1B1C; Fri, 23 Jan 2015 15:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 WryWCLRQdXZh; Fri, 23 Jan 2015 15:24:44 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45ED81A0074; Fri, 23 Jan 2015 15:24:44 -0800 (PST)
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0NNOO7B031409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Jan 2015 18:24:25 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com t0NNOO7B031409
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1422055465; bh=UXIvLCroosGkmH9jMd+88o+JAxg=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=ndTKIe0fHpxncx5Qf5Kqf8T70tBb9dXv3aYITXy8x6og4H12wEHaOXwr+5yNS+40c VRSafX8oPXIViKrOdfRnRMdLJZU7sC9lDfueyCCL9GSA10NlJa3qv5XzwokwSam0yp EQ3odRgCtTsM6Kk2zpx86RtH2UD8atuGQDcAvqAw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com t0NNOO7B031409
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd54.lss.emc.com (RSA Interceptor); Fri, 23 Jan 2015 18:22:21 -0500
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.222.70.134]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0NNO48n014618 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 23 Jan 2015 18:24:05 -0500
Received: from MXHUB105.corp.emc.com (10.253.50.22) by mxhub22.corp.emc.com (128.222.70.134) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 23 Jan 2015 18:24:04 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.208]) by MXHUB105.corp.emc.com ([10.253.50.22]) with mapi id 14.03.0195.001; Fri, 23 Jan 2015 18:24:04 -0500
From: "Black, David" <david.black@emc.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Thread-Topic: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
Thread-Index: AQHQNPjfXezGEief1UKql1cJy8uz1ZzJiMkggATuVYD//+X7oA==
Date: Fri, 23 Jan 2015 23:24:03 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936313B0A@MX104CL02.corp.emc.com>
References: <20150120213405.4542.64355.idtracker@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362E97F4@MX104CL02.corp.emc.com> <836DF41F-E152-4C9A-A52D-26BA14FD1DE7@fh-muenster.de>
In-Reply-To: <836DF41F-E152-4C9A-A52D-26BA14FD1DE7@fh-muenster.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/MSV9NKmGV5sreoqEIgsgKrQe5NE>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, Benoit Claise <bclaise@cisco.com>
Subject: Re: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 23:24:46 -0000

> What about:
>=20
> NEW
>     support the most recently published version of DTLS, which was DTLS
>     1.2 [RFC6347] when this RFC was published.
> END
>=20
> This provides the same information and is simpler. OK?

That's ok, but let's not lose the RFC Editor note, e.g., add:

    RFC Editor: please ensure that the authors double check the above
    statement about DTLS 1.2 during AUTH48 and then remove this note
    before publication.

Thanks,
--David

> -----Original Message-----
> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> Sent: Friday, January 23, 2015 2:56 PM
> To: Black, David
> Cc: Benoit Claise; The IESG; Gorry Fairhurst; tsvwg-chairs@tools.ietf.org=
;
> tsvwg@ietf.org; draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
> Subject: Re: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sct=
p-
> dtls-encaps-08: (with COMMENT)
>=20
>=20
> > On 20 Jan 2015, at 22:47, Black, David <david.black@emc.com> wrote:
> >
> > Benoit,
> >
> >> The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
> >>   support the most recently published version of DTLS, which is DTLS
> >>   1.2 [RFC6347] as of December 2014.
> >>
> >> December 2014 is wrong.
> >
> > Nitpick department ;-) - as of Dec 2014, DTLS 1.2 [RFC6347] is the most
> > recently published (as an RFC) version of DTLS, even though that RFC wa=
s
> > published in Jan 2012, so the quoted text is actually correct ;-).
> >
> > Nonetheless, here's a clearer suggestion:
> >
> > OLD
> >     support the most recently published version of DTLS, which is DTLS
> >     1.2 [RFC6347] as of December 2014.
> > NEW
> >     support the most recently published version of DTLS, which was DTLS
> >     1.2 [RFC6347] when this RFC was published (XXXXXXXXX 2015).
> >
> >     RFC Editor: please fill in publication month of this RFC and ensure
> >     that correctness of the above statement is checked during AUTH48.
> > END
> What about:
>=20
> NEW
>     support the most recently published version of DTLS, which was DTLS
>     1.2 [RFC6347] when this RFC was published.
> END
>=20
> This provides the same information and is simpler. OK?
>=20
> Best regards
> Michael
> >
> > Thanks,
> > --David
> >
> >
> >> -----Original Message-----
> >> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Benoit Claise
> >> Sent: Tuesday, January 20, 2015 4:34 PM
> >> To: The IESG
> >> Cc: gorry@erg.abdn.ac.uk; tsvwg-chairs@tools.ietf.org; tsvwg@ietf.org;
> draft-
> >> ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
> >> Subject: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp=
-
> dtls-
> >> encaps-08: (with COMMENT)
> >>
> >> Benoit Claise has entered the following ballot position for
> >> draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection
> >>
> >> When responding, please keep the subject line intact and reply to all
> >> email addresses included in the To and CC lines. (Feel free to cut thi=
s
> >> introductory paragraph, however.)
> >>
> >>
> >> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.ht=
ml
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> COMMENT:
> >> ----------------------------------------------------------------------
> >>
> >> The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
> >>   support the most recently published version of DTLS, which is DTLS
> >>   1.2 [RFC6347] as of December 2014.
> >>
> >> December 2014 is wrong.
> >>
> >


From nobody Fri Jan 23 15:55:42 2015
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 947CA1AD0D3 for <tsvwg@ietfa.amsl.com>; Fri, 23 Jan 2015 15:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 T7QdVzhYNNB9 for <tsvwg@ietfa.amsl.com>; Fri, 23 Jan 2015 15:55:36 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705C91A88AE for <tsvwg@ietf.org>; Fri, 23 Jan 2015 15:55:36 -0800 (PST)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id t0NNt9W0017535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 23 Jan 2015 15:55:09 -0800 (PST)
Message-ID: <54C2DF5D.8040800@isi.edu>
Date: Fri, 23 Jan 2015 15:55:09 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <20150123220911.26781.11988.idtracker@ietfa.amsl.com>
In-Reply-To: <20150123220911.26781.11988.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/MdIPfFu_JcMuCO5Z-WZUMUtwP9U>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 23:55:38 -0000

Hi, all,

This update includes minor changes to address IETF LC comments.

Joe

On 1/23/2015 2:09 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 Transport Area Working Group Working Group of the IETF.
> 
>         Title           : Recommendations for Transport Port Number Uses
>         Author          : Joe Touch
> 	Filename        : draft-ietf-tsvwg-port-use-07.txt
> 	Pages           : 22
> 	Date            : 2015-01-23
> 
> Abstract:
>    This document provides recommendations to application and service
>    designers on how to use the transport protocol port number space. It
>    complements (but does not update) RFC6335, which focuses on IANA
>    process.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-port-use-07
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-07
> 
> 
> 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 Sat Jan 24 01:10:36 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD1D1A1A3D; Sat, 24 Jan 2015 01:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level: 
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] 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 d64UcDsH_lKF; Sat, 24 Jan 2015 01:10:32 -0800 (PST)
Received: from mailms.fh-muenster.de (mail.fh-muenster.de [212.201.120.190]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F11241A1A3E; Sat, 24 Jan 2015 01:10:30 -0800 (PST)
Received: from [192.168.1.200] (p508F28BF.dip0.t-ipconnect.de [80.143.40.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: tuexen) by mailms.fh-muenster.de (Postfix) with ESMTPSA id A790D280CF8; Sat, 24 Jan 2015 10:10:27 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936313B0A@MX104CL02.corp.emc.com>
Date: Sat, 24 Jan 2015 10:10:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7855283-B8E8-4E30-BB76-F99051F4887C@fh-muenster.de>
References: <20150120213405.4542.64355.idtracker@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362E97F4@MX104CL02.corp.emc.com> <836DF41F-E152-4C9A-A52D-26BA14FD1DE7@fh-muenster.de> <CE03DB3D7B45C245BCA0D24327794936313B0A@MX104CL02.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/MAqjR9GzGOVLk7eGVSwK9cm10Mg>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, Benoit Claise <bclaise@cisco.com>
Subject: Re: [tsvwg] Benoit Claise's No Objection on draft-ietf-tsvwg-sctp-dtls-encaps-08: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 09:10:34 -0000

> On 24 Jan 2015, at 00:24, Black, David <david.black@emc.com> wrote:
>=20
>> What about:
>>=20
>> NEW
>>  support the most recently published version of DTLS, which was DTLS
>>  1.2 [RFC6347] when this RFC was published.
>> END
>>=20
>> This provides the same information and is simpler. OK?
>=20
> That's ok, but let's not lose the RFC Editor note, e.g., add:
>=20
>  RFC Editor: please ensure that the authors double check the above
>  statement about DTLS 1.2 during AUTH48 and then remove this note
>  before publication.
OK. Added.

Best regards
Michael
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: Friday, January 23, 2015 2:56 PM
>> To: Black, David
>> Cc: Benoit Claise; The IESG; Gorry Fairhurst; =
tsvwg-chairs@tools.ietf.org;
>> tsvwg@ietf.org; draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
>> Subject: Re: [tsvwg] Benoit Claise's No Objection on =
draft-ietf-tsvwg-sctp-
>> dtls-encaps-08: (with COMMENT)
>>=20
>>=20
>>> On 20 Jan 2015, at 22:47, Black, David <david.black@emc.com> wrote:
>>>=20
>>> Benoit,
>>>=20
>>>> The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
>>>> support the most recently published version of DTLS, which is DTLS
>>>> 1.2 [RFC6347] as of December 2014.
>>>>=20
>>>> December 2014 is wrong.
>>>=20
>>> Nitpick department ;-) - as of Dec 2014, DTLS 1.2 [RFC6347] is the =
most
>>> recently published (as an RFC) version of DTLS, even though that RFC =
was
>>> published in Jan 2012, so the quoted text is actually correct ;-).
>>>=20
>>> Nonetheless, here's a clearer suggestion:
>>>=20
>>> OLD
>>>  support the most recently published version of DTLS, which is DTLS
>>>  1.2 [RFC6347] as of December 2014.
>>> NEW
>>>  support the most recently published version of DTLS, which was DTLS
>>>  1.2 [RFC6347] when this RFC was published (XXXXXXXXX 2015).
>>>=20
>>>  RFC Editor: please fill in publication month of this RFC and ensure
>>>  that correctness of the above statement is checked during AUTH48.
>>> END
>> What about:
>>=20
>> NEW
>>  support the most recently published version of DTLS, which was DTLS
>>  1.2 [RFC6347] when this RFC was published.
>> END
>>=20
>> This provides the same information and is simpler. OK?
>>=20
>> Best regards
>> Michael
>>>=20
>>> Thanks,
>>> --David
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Benoit =
Claise
>>>> Sent: Tuesday, January 20, 2015 4:34 PM
>>>> To: The IESG
>>>> Cc: gorry@erg.abdn.ac.uk; tsvwg-chairs@tools.ietf.org; =
tsvwg@ietf.org;
>> draft-
>>>> ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
>>>> Subject: [tsvwg] Benoit Claise's No Objection on =
draft-ietf-tsvwg-sctp-
>> dtls-
>>>> encaps-08: (with COMMENT)
>>>>=20
>>>> Benoit Claise has entered the following ballot position for
>>>> draft-ietf-tsvwg-sctp-dtls-encaps-08: No Objection
>>>>=20
>>>> When responding, please keep the subject line intact and reply to =
all
>>>> email addresses included in the To and CC lines. (Feel free to cut =
this
>>>> introductory paragraph, however.)
>>>>=20
>>>>=20
>>>> Please refer to =
http://www.ietf.org/iesg/statement/discuss-criteria.html
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>=20
>>>>=20
>>>> The document, along with other ballot positions, can be found here:
>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
>>>>=20
>>>>=20
>>>>=20
>>>> =
----------------------------------------------------------------------
>>>> COMMENT:
>>>> =
----------------------------------------------------------------------
>>>>=20
>>>> The DTLS implementation MUST support DTLS 1.0 [RFC4347] and SHOULD
>>>> support the most recently published version of DTLS, which is DTLS
>>>> 1.2 [RFC6347] as of December 2014.
>>>>=20
>>>> December 2014 is wrong.
>>>>=20
>>>=20
>=20
>=20


From nobody Sat Jan 24 09:02:11 2015
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A41FE1A89F2 for <tsvwg@ietfa.amsl.com>; Sat, 24 Jan 2015 09:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 e1a5M-8pqsz3 for <tsvwg@ietfa.amsl.com>; Sat, 24 Jan 2015 09:02:09 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 288441A89F0 for <tsvwg@ietf.org>; Sat, 24 Jan 2015 09:02:09 -0800 (PST)
Received: from [192.168.1.11] (pool-71-103-148-202.lsanca.dsl-w.verizon.net [71.103.148.202]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id t0OH1qcw002572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 24 Jan 2015 09:01:55 -0800 (PST)
Message-ID: <54C3CFFF.3030202@isi.edu>
Date: Sat, 24 Jan 2015 09:01:51 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <20150123220911.26781.11988.idtracker@ietfa.amsl.com> <54C2DF5D.8040800@isi.edu>
In-Reply-To: <54C2DF5D.8040800@isi.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/lFSNiZw467XANPPbvzdciDeTrmQ>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 17:02:10 -0000

FYI, those changes are summarized here:

---

OPS review by Tim Wicinski

	- typo (fixed)

	- suggestion to summarize MUST/MAY/SHOULDs
	in an appendix (discussed and withdrawn)

GEN-ART review by Dan Romascanu

	- suggestion to unify use of "application
	and service designers" and avoid "system
	designers" (done)

	- a request to address privacy considerations
	(done as an additional paragraph in Security
	Considerations)

review by Pearl Liang (IANA)

	- suggestion to revise IANA considerations (done)

review by Alexey Melnikov

	- suggested revision of how IANA is referred to when
	certain decisions are reached (done)

review by Michelle Cotton (IANA)

	- various typos (fixed)
	- issues similar to those raised by Alexey

----

On 1/23/2015 3:55 PM, Joe Touch wrote:
> Hi, all,
>
> This update includes minor changes to address IETF LC comments.
>
> Joe
>
> On 1/23/2015 2:09 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 Transport Area Working Group Working Group of the IETF.
>>
>>          Title           : Recommendations for Transport Port Number Uses
>>          Author          : Joe Touch
>> 	Filename        : draft-ietf-tsvwg-port-use-07.txt
>> 	Pages           : 22
>> 	Date            : 2015-01-23
>>
>> Abstract:
>>     This document provides recommendations to application and service
>>     designers on how to use the transport protocol port number space. It
>>     complements (but does not update) RFC6335, which focuses on IANA
>>     process.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-port-use-07
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-07
>>
>>
>> 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 Sat Jan 24 12:53:18 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C70441A0065; Sat, 24 Jan 2015 12:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Br1x8WpLvSWh; Sat, 24 Jan 2015 12:53:12 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 64FD91A0063; Sat, 24 Jan 2015 12:53:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150124205312.3955.92757.idtracker@ietfa.amsl.com>
Date: Sat, 24 Jan 2015 12:53:12 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/eOX6veTBKlTJqAsjy5iDtb5OzIA>
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-09.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 20:53:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : DTLS Encapsulation of SCTP Packets
        Authors         : Michael Tuexen
                          Randall R. Stewart
                          Randell Jesup
                          Salvatore Loreto
	Filename        : draft-ietf-tsvwg-sctp-dtls-encaps-09.txt
	Pages           : 10
	Date            : 2015-01-24

Abstract:
   The Stream Control Transmission Protocol (SCTP) is a transport
   protocol originally defined to run on top of the network protocols
   IPv4 or IPv6.  This document specifies how SCTP can be used on top of
   the Datagram Transport Layer Security (DTLS) protocol.  Using the
   encapsulation method described in this document, SCTP is unaware of
   the protocols being used below DTLS; hence explicit IP addresses
   cannot be used in the SCTP control chunks.  As a consequence, the
   SCTP associations carried over DTLS can only be single homed.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-dtls-encaps-09


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 Sat Jan 24 12:53:20 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3101A0065 for <tsvwg@ietfa.amsl.com>; Sat, 24 Jan 2015 12:53:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 FeMrr0agM8bS; Sat, 24 Jan 2015 12:53:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 801DB1A0066; Sat, 24 Jan 2015 12:53:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org, spencerdawkins.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150124205312.3955.60365.idtracker@ietfa.amsl.com>
Date: Sat, 24 Jan 2015 12:53:12 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/kpaUmNEYWJyiJnGGInd68on6bjQ>
Subject: [tsvwg] New Version Notification - draft-ietf-tsvwg-sctp-dtls-encaps-09.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 20:53:14 -0000

A new version (-09) has been submitted for draft-ietf-tsvwg-sctp-dtls-encaps:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-dtls-encaps-09.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-dtls-encaps-09

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.

IETF Secretariat.


From nobody Mon Jan 26 03:10:19 2015
Return-Path: <barryleiba@computer.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74B2A1A8900; Mon, 26 Jan 2015 03:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 PthH1luILWf2; Mon, 26 Jan 2015 03:09:47 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A51031A88FE; Mon, 26 Jan 2015 03:09:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Barry Leiba" <barryleiba@computer.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126110943.8665.16178.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 03:09:43 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/1pxu7DjL65ksQhMWElAy3M2tYdg>
Cc: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
Subject: [tsvwg] Barry Leiba's Discuss on draft-ietf-tsvwg-sctp-prpolicies-06: (with DISCUSS and COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 11:09:52 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-tsvwg-sctp-prpolicies-06: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I have four things I'd like to discuss; three are up here, and one is
down in the non-blocking comments.

1. Section 4 says this:

   Please note that this section is informational only.

How are sections 4.2 thru 4.5 not normative?

2. The table in Section 4.2 shows the two policies that come out of RFC
6458 and the two that come from this document.  Is this the time to
create a registry for these?

3. In Section 6, you say that this adds no security considerations.  Are
there really no security considerations introduced by new conditions
under which messages can be abandoned?  And who determines the message
priorities?  Are there no security considerations involved in that
determination?  Is there no discussion at all that might be useful in
determining reasonable values for Limited Retransmission Policy?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

-- Section 3.1 --

   The Limited Retransmissions Policy can be used with data channels in
   the WebRTC protocol stack.  See [I-D.ietf-rtcweb-data-channel] for
   more information.

This isn't a DISCUSS, because I don't think I want to block the document
on this, but I would like to discuss it:  Is this meant to put
restrictions on where the Limited Retransmissions Policy can be used?  If
so, it should be clearer about that.  If not, what's the reason for this
specific shout-out?

The same question applies to this paragraph from Section 3.2:

   The Priority Policy can be used in the IPFIX protocol stack.  See
   [RFC7011] for more information.


-- Section 3.2 --

   When storing a user message in the send buffer
   while there is not enough available space, the SCTP stack at the
   sender side MAY abandon other user messages of the same SCTP
   association with a priority lower than the provided one.  The
   algorithm for selecting the message being abandoned is implementation
   specific.

A minor point: the first part is written as allowing multiple messages to
be abandoned, and the last sentence is written in the singular.  Should
the second part say "message(s)" ?



From nobody Mon Jan 26 03:51:03 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA7AF1A8934; Mon, 26 Jan 2015 03:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level: 
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] 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 P0xWNa264iw3; Mon, 26 Jan 2015 03:50:55 -0800 (PST)
Received: from mailms.fh-muenster.de (mail.fh-muenster.de [212.201.120.190]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DBB91A894F; Mon, 26 Jan 2015 03:50:55 -0800 (PST)
Received: from [192.168.1.200] (p508F01E3.dip0.t-ipconnect.de [80.143.1.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: tuexen) by mailms.fh-muenster.de (Postfix) with ESMTPSA id BA862280CF8; Mon, 26 Jan 2015 12:50:52 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <20150126110943.8665.16178.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 12:50:51 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <25CEAA89-36CD-4DFA-A134-8AFF328CD4A2@fh-muenster.de>
References: <20150126110943.8665.16178.idtracker@ietfa.amsl.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/xX0Nt-JuSc5OEa9ClsKb76hW2fc>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, The IESG <iesg@ietf.org>, tsvwg@ietf.org
Subject: Re: [tsvwg] Barry Leiba's Discuss on draft-ietf-tsvwg-sctp-prpolicies-06: (with DISCUSS and COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 11:50:57 -0000

> On 26 Jan 2015, at 12:09, Barry Leiba <barryleiba@computer.org> wrote:
> 
> Barry Leiba has entered the following ballot position for
> draft-ietf-tsvwg-sctp-prpolicies-06: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
Barry,

thank you very much for your review. See my comments in-line.

Best regards
Michael
> I have four things I'd like to discuss; three are up here, and one is
> down in the non-blocking comments.
> 
> 1. Section 4 says this:
> 
>   Please note that this section is informational only.
> 
> How are sections 4.2 thru 4.5 not normative?
Section 4 (and all the subsections) deal with the socket API. Up to know
the socket API for SCTP has "only" be specified informational. See
the informational RFC
https://tools.ietf.org/html/rfc6458
and the socket API sections in extensions not covered by the above RFC:
https://tools.ietf.org/html/rfc6525#section-6
https://tools.ietf.org/html/rfc7053#section-7
So for consistency it would be good to keep it that way.

The socket API for IPv6
http://tools.ietf.org/html/rfc3542.html
was also done this way.
> 
> 2. The table in Section 4.2 shows the two policies that come out of RFC
> 6458 and the two that come from this document.  Is this the time to
> create a registry for these?
Hmm. IANA normally doesn't manage values used only in the socket API.
We just specify the name of the constant and leave the numeric value
up to the implementation. Therefore you get portable source code, but
not portable binaries...
> 
> 3. In Section 6, you say that this adds no security considerations.  Are
> there really no security considerations introduced by new conditions
> under which messages can be abandoned?  And who determines the message
https://tools.ietf.org/html/rfc3758#section-7
discusses the generic security issues related to using PR-SCTP. I don't
see any additional ones. Please note that the policies are processed
only on the local node only for the affected association. So a user program
using one socket can't hurt a program using other sockets.
> priorities?  Are there no security considerations involved in that
> determination?  Is there no discussion at all that might be useful in
I don't see how one association can hurt another...
> determining reasonable values for Limited Retransmission Policy?
That is up to the application. One value (using 0) is discussed in
the second paragraph of
https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-prpolicies-06#section-3.1
but again: I don't see any security related issue from a specific
policy.
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> -- Section 3.1 --
> 
>   The Limited Retransmissions Policy can be used with data channels in
>   the WebRTC protocol stack.  See [I-D.ietf-rtcweb-data-channel] for
>   more information.
> 
> This isn't a DISCUSS, because I don't think I want to block the document
> on this, but I would like to discuss it:  Is this meant to put
> restrictions on where the Limited Retransmissions Policy can be used?  If
> so, it should be clearer about that.  If not, what's the reason for this
> specific shout-out?
It is not meant to put any kind of restrictions on the uses. It is
meant to provide an example where it is used. Data channel can
be configured to use this policy, but they can also use a different
policy or they can be reliable. That is way we used the formulation
"can be used"...
> 
> The same question applies to this paragraph from Section 3.2:
> 
>   The Priority Policy can be used in the IPFIX protocol stack.  See
>   [RFC7011] for more information.
Same answer as above. It is meant as an example.
> 
> 
> -- Section 3.2 --
> 
>   When storing a user message in the send buffer
>   while there is not enough available space, the SCTP stack at the
>   sender side MAY abandon other user messages of the same SCTP
>   association with a priority lower than the provided one.  The
>   algorithm for selecting the message being abandoned is implementation
>   specific.
> 
> A minor point: the first part is written as allowing multiple messages to
> be abandoned, and the last sentence is written in the singular.  Should
> the second part say "message(s)" ?
Good point. It should read:
   Using the Priority Policy allows the sender of a user message to
   specify a priority.  When storing a user message in the send buffer
   while there is not enough available space, the SCTP stack at the
   sender side MAY abandon other user message(s) of the same SCTP
   association with a priority lower than the provided one.  The
   algorithm for selecting the message(s) being abandoned is
   implementation specific.
OK?
> 
> 
> 


From nobody Mon Jan 26 04:19:10 2015
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD0C1A8968 for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 04:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 3N8P5nU6E06q for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 04:19:01 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D81941A8A12 for <tsvwg@ietf.org>; Mon, 26 Jan 2015 04:19:00 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id t0QCIuPD014249 for <tsvwg@ietf.org>; Mon, 26 Jan 2015 13:18:56 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
References: <20150126121737.13533.9103.idtracker@ietfa.amsl.com>
In-Reply-To: <20150126121737.13533.9103.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 13:19:06 +0100
Message-ID: <002301d03962$47f87d70$d7e97850$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHK6uLDq8t14N5bWJP8qoGNjOMJOZzc7rVA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/XihKMEwwrbQP9W5ak6b7_eJXf8Q>
Subject: [tsvwg] RV: New Version Notification for draft-saldana-tsvwg-simplemux-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 12:19:08 -0000

> -----Mensaje original-----
> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Enviado el: lunes, 26 de enero de 2015 13:18
> Para: Jose Saldana; Jose Saldana
> Asunto: New Version Notification for =
draft-saldana-tsvwg-simplemux-02.txt
>=20
>=20
> A new version of I-D, draft-saldana-tsvwg-simplemux-02.txt
> has been successfully submitted by Jose Saldana and posted to the IETF
> repository.
>=20
> Name:		draft-saldana-tsvwg-simplemux
> Revision:	02
> Title:		Simplemux. A generic multiplexing protocol
> Document date:	2015-01-26
> Group:		Individual Submission
> Pages:		11
> URL:            =
http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-simplemux-02.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/
> Htmlized:       =
http://tools.ietf.org/html/draft-saldana-tsvwg-simplemux-02
> Diff:           =
http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-simplemux-02
>=20
> Abstract:
>    There are some situations in which multiplexing a number of small
>    packets into a bigger one is desirable.  For example, a number of
>    small packets can be sent together between a pair of machines if =
they
>    share a common network path.  Thus, the traffic profile can be
>    shifted from small to larger packets, reducing the network overhead
>    and the number of packets per second to be managed by intermediate
>    routers.
>=20
>    This document describes Simplemux, a protocol able to encapsulate a
>    number of packets belonging to different protocols into a single
>    packet.  It includes the "Protocol" field on each multiplexing
>    header, thus allowing the inclusion of a number of packets =
belonging
>    to different protocols on a packet of another protocol.
>=20
>    The size of the multiplexing headers is kept very low (it may be a
>    single byte when multiplexing small packets) in order to reduce the
>    overhead.
>=20
>=20
>=20
>=20
> 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.
>=20
> The IETF Secretariat



From nobody Mon Jan 26 05:11:51 2015
Return-Path: <barryleiba@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3871A8A68; Mon, 26 Jan 2015 05:11:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, 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 ZbJwrvFfckHB; Mon, 26 Jan 2015 05:11:44 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72FF51A1A39; Mon, 26 Jan 2015 05:11:44 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id z12so7391006lbi.7; Mon, 26 Jan 2015 05:11:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fQmnkmPOV/3LZve7PzmI4LftYgPj+1w79m2XTPDSISc=; b=FD3c5jSLNiAeHIykFF4tpYnOMeCHQgHn6pLqIyejYk0C/cP19KesbVeBIQ4l+WG1F1 m2zIDGU68wGF4VABt6E0PHn4gc6lhC8gwhYScmvglvw/Gx47GkO3nrh6bv9dHQkgSfBK grosp2WTgE0FZf3zzKAFecrw5sg+WGdqtqaD6luFXRLvvgM4+7WV4WnSaTl4ZLKY/3pz EHadVuFFqabvuB3wUwQJbb+2BxNLp7lQ+7slAIz9UfYNHDFYWvaG1pzqxiWLahUWkrE5 FQF6SoVjoPI4YkncVYmoJR/Yv7cAnm0kMrgmWySTbLBTvyb8YwX66KxGofOUNQFHK3l1 ovjQ==
MIME-Version: 1.0
X-Received: by 10.152.27.130 with SMTP id t2mr20625623lag.28.1422277902814; Mon, 26 Jan 2015 05:11:42 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.168 with HTTP; Mon, 26 Jan 2015 05:11:42 -0800 (PST)
In-Reply-To: <25CEAA89-36CD-4DFA-A134-8AFF328CD4A2@fh-muenster.de>
References: <20150126110943.8665.16178.idtracker@ietfa.amsl.com> <25CEAA89-36CD-4DFA-A134-8AFF328CD4A2@fh-muenster.de>
Date: Mon, 26 Jan 2015 08:11:42 -0500
X-Google-Sender-Auth: 64BBS7V8RwNUPSwEPqIS9GmGJEA
Message-ID: <CALaySJKSFfFtmgME8fhimQu9PayJm_Ni7xLtHRWL+G7-KBevTQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/2hGgLsZFFKh-U4e5im67Q160Sew>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg chair <tsvwg-chairs@tools.ietf.org>, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, The IESG <iesg@ietf.org>, tsvwg@ietf.org
Subject: Re: [tsvwg] Barry Leiba's Discuss on draft-ietf-tsvwg-sctp-prpolicies-06: (with DISCUSS and COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 13:11:46 -0000

Great; thanks for the quick response, Michael.

>> How are sections 4.2 thru 4.5 not normative?
>
> Section 4 (and all the subsections) deal with the socket API. Up to know
> the socket API for SCTP has "only" be specified informational.

Ack; I'll clear this.

>> 2. The table in Section 4.2 shows the two policies that come out of RFC
>> 6458 and the two that come from this document.  Is this the time to
>> create a registry for these?
>
> Hmm. IANA normally doesn't manage values used only in the socket API.
> We just specify the name of the constant and leave the numeric value
> up to the implementation. Therefore you get portable source code, but
> not portable binaries...

But is there not any value in having a list of the names that are in
use, with references to where they're defined?  I'll clear this and
move it to a comment; no need to further respond, but please think
about whether it'd be useful (or not) to have an FCFS registry for
these, even if just for reference purposes.

>> 3. In Section 6, you say that this adds no security considerations.  Are
>> there really no security considerations introduced by new conditions
>> under which messages can be abandoned?  And who determines the message
...
> Please note that the policies are processed
> only on the local node only for the affected association. So a user program
> using one socket can't hurt a program using other sockets.

Yes, I get that, and I guess that answers any questions about an
attacker inserting priority 0 messages, or the like.  I'll clear this
one too.

On the non-blocking stuff...

>> -- Section 3.1 --
>>
>>   The Limited Retransmissions Policy can be used with data channels in
>>   the WebRTC protocol stack.  See [I-D.ietf-rtcweb-data-channel] for
>>   more information.
...
> It is not meant to put any kind of restrictions on the uses. It is
> meant to provide an example where it is used. Data channel can
> be configured to use this policy, but they can also use a different
> policy or they can be reliable. That is way we used the formulation
> "can be used"...

Ack.  But I wonder whether implementors might misunderstand, and think
it's meant to be restrictive.  Again, no need to further respond...
but please consider changing the wording (here and in 3.2) to
something like this:

NEW
   The Limited Retransmissions Policy was designed to be used with
   data channels in the WebRTC protocol stack (see
   [I-D.ietf-rtcweb-data-channel]), and can also be used in other
   appropriate situations.
END

...or maybe...

NEW
   The WebRTC protocol stack (see [I-D.ietf-rtcweb-data-channel]), is
   an example of where the Limited Retransmissions Policy might be
   used.
END

Thanks.  Off to clear the DISCUSS now.

Barry


From nobody Mon Jan 26 05:14:57 2015
Return-Path: <barryleiba@computer.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B799C1A8A90; Mon, 26 Jan 2015 05:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 SzFhzH0GhwkD; Mon, 26 Jan 2015 05:14:48 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D48031A8714; Mon, 26 Jan 2015 05:14:48 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Barry Leiba" <barryleiba@computer.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126131448.2086.85085.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 05:14:48 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/mnwJF8gGINzkpga8-NQLeB5iaqs>
Cc: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
Subject: [tsvwg] Barry Leiba's No Objection on draft-ietf-tsvwg-sctp-prpolicies-06: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 13:14:52 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-tsvwg-sctp-prpolicies-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

-- Section 3.1 --

   The Limited Retransmissions Policy can be used with data channels in
   the WebRTC protocol stack.  See [I-D.ietf-rtcweb-data-channel] for
   more information.

I wonder whether implementors might misunderstand, and think this is
meant to be restrictive.  Please consider changing the wording (here and
in 3.2) to something like this:

NEW
   The Limited Retransmissions Policy was designed to be used with
   data channels in the WebRTC protocol stack (see
   [I-D.ietf-rtcweb-data-channel]), and can also be used in other
   appropriate situations.
END

...or maybe...

NEW
   The WebRTC protocol stack (see [I-D.ietf-rtcweb-data-channel]), is
   an example of where the Limited Retransmissions Policy might be
   used.
END

-- Section 3.2 --

   When storing a user message in the send buffer
   while there is not enough available space, the SCTP stack at the
   sender side MAY abandon other user messages of the same SCTP
   association with a priority lower than the provided one.  The
   algorithm for selecting the message being abandoned is implementation
   specific.

A minor point: the first part is written as allowing multiple messages to
be abandoned, and the last sentence is written in the singular.  Should
the second part say "message(s)" ?

-- Section 4.2 --

The table shows the two policies that come out of RFC 6458 and the two
that come from this document.  Is it worth it to create a (FCFS?)
registry for these names, to document them and provide references?



From nobody Mon Jan 26 06:38:17 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7268C1A8A9C for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 06:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 LEq-dcErUMuM; Mon, 26 Jan 2015 06:38:12 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AD541A8851; Mon, 26 Jan 2015 06:38:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126143812.5850.68923.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 06:38:12 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/cMbawag50o-AIK0cuPWb_Wv1rCY>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-09.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 14:38:13 -0000

IESG has approved the document and state has been changed to Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


From nobody Mon Jan 26 08:30:45 2015
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0D91A9250 for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 08:30:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ZWeTm2AFjsdx for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 08:30:36 -0800 (PST)
Received: from hubrelay-by-03.bt.com (hubrelay-by-03.bt.com [62.7.242.139]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 475AE1A885D for <tsvwg@ietf.org>; Mon, 26 Jan 2015 08:30:35 -0800 (PST)
Received: from EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) by EVMHR03-UKBR.bt.com (10.216.161.35) with Microsoft SMTP Server (TLS) id 8.3.348.2; Mon, 26 Jan 2015 16:30:31 +0000
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) with Microsoft SMTP Server (TLS) id 8.3.348.2; Mon, 26 Jan 2015 16:30:32 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.3.181.6; Mon, 26 Jan 2015 16:30:28 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.111.38.222])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id t0QGUNDL016261;	Mon, 26 Jan 2015 16:30:25 GMT
Message-ID: <201501261630.t0QGUNDL016261@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 26 Jan 2015 13:47:23 +0000
To: "Black, David" <david.black@emc.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936276347@MX104CL02.corp.emc. com>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com> <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm> <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk> <CE03DB3D7B45C245BCA0D24327794936276347@MX104CL02.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/vskMZULq1YUf5qUdrvyBbJOsIrY>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 16:30:39 -0000

David,

Apologies for the ultra-long RTT. Inline...

At 19:03 21/11/2014, Black, David wrote:
>Bob,
>
> > 1) Regarding congestion control, I do not share the position of some
> > others in tsvwg. Congestion responsiveness is determined by how the
> > source spaces out the packets (i.e. their instantaneous rate). Just
> > because a tunnel ingress encapsulates a packet with a UDP header does
> > not suddenly make it unresponsive to congestion. The spacing between
> > packets is still determined by the source. So there is no need to
> > even mention congestion control considerations in a tunneling
> > document, except to say in the scoping at the start that the addition
> > of tunnel headers is completely orthogonal to congestion avoidance and
> > control.
>
>Unfortunately, it's not "completely orthogonal" because UDP goes many
>places that the encapsulated protocols can't.  Hence "can't get there
>from here" protection in NATs and other middleboxes that drop the
>unencapsulated protocol won't stop non-congestion controlled UDP-
>encapsulated traffic from getting into places that it shouldn't and
>causing damage.  Also, please take note of the text in the mpls-in-udp
>draft that recommends filters to block such traffic from going where
>it shouldn't, which restores some of these protections.

OK, that's correct, but I should have phrased my concern differently.

Advice on where an operator should not deploy tunnel endpoints is a 
run-time concern, for which it is appropriate to advise operators 
(and maybe users). A specification like Lucy's is surely solely for 
an implementer audience. Unless we can say there is something that 
must be implemented along with the tunnel encap/decap, surely we 
should not hold Lucy back.

Yes, we should work on circuit breakers for tunnels. But that's for 
the operator audience. We should not take out our frustrations with 
operators on implementers. We should not hold Lucy and others like 
her back for this. She is innocent in this battle.


Bob



>Thanks,
>--David
>
> > -----Original Message-----
> > From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> > Sent: Friday, November 21, 2014 12:30 PM
> > To: Lucy yong
> > Cc: Black, David; tsvwg@ietf.org
> > Subject: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
> >
> > Lucy,
> >
> > I'll wait for David's promised proposal to the list before commenting
> > on the checksum issue.
> >
> > 1) Regarding congestion control, I do not share the position of some
> > others in tsvwg. Congestion responsiveness is determined by how the
> > source spaces out the packets (i.e. their instantaneous rate). Just
> > because a tunnel ingress encapsulates a packet with a UDP header does
> > not suddenly make it unresponsive to congestion. The spacing between
> > packets is still determined by the source. So there is no need to
> > even mention congestion control considerations in a tunnelling
> > document, except to say in the scoping at the start that the addition
> > of tunnel headers is completely orthogonal to congestion avoidance and
> > control.
> >
> > 2)
> > Please replace:
> >     Tunnel end points that support
> >     ECN MUST use the method described in [RFC6040] for ECN marking
> >     propagation.
> > With:
> >     Tunnel end points need to use the method described in [RFC6040]
> > for ECN marking
> >     propagation.
> > Rationale:
> >     i) There is no such thing as a tunnel end point that does not
> > support ECN - it has to put something in the ECN field, and it would
> > not be appropriate to put anything in there other than what RFC6040 says.
> >    ii) Generally it is not a good idea to fill one draft with
> > normative statements that repeat normative statements made in other
> > drafts. Otherwise updating an RFC gets very difficult - we have to
> > update all the other RFCs that gratuitously repeat what it says.
> >
> > 3) Nit in section 3.1.
> >     Section 5 of RFC6936 [RFC6936] specifies the additional requirements
> >     that implementation of UDP zero-checksum over IPv6 MUST compliant
> >     with. To compliant with it, the following additional requirements
> >     apply
> > s/compliant/comply/ (twice)
> >
> > There are other nits, but they can be dealt with later.
> >
> >
> > Cheers
> >
> >
> > Bob
> >
> >
> >
> >
> > ________________________________________________________________
> > Bob Briscoe,                                                  BT

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Mon Jan 26 09:55:41 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B8D91A82E2; Mon, 26 Jan 2015 09:55:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 PgCqUWTAgbNI; Mon, 26 Jan 2015 09:55:33 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A08E1A702E; Mon, 26 Jan 2015 09:55:32 -0800 (PST)
Received: from [192.168.1.200] (p508F01E3.dip0.t-ipconnect.de [80.143.1.227]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 5E38D1C0B4606; Mon, 26 Jan 2015 18:55:29 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CALaySJKSFfFtmgME8fhimQu9PayJm_Ni7xLtHRWL+G7-KBevTQ@mail.gmail.com>
Date: Mon, 26 Jan 2015 18:55:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <47BDB981-5095-4BCB-8A0E-CA1BE971EA53@fh-muenster.de>
References: <20150126110943.8665.16178.idtracker@ietfa.amsl.com> <25CEAA89-36CD-4DFA-A134-8AFF328CD4A2@fh-muenster.de> <CALaySJKSFfFtmgME8fhimQu9PayJm_Ni7xLtHRWL+G7-KBevTQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/YFyjUN5f7-D2w_anR24eNpAAEy0>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg chair <tsvwg-chairs@tools.ietf.org>, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, The IESG <iesg@ietf.org>, tsvwg@ietf.org
Subject: Re: [tsvwg] Barry Leiba's Discuss on draft-ietf-tsvwg-sctp-prpolicies-06: (with DISCUSS and COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 17:55:39 -0000

> On 26 Jan 2015, at 14:11, Barry Leiba <barryleiba@computer.org> wrote:
>=20
> Great; thanks for the quick response, Michael.
>=20
>>> How are sections 4.2 thru 4.5 not normative?
>>=20
>> Section 4 (and all the subsections) deal with the socket API. Up to =
know
>> the socket API for SCTP has "only" be specified informational.
>=20
> Ack; I'll clear this.
OK.
>=20
>>> 2. The table in Section 4.2 shows the two policies that come out of =
RFC
>>> 6458 and the two that come from this document.  Is this the time to
>>> create a registry for these?
>>=20
>> Hmm. IANA normally doesn't manage values used only in the socket API.
>> We just specify the name of the constant and leave the numeric value
>> up to the implementation. Therefore you get portable source code, but
>> not portable binaries...
>=20
> But is there not any value in having a list of the names that are in
> use, with references to where they're defined?  I'll clear this and
> move it to a comment; no need to further respond, but please think
> about whether it'd be useful (or not) to have an FCFS registry for
> these, even if just for reference purposes.
We do have lots of these, for example the namespace of all SCTP level
socket options. I don't think IANA manages anything like this right now.
And implementations might have additional constants being used. The
number of kernel implementations is small (Linux, Solaris, FreeBSD)
and we get all of these normally involved in a review. So it wasn't
an issue up to now.
>=20
>>> 3. In Section 6, you say that this adds no security considerations.  =
Are
>>> there really no security considerations introduced by new conditions
>>> under which messages can be abandoned?  And who determines the =
message
> ...
>> Please note that the policies are processed
>> only on the local node only for the affected association. So a user =
program
>> using one socket can't hurt a program using other sockets.
>=20
> Yes, I get that, and I guess that answers any questions about an
> attacker inserting priority 0 messages, or the like.  I'll clear this
> one too.
>=20
> On the non-blocking stuff...
>=20
>>> -- Section 3.1 --
>>>=20
>>>  The Limited Retransmissions Policy can be used with data channels =
in
>>>  the WebRTC protocol stack.  See [I-D.ietf-rtcweb-data-channel] for
>>>  more information.
> ...
>> It is not meant to put any kind of restrictions on the uses. It is
>> meant to provide an example where it is used. Data channel can
>> be configured to use this policy, but they can also use a different
>> policy or they can be reliable. That is way we used the formulation
>> "can be used"...
>=20
> Ack.  But I wonder whether implementors might misunderstand, and think
> it's meant to be restrictive.  Again, no need to further respond...
> but please consider changing the wording (here and in 3.2) to
> something like this:
>=20
> NEW
>   The Limited Retransmissions Policy was designed to be used with
>   data channels in the WebRTC protocol stack (see
>   [I-D.ietf-rtcweb-data-channel]), and can also be used in other
>   appropriate situations.
> END
>=20
> ...or maybe...
>=20
> NEW
>   The WebRTC protocol stack (see [I-D.ietf-rtcweb-data-channel]), is
>   an example of where the Limited Retransmissions Policy might be
>   used.
> END
OK. What about:
<t>The WebRTC protocol stack (see <xref =
target=3D'I-D.ietf-rtcweb-data-channel'/>),
is an example of where the Limited Retransmissions Policy is used.</t>

and

<t>The IPFIX protocol stack (see <xref target=3D'RFC7011'/>) is an =
example
of where the Priority Policy can be used.</t>

Best regards
Michael
>=20
> Thanks.  Off to clear the DISCUSS now.
>=20
> Barry
>=20


From nobody Mon Jan 26 09:58:12 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DDE91ACCE4; Mon, 26 Jan 2015 09:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 xEXetW23Jgsj; Mon, 26 Jan 2015 09:58:09 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F94B1ACD12; Mon, 26 Jan 2015 09:58:07 -0800 (PST)
Received: from [192.168.1.200] (p508F01E3.dip0.t-ipconnect.de [80.143.1.227]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id D8C681C0B4606; Mon, 26 Jan 2015 18:58:04 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <20150126131448.2086.85085.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 18:58:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA83AF18-BF00-4DC8-ADC0-7B53AF20A204@fh-muenster.de>
References: <20150126131448.2086.85085.idtracker@ietfa.amsl.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/xxBrQpRrKvCxKrjv6piTT-__cJQ>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, The IESG <iesg@ietf.org>, tsvwg@ietf.org
Subject: Re: [tsvwg] Barry Leiba's No Objection on draft-ietf-tsvwg-sctp-prpolicies-06: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 17:58:10 -0000

> On 26 Jan 2015, at 14:14, Barry Leiba <barryleiba@computer.org> wrote:
>=20
> Barry Leiba has entered the following ballot position for
> draft-ietf-tsvwg-sctp-prpolicies-06: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> -- Section 3.1 --
>=20
>   The Limited Retransmissions Policy can be used with data channels in
>   the WebRTC protocol stack.  See [I-D.ietf-rtcweb-data-channel] for
>   more information.
>=20
> I wonder whether implementors might misunderstand, and think this is
> meant to be restrictive.  Please consider changing the wording (here =
and
> in 3.2) to something like this:
>=20
> NEW
>   The Limited Retransmissions Policy was designed to be used with
>   data channels in the WebRTC protocol stack (see
>   [I-D.ietf-rtcweb-data-channel]), and can also be used in other
>   appropriate situations.
> END
>=20
> ...or maybe...
>=20
> NEW
>   The WebRTC protocol stack (see [I-D.ietf-rtcweb-data-channel]), is
>   an example of where the Limited Retransmissions Policy might be
>   used.
> END
I prefer the second one.

I changed the text to
<t>The WebRTC protocol stack (see <xref =
target=3D'I-D.ietf-rtcweb-data-channel'/>),
is an example of where the Limited Retransmissions Policy is used.</t>

and for consistency

<t>The IPFIX protocol stack (see <xref target=3D'RFC7011'/>) is an =
example
of where the Priority Policy can be used.</t>
>=20
> -- Section 3.2 --
>=20
>   When storing a user message in the send buffer
>   while there is not enough available space, the SCTP stack at the
>   sender side MAY abandon other user messages of the same SCTP
>   association with a priority lower than the provided one.  The
>   algorithm for selecting the message being abandoned is =
implementation
>   specific.
>=20
> A minor point: the first part is written as allowing multiple messages =
to
> be abandoned, and the last sentence is written in the singular.  =
Should
> the second part say "message(s)" ?
Already fixed:
<t>Using the Priority Policy allows the sender of a user message to =
specify
a priority. When storing a user message in the send buffer while there =
is not
enough available space, the SCTP stack at the sender side MAY abandon =
other
user message(s) of the same SCTP association with a priority lower than =
the
provided one. The algorithm for selecting the message(s) being abandoned =
is
implementation specific.</t>
>=20
> -- Section 4.2 --
>=20
> The table shows the two policies that come out of RFC 6458 and the two
> that come from this document.  Is it worth it to create a (FCFS?)
> registry for these names, to document them and provide references?
See my earlier response.

Best regards
Michael
>=20
>=20
>=20


From nobody Mon Jan 26 10:00:18 2015
Return-Path: <barryleiba@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA9C61A1BE5; Mon, 26 Jan 2015 10:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, 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 SxqzvPYU9e1S; Mon, 26 Jan 2015 10:00:13 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4FF91A1BDD; Mon, 26 Jan 2015 10:00:12 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id pv20so9031068lab.7; Mon, 26 Jan 2015 10:00:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=TiNDbv+8Dk3pKZM4PNnqVxDxtBjZKn5qmgiiSs45/qI=; b=wcI8yR61Y9DmxOARM9c23zzxPVNs1t8pp7tLSUcW2Un8gt5drYQJgJ1mzcj8YaH1NJ dyhx3XikCi9JWt1wW8WxdsJ59YIBN9jWKd+Be20Fw1u1P6Km1LJx5JsiHAsS4jdsvOcg S5iOI3CSqWBRdF66b2pzD9C1VFbvwPQeeQGT8/1S1kqc/8ilehlwPQg83dyTcyftS3Yx oMtrailSIFEQA37y+K5KyXvGGvp55+qY2mAtIGhRDoVKQlubCj62FNjqdboKGbtG0Vne /i7N3XZZQJA+N/IuTqcNTBW9bhV5+HnhiPe+05Y487RLxc3e4wQsUYbYmnr4+0X5GQuH ygNg==
MIME-Version: 1.0
X-Received: by 10.152.22.67 with SMTP id b3mr22956523laf.82.1422295211317; Mon, 26 Jan 2015 10:00:11 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.168 with HTTP; Mon, 26 Jan 2015 10:00:11 -0800 (PST)
In-Reply-To: <47BDB981-5095-4BCB-8A0E-CA1BE971EA53@fh-muenster.de>
References: <20150126110943.8665.16178.idtracker@ietfa.amsl.com> <25CEAA89-36CD-4DFA-A134-8AFF328CD4A2@fh-muenster.de> <CALaySJKSFfFtmgME8fhimQu9PayJm_Ni7xLtHRWL+G7-KBevTQ@mail.gmail.com> <47BDB981-5095-4BCB-8A0E-CA1BE971EA53@fh-muenster.de>
Date: Mon, 26 Jan 2015 19:00:11 +0100
X-Google-Sender-Auth: 8AcpB2ZbkJM0qsrtsxr8AO3HQ2E
Message-ID: <CALaySJ+Crzn9cjMsKB=-KxfFvQO_Hg3Naa_4v-HkZ8gv7bxuSg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/I-V3bpuqliHmno70LshLXjTJEzM>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg chair <tsvwg-chairs@tools.ietf.org>, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, The IESG <iesg@ietf.org>, tsvwg@ietf.org
Subject: Re: [tsvwg] Barry Leiba's Discuss on draft-ietf-tsvwg-sctp-prpolicies-06: (with DISCUSS and COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 18:00:14 -0000

> OK. What about:
>
> <t>The WebRTC protocol stack (see <xref target='I-D.ietf-rtcweb-data-channel'/>),
> is an example of where the Limited Retransmissions Policy is used.</t>
>
> and
>
> <t>The IPFIX protocol stack (see <xref target='RFC7011'/>) is an example
> of where the Priority Policy can be used.</t>

Sure, that gets the point across too.  Thanks!

Barry


From nobody Mon Jan 26 11:06:35 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F4A1ACEAB for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 11:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 mxrE4dRD2UYa; Mon, 26 Jan 2015 11:06:22 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D251ACE6E; Mon, 26 Jan 2015 11:06:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126190622.29916.40517.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 11:06:22 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/oz7g8ymrG2614h4x61ucm0KQWMI>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-09.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 19:06:24 -0000

IANA action state changed to In Progress
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


From nobody Mon Jan 26 11:06:44 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E73F1ACEA2 for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 11:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 CZtWOIwnPFaD; Mon, 26 Jan 2015 11:06:27 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C4A1ACEA3; Mon, 26 Jan 2015 11:06:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126190623.29916.74437.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 11:06:23 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/kHcIkICJv40KP3ZaGTntdbO04tI>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-09.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 19:06:33 -0000

IANA action state changed to No IC
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


From nobody Mon Jan 26 11:16:55 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC141ACEA7 for <tsvwg@ietfa.amsl.com>; Mon, 26 Jan 2015 11:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 vUxTbkc_MidX; Mon, 26 Jan 2015 11:16:47 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35EE61A8BC3; Mon, 26 Jan 2015 11:16:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, tsvwg@ietf.org, draft-ietf-tsvwg-sctp-dtls-encaps.all@tools.ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126191647.23450.3512.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 11:16:47 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/lacIcwcOu4Hh-xvM9Rg8okJ_Oh4>
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-dtls-encaps-09.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 19:16:53 -0000

IESG state changed to RFC Ed Queue from Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


From nobody Tue Jan 27 00:37:42 2015
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0823F1A8737 for <tsvwg@ietfa.amsl.com>; Tue, 27 Jan 2015 00:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 DvmqeX1POG9E for <tsvwg@ietfa.amsl.com>; Tue, 27 Jan 2015 00:37:30 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5B041A700C for <tsvwg@ietf.org>; Tue, 27 Jan 2015 00:37:29 -0800 (PST)
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0R8bNLO026846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Jan 2015 03:37:24 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t0R8bNLO026846
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1422347844; bh=ZI+KDe8MOMjHT0g9/O/qZAYcK9c=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=NITlDNr6nR8e+DZ7WacxmtAu3tpOgGbqJBgyAKfSjU0JMgOHb5nnMPt4yXLXdXehU lApFsfoYtdWVkXI3wfWjIuSJtXL73WxDksk4sxtKCAFxp7li3NwTDgE0OmY3yTduDg AR0179cmG/vN0cu0m1FjyiaekEan/ZftgsqecByc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t0R8bNLO026846
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd51.lss.emc.com (RSA Interceptor); Tue, 27 Jan 2015 03:36:54 -0500
Received: from mxhub39.corp.emc.com (mxhub39.corp.emc.com [128.222.70.106]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t0R8b7OL031726 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jan 2015 03:37:07 -0500
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub39.corp.emc.com (128.222.70.106) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 27 Jan 2015 03:37:07 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.208]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Tue, 27 Jan 2015 03:37:07 -0500
From: "Black, David" <david.black@emc.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Thread-Topic: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
Thread-Index: AQHQBbFgNPxZKlPnckibF3usr/uACpxrbU8QgGeSUpeAAQwxcA==
Date: Tue, 27 Jan 2015 08:37:06 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936319E14@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com> <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm> <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk> <CE03DB3D7B45C245BCA0D24327794936276347@MX104CL02.corp.emc.com> <201501261630.t0QGUNDL016261@bagheera.jungle.bt.co.uk>
In-Reply-To: <201501261630.t0QGUNDL016261@bagheera.jungle.bt.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.76.190.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/CNh1JlZBEeN6IR6fW8c0poOPzP8>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 08:37:39 -0000

> A specification like Lucy's is surely solely for
> an implementer audience.

With my OPS Directorate member hat on (and WG chair hat off), I
definitely disagree ...

... we routinely review all drafts for appropriate operational
considerations - see RFC 5706, and in particular Appendix A.1,
which is definitely applicable to this draft.

Thanks,
--David

> -----Original Message-----
> From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> Sent: Monday, January 26, 2015 8:47 AM
> To: Black, David
> Cc: tsvwg@ietf.org
> Subject: RE: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
>=20
> David,
>=20
> Apologies for the ultra-long RTT. Inline...
>=20
> At 19:03 21/11/2014, Black, David wrote:
> >Bob,
> >
> > > 1) Regarding congestion control, I do not share the position of some
> > > others in tsvwg. Congestion responsiveness is determined by how the
> > > source spaces out the packets (i.e. their instantaneous rate). Just
> > > because a tunnel ingress encapsulates a packet with a UDP header does
> > > not suddenly make it unresponsive to congestion. The spacing between
> > > packets is still determined by the source. So there is no need to
> > > even mention congestion control considerations in a tunneling
> > > document, except to say in the scoping at the start that the addition
> > > of tunnel headers is completely orthogonal to congestion avoidance an=
d
> > > control.
> >
> >Unfortunately, it's not "completely orthogonal" because UDP goes many
> >places that the encapsulated protocols can't.  Hence "can't get there
> >from here" protection in NATs and other middleboxes that drop the
> >unencapsulated protocol won't stop non-congestion controlled UDP-
> >encapsulated traffic from getting into places that it shouldn't and
> >causing damage.  Also, please take note of the text in the mpls-in-udp
> >draft that recommends filters to block such traffic from going where
> >it shouldn't, which restores some of these protections.
>=20
> OK, that's correct, but I should have phrased my concern differently.
>=20
> Advice on where an operator should not deploy tunnel endpoints is a
> run-time concern, for which it is appropriate to advise operators
> (and maybe users). A specification like Lucy's is surely solely for
> an implementer audience. Unless we can say there is something that
> must be implemented along with the tunnel encap/decap, surely we
> should not hold Lucy back.
>=20
> Yes, we should work on circuit breakers for tunnels. But that's for
> the operator audience. We should not take out our frustrations with
> operators on implementers. We should not hold Lucy and others like
> her back for this. She is innocent in this battle.
>=20
>=20
> Bob
>=20
>=20
>=20
> >Thanks,
> >--David
> >
> > > -----Original Message-----
> > > From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> > > Sent: Friday, November 21, 2014 12:30 PM
> > > To: Lucy yong
> > > Cc: Black, David; tsvwg@ietf.org
> > > Subject: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
> > >
> > > Lucy,
> > >
> > > I'll wait for David's promised proposal to the list before commenting
> > > on the checksum issue.
> > >
> > > 1) Regarding congestion control, I do not share the position of some
> > > others in tsvwg. Congestion responsiveness is determined by how the
> > > source spaces out the packets (i.e. their instantaneous rate). Just
> > > because a tunnel ingress encapsulates a packet with a UDP header does
> > > not suddenly make it unresponsive to congestion. The spacing between
> > > packets is still determined by the source. So there is no need to
> > > even mention congestion control considerations in a tunnelling
> > > document, except to say in the scoping at the start that the addition
> > > of tunnel headers is completely orthogonal to congestion avoidance an=
d
> > > control.
> > >
> > > 2)
> > > Please replace:
> > >     Tunnel end points that support
> > >     ECN MUST use the method described in [RFC6040] for ECN marking
> > >     propagation.
> > > With:
> > >     Tunnel end points need to use the method described in [RFC6040]
> > > for ECN marking
> > >     propagation.
> > > Rationale:
> > >     i) There is no such thing as a tunnel end point that does not
> > > support ECN - it has to put something in the ECN field, and it would
> > > not be appropriate to put anything in there other than what RFC6040 s=
ays.
> > >    ii) Generally it is not a good idea to fill one draft with
> > > normative statements that repeat normative statements made in other
> > > drafts. Otherwise updating an RFC gets very difficult - we have to
> > > update all the other RFCs that gratuitously repeat what it says.
> > >
> > > 3) Nit in section 3.1.
> > >     Section 5 of RFC6936 [RFC6936] specifies the additional requireme=
nts
> > >     that implementation of UDP zero-checksum over IPv6 MUST compliant
> > >     with. To compliant with it, the following additional requirements
> > >     apply
> > > s/compliant/comply/ (twice)
> > >
> > > There are other nits, but they can be dealt with later.
> > >
> > >
> > > Cheers
> > >
> > >
> > > Bob
> > >
> > >
> > >
> > >
> > > ________________________________________________________________
> > > Bob Briscoe,                                                  BT
>=20
> ________________________________________________________________
> Bob Briscoe,                                                  BT


From nobody Wed Jan 28 05:08:07 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1FDF1A701A for <tsvwg@ietfa.amsl.com>; Wed, 28 Jan 2015 05:08:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.022
X-Spam-Level: 
X-Spam-Status: No, score=0.022 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 sDEv8fbnhpc8 for <tsvwg@ietfa.amsl.com>; Wed, 28 Jan 2015 05:07:53 -0800 (PST)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B15011A00ED for <tsvwg@ietf.org>; Wed, 28 Jan 2015 05:07:50 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id n3so11695187wiv.3 for <tsvwg@ietf.org>; Wed, 28 Jan 2015 05:07:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to :content-type; bh=cipUk8REIhS6VsZy2IoXDsY4jBhDDa5hGfgy/JH2cNc=; b=NS6DijGJqqdkYpxmK93TSjDR7O9toBdPR+ewOqOKpE2Qg9AIlUJU42nPU6A0eCKHAF H6sCQvyreX8ViIodOt6SarDbMLfAzc4qaMDKeZMj6yU1uQ2PJZNPOYZbnDIcH3f52aky oG93p7TvmnrjQg6MCDXaCzbhyMDk6+qvjA8sU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=cipUk8REIhS6VsZy2IoXDsY4jBhDDa5hGfgy/JH2cNc=; b=hEDy9PWBZTyFn3Ed1bmBeGucQQkK+il89+3oszUxDYQr3+WRajsHHbVkYXp1I4TC1b Z/gKtC/YfRDzekaS6MJixuay/M/rCllon0rMZRyiE++uPVA+xGYHypsWlLlul9t6splr 3UoxUDrbRyof8EgdnXW/tOeM8SAzEZrxwjWS6mg22xsRUPdul47BOqYjm51xqn4+pLvl kAOwPpnDgt5e7AczXyFp89HWpabWF71CHf0Bpbbtq4hUNHxPnyBceWqrmF0Orudn093t jlgddRl4xPTw1PvqLR37vBawNQwA7DAx8ygHvhIR3RqV+P5tnzKg4yVQCXB3cDrFR76z 8uaQ==
X-Gm-Message-State: ALoCoQltIvMY2j0WnuBy2UqI6VF1qe57bW9dY75C6HztAOsVIBES1nkPnxSUEJcROURrB+VsvIlLndUnUT9fx+t4tQWOAbVPKodRgu5Fb/5GYsDyfXV2XXM=
X-Received: by 10.180.103.201 with SMTP id fy9mr7031473wib.31.1422450469392; Wed, 28 Jan 2015 05:07:49 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdA6+2g7uTb/cxzBSxOIbzgzpU2HNg==
Date: Wed, 28 Jan 2015 14:07:48 +0100
Message-ID: <12c48c203fe56af6569f4056e6add852@mail.gmail.com>
To: tsvwg@ietf.org, Randall Stewart <rrs@netflix.com>, Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/alternative; boundary=14dae9cc90b8f07689050db60e56
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/w8WD969n6IPQgBUmx-Z11pGMpbw>
Subject: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 13:08:01 -0000

--14dae9cc90b8f07689050db60e56
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,



We have stumbled into an issue with a MUST in RFC4960 text on INIT
Collision handling.

We hope that the wg could help resolve the issue.



The issue is the following underlined text of RFC4960 (from RC4460).



Section 5.2.1 of RFC4960:





   Upon receipt of an INIT in the COOKIE-WAIT state, an endpoint MUST

   respond with an INIT ACK using the same parameters it sent in its

   original INIT chunk (including its Initiation Tag, unchanged).

   When responding, the endpoint MUST send the INIT ACK back to the same

   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   address that the original INIT (sent by this endpoint) was sent to.

   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^



   Upon receipt of an INIT in the COOKIE-ECHOED state, an endpoint MUST

   respond with an INIT ACK using the same parameters it sent in its

   original INIT chunk (including its Initiation Tag, unchanged),

   provided that no NEW address has been added to the forming

   association.  If the INIT message indicates that a new address has

   been added to the association, then the entire INIT MUST be

   discarded, and NO changes should be made to the existing association.

   An ABORT SHOULD be sent in response that MAY include the error

   'Restart of an association with new addresses'.  The error SHOULD

   list the addresses that were added to the restarting association.







The issue we have can be illustrated by the following example:



        A connect() towards peer address X and Y has been made at local EP.
INIT is sent to Peer address X.



       Peer EP in fact have local addresses Y and Z and an incoming
collision INIT is sent from Y including Y and Z as address parameters.



       According to the above MUST the INIT ACK should be returned to X
which will be completely in vain (of course).





Note:



It is understood that the in order to prevent association high jacking then
it is imperative that the INIT ACK be not returned to a peer address

not  specified on the local EP side as a remote address for the association
(in cookie_wait). Thus the INIT ACK cannot simply be reflected to sender
address.



Question:



Is this the intention of the RFC4960 MUST to prescribe for this exact
operation.



Possible answers:



=C2=B7         Yes this is the intention, hopefully the association will be
established when local EP re-send INIT to alternative address Y

=C2=B7         No,  the =E2=80=9CMUST=E2=80=9D is wrong and should have rea=
d =E2=80=93 =E2=80=9CSHOULD return to
a destination address provided in  the INIT which also is specified locally
as a peer address for the association (in cookie_wait)=E2=80=9D



Thanks !



BR, Karen

--14dae9cc90b8f07689050db60e56
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dus-ascii"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1971130912;
	mso-list-type:hybrid;
	mso-list-template-ids:151650630 -912466146 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style></head><body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div =
class=3D"WordSection1"><p class=3D"MsoNormal">Hi,</p><p class=3D"MsoNormal"=
>=C2=A0</p><p class=3D"MsoNormal">We have stumbled into an issue with a MUS=
T in RFC4960 text on INIT Collision handling.</p><p class=3D"MsoNormal">We =
hope that the wg could help resolve the issue.</p><p class=3D"MsoNormal">=
=C2=A0</p><p class=3D"MsoNormal">The issue is the following underlined text=
 of RFC4960 (from RC4460). </p><p class=3D"MsoNormal">=C2=A0</p><p class=3D=
"MsoNormal">Section 5.2.1 of RFC4960:</p><p class=3D"MsoNormal"><span style=
=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=
=A0=C2=A0 </span></p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt=
;font-family:&quot;Courier New&quot;;color:black">=C2=A0</span></p><p class=
=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Courier Ne=
w&quot;;color:black">=C2=A0=C2=A0 Upon receipt of an INIT in the COOKIE-WAI=
T state, an endpoint MUST</span></p><p class=3D"MsoNormal"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=A0=C2=
=A0 respond with an INIT ACK using the same parameters it sent in its</span=
></p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;;color:black">=C2=A0=C2=A0 original INIT chunk (includi=
ng its Initiation Tag, unchanged). <br><br></span></p><p class=3D"MsoNormal=
"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color=
:black">=C2=A0=C2=A0=C2=A0When responding, the endpoint MUST send the INIT =
ACK back to the same</span></p><p class=3D"MsoNormal"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 ^^=
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^</span>=
</p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quo=
t;Courier New&quot;;color:black">=C2=A0=C2=A0 address that the original INI=
T (sent by this endpoint) was sent to.</span></p><p class=3D"MsoNormal"><sp=
an style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:blac=
k">=C2=A0=C2=A0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^^^^ </span></p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt=
;font-family:&quot;Courier New&quot;;color:black">=C2=A0</span></p><p class=
=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Courier Ne=
w&quot;;color:black">=C2=A0=C2=A0 Upon receipt of an INIT in the COOKIE-ECH=
OED state, an endpoint MUST</span></p><p class=3D"MsoNormal"><span style=3D=
"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=A0=
=C2=A0 respond with an INIT ACK using the same parameters it sent in its</s=
pan></p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 original INIT chunk (incl=
uding its Initiation Tag, unchanged),</span></p><p class=3D"MsoNormal"><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black=
">=C2=A0=C2=A0 provided that no NEW address has been added to the forming</=
span></p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family=
:&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 association.=C2=A0 If th=
e INIT message indicates that a new address has</span></p><p class=3D"MsoNo=
rmal"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;c=
olor:black">=C2=A0=C2=A0 been added to the association, then the entire INI=
T MUST be</span></p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;=
font-family:&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 discarded, an=
d NO changes should be made to the existing association.</span></p><p class=
=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Courier Ne=
w&quot;;color:black">=C2=A0=C2=A0 An ABORT SHOULD be sent in response that =
MAY include the error</span></p><p class=3D"MsoNormal"><span style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 &=
#39;Restart of an association with new addresses&#39;.=C2=A0 The error SHOU=
LD</span></p><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-fa=
mily:&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 list the addresses t=
hat were added to the restarting association.</span></p><p class=3D"MsoNorm=
al">=C2=A0</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">=C2=
=A0</p><p class=3D"MsoNormal">The issue we have can be illustrated by the f=
ollowing example:</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal=
">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A connect() towards peer addre=
ss X and Y has been made at local EP. INIT is sent to Peer address X.</p><p=
 class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 Peer EP in fact have local addresses Y and Z and an incomin=
g collision INIT is sent from Y including Y and Z as address parameters.</p=
><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 According to the above MUST the INIT ACK should be retur=
ned to X which will be completely in vain (of course).</p><p class=3D"MsoNo=
rmal">=C2=A0</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Not=
e:</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">It is underst=
ood that the in order to prevent association high jacking then it is impera=
tive that the INIT ACK be not returned to a peer address </p><p class=3D"Ms=
oNormal">not =C2=A0specified on the local EP side as a remote address for t=
he association (in cookie_wait). Thus the INIT ACK cannot simply be reflect=
ed to sender address.</p><p class=3D"MsoNormal">=C2=A0=C2=A0=C2=A0 </p><p c=
lass=3D"MsoNormal">Question:</p><p class=3D"MsoNormal">=C2=A0</p><p class=
=3D"MsoNormal">Is this the intention of the RFC4960 MUST to prescribe for t=
his exact operation.</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNor=
mal">Possible answers:</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoL=
istParagraph" style><span style=3D"font-family:Symbol"><span style>=C2=B7<s=
pan style=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span></span></span>Yes this is the intention,=
 hopefully the association will be established when local EP re-send INIT t=
o alternative address Y</p><p class=3D"MsoListParagraph" style><span style=
=3D"font-family:Symbol"><span style>=C2=B7<span style=3D"font:7.0pt &quot;T=
imes New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </sp=
an></span></span>No, =C2=A0the =E2=80=9CMUST=E2=80=9D is wrong and should h=
ave read =E2=80=93 =E2=80=9CSHOULD return to a destination address provided=
 in =C2=A0the INIT which also is specified locally as a peer address for th=
e association (in cookie_wait)=E2=80=9D</p><p class=3D"MsoNormal">=C2=A0</p=
><p class=3D"MsoNormal">Thanks !</p><p class=3D"MsoNormal">=C2=A0</p><p cla=
ss=3D"MsoNormal">BR, Karen</p></div></body></html>

--14dae9cc90b8f07689050db60e56--


From nobody Wed Jan 28 13:06:15 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7A8E1A1A92 for <tsvwg@ietfa.amsl.com>; Wed, 28 Jan 2015 13:06:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 RwaAivNV_CCk for <tsvwg@ietfa.amsl.com>; Wed, 28 Jan 2015 13:06:09 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA9BD1A005C for <tsvwg@ietf.org>; Wed, 28 Jan 2015 13:06:08 -0800 (PST)
Received: from [192.168.1.200] (p508F0277.dip0.t-ipconnect.de [80.143.2.119]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id AC46C1C0B3EE3; Wed, 28 Jan 2015 22:06:05 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <12c48c203fe56af6569f4056e6add852@mail.gmail.com>
Date: Wed, 28 Jan 2015 22:06:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B618562-2865-4A11-A654-1E38F83C298D@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/0UtNIczyffhlsjcKRy-ezpXbWfs>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 21:06:11 -0000

> On 28 Jan 2015, at 14:07, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:
>=20
> Hi,
> =20
> We have stumbled into an issue with a MUST in RFC4960 text on INIT =
Collision handling.
> We hope that the wg could help resolve the issue.
> =20
> The issue is the following underlined text of RFC4960 (from RC4460).=20=

> =20
> Section 5.2.1 of RFC4960:
>   =20
> =20
>    Upon receipt of an INIT in the COOKIE-WAIT state, an endpoint MUST
>    respond with an INIT ACK using the same parameters it sent in its
>    original INIT chunk (including its Initiation Tag, unchanged).=20
>=20
>    When responding, the endpoint MUST send the INIT ACK back to the =
same
>    =
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    address that the original INIT (sent by this endpoint) was sent to.
>    =
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=20
> =20
>    Upon receipt of an INIT in the COOKIE-ECHOED state, an endpoint =
MUST
>    respond with an INIT ACK using the same parameters it sent in its
>    original INIT chunk (including its Initiation Tag, unchanged),
>    provided that no NEW address has been added to the forming
>    association.  If the INIT message indicates that a new address has
>    been added to the association, then the entire INIT MUST be
>    discarded, and NO changes should be made to the existing =
association.
>    An ABORT SHOULD be sent in response that MAY include the error
>    'Restart of an association with new addresses'.  The error SHOULD
>    list the addresses that were added to the restarting association.
> =20
> =20
> =20
> The issue we have can be illustrated by the following example:
> =20
>         A connect() towards peer address X and Y has been made at =
local EP. INIT is sent to Peer address X.
Do you mean sctp_connectx()? So the peer EP owns X and Y. The INIT is =
sent to X.
> =20
>        Peer EP in fact have local addresses Y and Z and an incoming =
collision INIT is sent from Y including Y and Z as address parameters.
So the peer EP does not own X and Y, but Y and Z? So the INIT sent above =
would be dropped...
I'm not sure if I understand your example...

Best regards
Michael
> =20
>        According to the above MUST the INIT ACK should be returned to =
X which will be completely in vain (of course).
> =20
> =20
> Note:
> =20
> It is understood that the in order to prevent association high jacking =
then it is imperative that the INIT ACK be not returned to a peer =
address=20
> not  specified on the local EP side as a remote address for the =
association (in cookie_wait). Thus the INIT ACK cannot simply be =
reflected to sender address.
>    =20
> Question:
> =20
> Is this the intention of the RFC4960 MUST to prescribe for this exact =
operation.
> =20
> Possible answers:
> =20
> =C2=B7         Yes this is the intention, hopefully the association =
will be established when local EP re-send INIT to alternative address Y
> =C2=B7         No,  the =E2=80=9CMUST=E2=80=9D is wrong and should =
have read =E2=80=93 =E2=80=9CSHOULD return to a destination address =
provided in  the INIT which also is specified locally as a peer address =
for the association (in cookie_wait)=E2=80=9D
> =20
> Thanks !
> =20
> BR, Karen


From nobody Wed Jan 28 13:38:35 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B561A038A for <tsvwg@ietfa.amsl.com>; Wed, 28 Jan 2015 13:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 l_-Ys0h2_GoH for <tsvwg@ietfa.amsl.com>; Wed, 28 Jan 2015 13:38:31 -0800 (PST)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59EFC1A1AB8 for <tsvwg@ietf.org>; Wed, 28 Jan 2015 13:38:25 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id n3so15859378wiv.3 for <tsvwg@ietf.org>; Wed, 28 Jan 2015 13:38:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=ZyRzYPvfJzzTlttSC/HO19cCtEw9O+EAJTotcxS9Zog=; b=L1IOUbJC9JTBjrpFsmxbdQ941g9ojPHxRceH9xv9B+buRO/3E7FU8VQ+JAsjWy0poQ AvNDHfEQcBfgwUrOIGGib6N082M8myYHp1FtWegVZW8bEqkXtlZ6m9U5dPSyuvkqGoEm qCPLyw4I5u1nMhdYK61oSkkDwHdt5bD5ENWHA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=ZyRzYPvfJzzTlttSC/HO19cCtEw9O+EAJTotcxS9Zog=; b=PI1DX7BJBEaKn5DKTBbE2mQ1wYVoXNjHuE3GA+/73w7sm563ubi7BRgJzqpQ58lUMU lzpU1wvBWoFPFLHocrbGpxs9kSMgvvoGDQabG4b2/ekZ7UcU1Na8xarSuUbs37YTxXAB jLlA6QTNwclMJL3CjtZBLNWKLxKf1xJLcv7RlYLwOop/csno83k/EoS1eqQGPHqWC7yM oDyxOAa0hmEQEk1LE4nXsF8S0+o3QRm5Pivdh0r2EcxLwQJ9VUfP7JmjbZC5ikfZbDA+ fWW0H1eJn3VD0ZAnkWuGBeEpCzcEK1S/gXP7bAbGL3XG8XZqaDTE7nXgptwyevfkk2xh yT3Q==
X-Gm-Message-State: ALoCoQk9b8gQxYGRWnheBicYejFDrt7ovy+xu59uOkVbFjQmfSHlkt8pIZMdJ30tqt1JqjYgbse82UXG/uBqJR7ibjvqOTUrjCiZS/GRCatY56ZAMles8p4=
X-Received: by 10.180.211.2 with SMTP id my2mr11084758wic.3.1422481104112; Wed, 28 Jan 2015 13:38:24 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <5B618562-2865-4A11-A654-1E38F83C298D@lurchi.franken.de>
In-Reply-To: <5B618562-2865-4A11-A654-1E38F83C298D@lurchi.franken.de>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/6VYolOppVTY59nckiuBBdiyn8gL9jbsumt6/yiA=
Date: Wed, 28 Jan 2015 22:38:22 +0100
Message-ID: <0020181f2b27ff67cdd1411a1c0ad8c5@mail.gmail.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/lInsxGdjCgASnjMOy9RYcuGVx_k>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 21:38:34 -0000

HI Michael,

Yes the outgoing INIT would be dropped and so apparently would now also the
INIT_ACK as it following RFC4960 MUST would be
sent also to X.

However were the INIT_ACK instead send to Y, an association would come up
with peer addresses Y and Z.

The same will happen when the local side eventually decides to send the INI=
T
to Y instead (after timeout of original INIT).

The policy of RFC4960 to MUST send the INIT_ACK to X does not seem like a
very good thing to do.

This is the point of the example.

NB:
I understand that we need a MUST to return the INIT_ACK to an address that
is common to what has been specified locally as peer address candidates
(here X and Y) and
to what the peer indicates in the INIT (here Y and Z).

Indeed if a malicious peer owning W, sends in an INIT, from source W,
claiming to own also Z, then the INIT_ACK should not be returned to W as
this could result in association high-jacking by C.  And RFC4960 Path
Verification would do no good here to prevent this for the following two
reasons:
* Y is auto Path Verified as it has been provided from ULP (according to
RFC4960).
(Besides that peer owning address Y would not send  ABORT to HBs coming in
to Y if it continues to try to sends INITs (each INIT of course is answered
with ABORT))

But why we need a MUST to have the INIT_ACK be sent to same address as
original INIT (sent to X) is not clear to me. And this is a _MUST_ (added b=
y
RFC4460).

Thanks !

BR, Karen

>-----Original Message-----
>From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>Sent: Wednesday, January 28, 2015 10:06 PM
>To: Karen Elisabeth Egede Nielsen
>Cc: tsvwg@ietf.org; Randall Stewart
>Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
>
>
>> On 28 Jan 2015, at 14:07, Karen Elisabeth Egede Nielsen
><karen.nielsen@tieto.com> wrote:
>>
>> Hi,
>>
>> We have stumbled into an issue with a MUST in RFC4960 text on INIT
>Collision handling.
>> We hope that the wg could help resolve the issue.
>>
>> The issue is the following underlined text of RFC4960 (from RC4460).
>>
>> Section 5.2.1 of RFC4960:
>>
>>
>>    Upon receipt of an INIT in the COOKIE-WAIT state, an endpoint MUST
>>    respond with an INIT ACK using the same parameters it sent in its
>>    original INIT chunk (including its Initiation Tag, unchanged).
>>
>>    When responding, the endpoint MUST send the INIT ACK back to the same
>>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>^^^^^^^^^^^
>>    address that the original INIT (sent by this endpoint) was sent to.
>>
>>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>^^^^^^^^^
>>
>>    Upon receipt of an INIT in the COOKIE-ECHOED state, an endpoint MUST
>>    respond with an INIT ACK using the same parameters it sent in its
>>    original INIT chunk (including its Initiation Tag, unchanged),
>>    provided that no NEW address has been added to the forming
>>    association.  If the INIT message indicates that a new address has
>>    been added to the association, then the entire INIT MUST be
>>    discarded, and NO changes should be made to the existing association.
>>    An ABORT SHOULD be sent in response that MAY include the error
>>    'Restart of an association with new addresses'.  The error SHOULD
>>    list the addresses that were added to the restarting association.
>>
>>
>>
>> The issue we have can be illustrated by the following example:
>>
>>         A connect() towards peer address X and Y has been made at local
>> EP.
>INIT is sent to Peer address X.
>Do you mean sctp_connectx()? So the peer EP owns X and Y. The INIT is sent
>to X.
>>
>>        Peer EP in fact have local addresses Y and Z and an incoming
>> collision INIT
>is sent from Y including Y and Z as address parameters.
>So the peer EP does not own X and Y, but Y and Z? So the INIT sent above
>would be dropped...
>I'm not sure if I understand your example...
>
>Best regards
>Michael
>>
>>        According to the above MUST the INIT ACK should be returned to X
>which will be completely in vain (of course).
>>
>>
>> Note:
>>
>> It is understood that the in order to prevent association high jacking
>> then it is imperative that the INIT ACK be not returned to a peer addres=
s
>> not
>specified on the local EP side as a remote address for the association (in
>cookie_wait). Thus the INIT ACK cannot simply be reflected to sender
>address.
>>
>> Question:
>>
>> Is this the intention of the RFC4960 MUST to prescribe for this exact
>operation.
>>
>> Possible answers:
>>
>> =C2=B7         Yes this is the intention, hopefully the association will=
 be
>> established
>when local EP re-send INIT to alternative address Y
>> =C2=B7         No,  the =E2=80=9CMUST=E2=80=9D is wrong and should have =
read =E2=80=93 =E2=80=9CSHOULD return
>> to a
>destination address provided in  the INIT which also is specified locally
>as a
>peer address for the association (in cookie_wait)=E2=80=9D
>>
>> Thanks !
>>
>> BR, Karen


From nobody Thu Jan 29 03:49:09 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F94B1A0211 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 03:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 p4byBIJfN-Ze for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 03:49:04 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519541A0035 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 03:49:04 -0800 (PST)
Received: from [192.168.1.200] (p508F0344.dip0.t-ipconnect.de [80.143.3.68]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id BCE771C0E9733; Thu, 29 Jan 2015 12:49:01 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <0020181f2b27ff67cdd1411a1c0ad8c5@mail.gmail.com>
Date: Thu, 29 Jan 2015 12:49:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E15D9866-6B7C-429B-BBAA-0E61F9898AA8@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <5B618562-2865-4A11-A654-1E38F83C298D@lurchi.franken.de> <0020181f2b27ff67cdd1411a1c0ad8c5@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/13WJKjwt73TtsLJ6rhob3cH-ems>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 11:49:07 -0000

> On 28 Jan 2015, at 22:38, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:
>=20
> HI Michael,
>=20
> Yes the outgoing INIT would be dropped and so apparently would now =
also the
> INIT_ACK as it following RFC4960 MUST would be
> sent also to X.
>=20
> However were the INIT_ACK instead send to Y, an association would come =
up
> with peer addresses Y and Z.
>=20
> The same will happen when the local side eventually decides to send =
the INIT
> to Y instead (after timeout of original INIT).
>=20
> The policy of RFC4960 to MUST send the INIT_ACK to X does not seem =
like a
> very good thing to do.
>=20
> This is the point of the example.
OK. Understood. I agree with your analysis. I see three conditions =
involved:
(a) The INIT-ACK MUST only be sent to an address configured by the upper =
layer
(b) The INIT-ACK MUST only be sent to an address reported in the =
incoming INIT
(c) The INIT-ACK SHOULD be sent to the source address of the received =
INIT.

I think the RFC actually needs to require (a) instead of limiting it to =
the
one address where the original INIT was sent to. (b) restricts the =
candidates
from (a). And I always prefer (c) in case of response packets.
>=20
> NB:
> I understand that we need a MUST to return the INIT_ACK to an address =
that
> is common to what has been specified locally as peer address =
candidates
> (here X and Y) and
> to what the peer indicates in the INIT (here Y and Z).
Correct.
>=20
> Indeed if a malicious peer owning W, sends in an INIT, from source W,
> claiming to own also Z, then the INIT_ACK should not be returned to W =
as
> this could result in association high-jacking by C.  And RFC4960 Path
> Verification would do no good here to prevent this for the following =
two
> reasons:
> * Y is auto Path Verified as it has been provided from ULP (according =
to
> RFC4960).
> (Besides that peer owning address Y would not send  ABORT to HBs =
coming in
> to Y if it continues to try to sends INITs (each INIT of course is =
answered
> with ABORT))
>=20
> But why we need a MUST to have the INIT_ACK be sent to same address as
> original INIT (sent to X) is not clear to me. And this is a _MUST_ =
(added by
> RFC4460).
The rule we are discussing was introduced in
https://tools.ietf.org/html/rfc4460#section-2.6

The path verification and the statement that the
upper layer can provide multiple peer addresses to the
sender of the INIT chunk is described in
https://tools.ietf.org/html/rfc4460#section-2.36
which is later introduced later.

The associate primitive in described in B) of
https://tools.ietf.org/html/rfc4960#section-10.1
also deals only with the possibility to provide a single
remote IP address (like the connect() call in the socket
API).

So I guess that the idea of providing multiple addresses
was introduce after
https://tools.ietf.org/html/rfc4460#section-2.6
was written. The rule is correct, if you only have a single
remote address. So at the writing, it was correct.

Later, when the idea of providing multiple peer addresses was
introduced (and sctp_connectx() was defined), neither the definition
of the Associate() primitive was updated nor the rule we are
discussing right now... At least this is what I suspect...

Best regards
Michael
>=20
> Thanks !
>=20
> BR, Karen
>=20
>> -----Original Message-----
>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>> Sent: Wednesday, January 28, 2015 10:06 PM
>> To: Karen Elisabeth Egede Nielsen
>> Cc: tsvwg@ietf.org; Randall Stewart
>> Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 =
MUST
>>=20
>>=20
>>> On 28 Jan 2015, at 14:07, Karen Elisabeth Egede Nielsen
>> <karen.nielsen@tieto.com> wrote:
>>>=20
>>> Hi,
>>>=20
>>> We have stumbled into an issue with a MUST in RFC4960 text on INIT
>> Collision handling.
>>> We hope that the wg could help resolve the issue.
>>>=20
>>> The issue is the following underlined text of RFC4960 (from RC4460).
>>>=20
>>> Section 5.2.1 of RFC4960:
>>>=20
>>>=20
>>>   Upon receipt of an INIT in the COOKIE-WAIT state, an endpoint MUST
>>>   respond with an INIT ACK using the same parameters it sent in its
>>>   original INIT chunk (including its Initiation Tag, unchanged).
>>>=20
>>>   When responding, the endpoint MUST send the INIT ACK back to the =
same
>>>=20
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> ^^^^^^^^^^^
>>>   address that the original INIT (sent by this endpoint) was sent =
to.
>>>=20
>>>=20
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> ^^^^^^^^^
>>>=20
>>>   Upon receipt of an INIT in the COOKIE-ECHOED state, an endpoint =
MUST
>>>   respond with an INIT ACK using the same parameters it sent in its
>>>   original INIT chunk (including its Initiation Tag, unchanged),
>>>   provided that no NEW address has been added to the forming
>>>   association.  If the INIT message indicates that a new address has
>>>   been added to the association, then the entire INIT MUST be
>>>   discarded, and NO changes should be made to the existing =
association.
>>>   An ABORT SHOULD be sent in response that MAY include the error
>>>   'Restart of an association with new addresses'.  The error SHOULD
>>>   list the addresses that were added to the restarting association.
>>>=20
>>>=20
>>>=20
>>> The issue we have can be illustrated by the following example:
>>>=20
>>>        A connect() towards peer address X and Y has been made at =
local
>>> EP.
>> INIT is sent to Peer address X.
>> Do you mean sctp_connectx()? So the peer EP owns X and Y. The INIT is =
sent
>> to X.
>>>=20
>>>       Peer EP in fact have local addresses Y and Z and an incoming
>>> collision INIT
>> is sent from Y including Y and Z as address parameters.
>> So the peer EP does not own X and Y, but Y and Z? So the INIT sent =
above
>> would be dropped...
>> I'm not sure if I understand your example...
>>=20
>> Best regards
>> Michael
>>>=20
>>>       According to the above MUST the INIT ACK should be returned to =
X
>> which will be completely in vain (of course).
>>>=20
>>>=20
>>> Note:
>>>=20
>>> It is understood that the in order to prevent association high =
jacking
>>> then it is imperative that the INIT ACK be not returned to a peer =
address
>>> not
>> specified on the local EP side as a remote address for the =
association (in
>> cookie_wait). Thus the INIT ACK cannot simply be reflected to sender
>> address.
>>>=20
>>> Question:
>>>=20
>>> Is this the intention of the RFC4960 MUST to prescribe for this =
exact
>> operation.
>>>=20
>>> Possible answers:
>>>=20
>>> =C2=B7         Yes this is the intention, hopefully the association =
will be
>>> established
>> when local EP re-send INIT to alternative address Y
>>> =C2=B7         No,  the =E2=80=9CMUST=E2=80=9D is wrong and should =
have read =E2=80=93 =E2=80=9CSHOULD return
>>> to a
>> destination address provided in  the INIT which also is specified =
locally
>> as a
>> peer address for the association (in cookie_wait)=E2=80=9D
>>>=20
>>> Thanks !
>>>=20
>>> BR, Karen
>=20


From nobody Thu Jan 29 05:12:16 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC721A037B for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 05:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 7HpI7-1zlaL9 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 05:12:09 -0800 (PST)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86C8D1A036C for <tsvwg@ietf.org>; Thu, 29 Jan 2015 05:12:07 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id l15so24355603wiw.0 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 05:12:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=YbsAPG9np52p+ehFAWVEt8aS7XHw4GSsaCD+TseiOiA=; b=AlVB/QPcEo5yNJ9xprU/+WCiu2ZeLmEK139sRp0Sxal9b1Us0VB0b638vEqMHCOmHc yD/HZWBj8Cq/RHxwGWuKI/Rx+Lj618dLq0RctpMsALMhMpZRRX5wp/5dyObfshDzSOoZ O069JPnDbay/GuOgaYHK8pNhii1YJe5xFVvbk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=YbsAPG9np52p+ehFAWVEt8aS7XHw4GSsaCD+TseiOiA=; b=g3ERHjlO3ZIye+84q5DxPe10xC6kE0h+fOSif+ysamtMjT3Smzs9f3DokTBaSxu/z/ 8jDqd8aK9b0WGE+A93CyhKvo0BXzTjx400sAnFXVz+xcdY+sqVQGw+3Z66+5Sr9lzjoF ySnDOpZqwsxipxc8RR6Qi9KDvctx67lQYBf+TLFhuT53GYNChNdgpOPWkiOAPM3L+jAp EpHmLl38GSIyzMIfwDQP04IHrff5rZBb/0JfbxGJnChpCxNNb6fyIX/JNZSx42xtQFGi 0WctqfGk+6NGUwkd6xHLyjCDg+tiRyNCfbJvjnmWZyup9nCNSwS+lFKnKd1dk5msPfLr ndXg==
X-Gm-Message-State: ALoCoQnuxRG6QlSdK3G6AMx2uXBw9T1377JqvqUCfr63bX/Bu5y8sTszl9I2+bFhqlFmv+a+5FjppCCsVWZ8LtuMqfTCZOfTcLCln6noOd99EXPCQhXTPAk=
X-Received: by 10.194.89.3 with SMTP id bk3mr1037028wjb.92.1422537125720; Thu, 29 Jan 2015 05:12:05 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <5B618562-2865-4A11-A654-1E38F83C298D@lurchi.franken.de> <0020181f2b27ff67cdd1411a1c0ad8c5@mail.gmail.com> <E15D9866-6B7C-429B-BBAA-0E61F9898AA8@lurchi.franken.de>
In-Reply-To: <E15D9866-6B7C-429B-BBAA-0E61F9898AA8@lurchi.franken.de>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/6VYolOppVTY59nckiuBBdiyn8gL9jbsuAWnBeBIBsBYbhJrG51EQ
Date: Thu, 29 Jan 2015 14:12:04 +0100
Message-ID: <5797dbe0c3fbf322d15b2eb9e8aec534@mail.gmail.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/oqQ14Qbg-J-kpIxgboLO6lxDTRk>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 13:12:12 -0000

HI Michael,

Thanks a lot!

I am in perfect agreement with the proposed resolution:

(a) The INIT-ACK MUST only be sent to an address configured by the upper
layer
(b) The INIT-ACK MUST only be sent to an address reported in the incoming
INIT
(c) The INIT-ACK SHOULD be sent to the source address of the received INIT.

And this is how we would like to alter our MH SCTP to behave in this
situation.

Shall we propose for an Errata ?

BR, Karen

>-----Original Message-----
>From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>Sent: Thursday, January 29, 2015 12:49 PM
>To: Karen Elisabeth Egede Nielsen
>Cc: tsvwg@ietf.org; Randall Stewart
>Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
>
>> On 28 Jan 2015, at 22:38, Karen Elisabeth Egede Nielsen
><karen.nielsen@tieto.com> wrote:
>>
>> HI Michael,
>>
>> Yes the outgoing INIT would be dropped and so apparently would now
>> also the INIT_ACK as it following RFC4960 MUST would be sent also to
>> X.
>>
>> However were the INIT_ACK instead send to Y, an association would come
>> up with peer addresses Y and Z.
>>
>> The same will happen when the local side eventually decides to send
>> the INIT to Y instead (after timeout of original INIT).
>>
>> The policy of RFC4960 to MUST send the INIT_ACK to X does not seem
>> like a very good thing to do.
>>
>> This is the point of the example.
>OK. Understood. I agree with your analysis. I see three conditions
>involved:
>(a) The INIT-ACK MUST only be sent to an address configured by the upper
>layer
>(b) The INIT-ACK MUST only be sent to an address reported in the incoming
>INIT
>(c) The INIT-ACK SHOULD be sent to the source address of the received INIT=
.
>
>I think the RFC actually needs to require (a) instead of limiting it to th=
e
>one
>address where the original INIT was sent to. (b) restricts the candidates
>from
>(a). And I always prefer (c) in case of response packets.
>>
>> NB:
>> I understand that we need a MUST to return the INIT_ACK to an address
>> that is common to what has been specified locally as peer address
>> candidates (here X and Y) and to what the peer indicates in the INIT
>> (here Y and Z).
>Correct.
>>
>> Indeed if a malicious peer owning W, sends in an INIT, from source W,
>> claiming to own also Z, then the INIT_ACK should not be returned to W
>> as this could result in association high-jacking by C.  And RFC4960
>> Path Verification would do no good here to prevent this for the
>> following two
>> reasons:
>> * Y is auto Path Verified as it has been provided from ULP (according
>> to RFC4960).
>> (Besides that peer owning address Y would not send  ABORT to HBs
>> coming in to Y if it continues to try to sends INITs (each INIT of
>> course is answered with ABORT))
>>
>> But why we need a MUST to have the INIT_ACK be sent to same address as
>> original INIT (sent to X) is not clear to me. And this is a _MUST_
>> (added by RFC4460).
>The rule we are discussing was introduced in
>https://tools.ietf.org/html/rfc4460#section-2.6
>
>The path verification and the statement that the upper layer can provide
>multiple peer addresses to the sender of the INIT chunk is described in
>https://tools.ietf.org/html/rfc4460#section-2.36
>which is later introduced later.
>
>The associate primitive in described in B) of
>https://tools.ietf.org/html/rfc4960#section-10.1
>also deals only with the possibility to provide a single remote IP address
>(like
>the connect() call in the socket API).
>
>So I guess that the idea of providing multiple addresses was introduce
>after
>https://tools.ietf.org/html/rfc4460#section-2.6
>was written. The rule is correct, if you only have a single remote address=
.
>So at
>the writing, it was correct.
>
>Later, when the idea of providing multiple peer addresses was introduced
>(and sctp_connectx() was defined), neither the definition of the
>Associate()
>primitive was updated nor the rule we are discussing right now... At least
>this
>is what I suspect...
>
>Best regards
>Michael
>>
>> Thanks !
>>
>> BR, Karen
>>
>>> -----Original Message-----
>>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>>> Sent: Wednesday, January 28, 2015 10:06 PM
>>> To: Karen Elisabeth Egede Nielsen
>>> Cc: tsvwg@ietf.org; Randall Stewart
>>> Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960
>>> MUST
>>>
>>>
>>>> On 28 Jan 2015, at 14:07, Karen Elisabeth Egede Nielsen
>>> <karen.nielsen@tieto.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> We have stumbled into an issue with a MUST in RFC4960 text on INIT
>>> Collision handling.
>>>> We hope that the wg could help resolve the issue.
>>>>
>>>> The issue is the following underlined text of RFC4960 (from RC4460).
>>>>
>>>> Section 5.2.1 of RFC4960:
>>>>
>>>>
>>>>   Upon receipt of an INIT in the COOKIE-WAIT state, an endpoint MUST
>>>>   respond with an INIT ACK using the same parameters it sent in its
>>>>   original INIT chunk (including its Initiation Tag, unchanged).
>>>>
>>>>   When responding, the endpoint MUST send the INIT ACK back to the
>>>> same
>>>>
>>>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> ^^^^^^^^^^^
>>>>   address that the original INIT (sent by this endpoint) was sent to.
>>>>
>>>>
>>>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> ^^^^^^^^^
>>>>
>>>>   Upon receipt of an INIT in the COOKIE-ECHOED state, an endpoint MUST
>>>>   respond with an INIT ACK using the same parameters it sent in its
>>>>   original INIT chunk (including its Initiation Tag, unchanged),
>>>>   provided that no NEW address has been added to the forming
>>>>   association.  If the INIT message indicates that a new address has
>>>>   been added to the association, then the entire INIT MUST be
>>>>   discarded, and NO changes should be made to the existing association=
.
>>>>   An ABORT SHOULD be sent in response that MAY include the error
>>>>   'Restart of an association with new addresses'.  The error SHOULD
>>>>   list the addresses that were added to the restarting association.
>>>>
>>>>
>>>>
>>>> The issue we have can be illustrated by the following example:
>>>>
>>>>        A connect() towards peer address X and Y has been made at
>>>> local EP.
>>> INIT is sent to Peer address X.
>>> Do you mean sctp_connectx()? So the peer EP owns X and Y. The INIT is
>>> sent to X.
>>>>
>>>>       Peer EP in fact have local addresses Y and Z and an incoming
>>>> collision INIT
>>> is sent from Y including Y and Z as address parameters.
>>> So the peer EP does not own X and Y, but Y and Z? So the INIT sent
>>> above would be dropped...
>>> I'm not sure if I understand your example...
>>>
>>> Best regards
>>> Michael
>>>>
>>>>       According to the above MUST the INIT ACK should be returned to
>>>> X
>>> which will be completely in vain (of course).
>>>>
>>>>
>>>> Note:
>>>>
>>>> It is understood that the in order to prevent association high
>>>> jacking then it is imperative that the INIT ACK be not returned to a
>>>> peer address not
>>> specified on the local EP side as a remote address for the
>>> association (in cookie_wait). Thus the INIT ACK cannot simply be
>>> reflected to sender address.
>>>>
>>>> Question:
>>>>
>>>> Is this the intention of the RFC4960 MUST to prescribe for this
>>>> exact
>>> operation.
>>>>
>>>> Possible answers:
>>>>
>>>> =C2=B7         Yes this is the intention, hopefully the association wi=
ll be
>>>> established
>>> when local EP re-send INIT to alternative address Y
>>>> =C2=B7         No,  the =E2=80=9CMUST=E2=80=9D is wrong and should hav=
e read =E2=80=93 =E2=80=9CSHOULD
>>>> return
>>>> to a
>>> destination address provided in  the INIT which also is specified
>>> locally as a peer address for the association (in cookie_wait)=E2=80=9D
>>>>
>>>> Thanks !
>>>>
>>>> BR, Karen
>>


From nobody Thu Jan 29 05:14:03 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8B7F1A037E for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 05:13:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 0gruztH1tkSd for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 05:13:58 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A25F1A0154 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 05:13:57 -0800 (PST)
Received: from [192.168.1.200] (p508F0344.dip0.t-ipconnect.de [80.143.3.68]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id A437E1C104E6E; Thu, 29 Jan 2015 14:13:55 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5797dbe0c3fbf322d15b2eb9e8aec534@mail.gmail.com>
Date: Thu, 29 Jan 2015 14:13:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E635DE5-3A91-4807-87C6-E0E9D816C13C@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <5B618562-2865-4A11-A654-1E38F83C298D@lurchi.franken.de> <0020181f2b27ff67cdd1411a1c0ad8c5@mail.gmail.com> <E15D9866-6B7C-429B-BBAA-0E61F9898AA8@lurchi.franken.de> <5797dbe0c3fbf322d15b2eb9e8aec534@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/Irk2yax7JBPRZWYjtvYTb9B_uSU>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 13:13:59 -0000

> On 29 Jan 2015, at 14:12, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:
>=20
> HI Michael,
>=20
> Thanks a lot!
>=20
> I am in perfect agreement with the proposed resolution:
>=20
> (a) The INIT-ACK MUST only be sent to an address configured by the =
upper
> layer
> (b) The INIT-ACK MUST only be sent to an address reported in the =
incoming
> INIT
> (c) The INIT-ACK SHOULD be sent to the source address of the received =
INIT.
>=20
> And this is how we would like to alter our MH SCTP to behave in this
> situation.
>=20
> Shall we propose for an Errata ?
Makes sense to me...

Best regards
Michael
>=20
> BR, Karen
>=20
>> -----Original Message-----
>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>> Sent: Thursday, January 29, 2015 12:49 PM
>> To: Karen Elisabeth Egede Nielsen
>> Cc: tsvwg@ietf.org; Randall Stewart
>> Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 =
MUST
>>=20
>>> On 28 Jan 2015, at 22:38, Karen Elisabeth Egede Nielsen
>> <karen.nielsen@tieto.com> wrote:
>>>=20
>>> HI Michael,
>>>=20
>>> Yes the outgoing INIT would be dropped and so apparently would now
>>> also the INIT_ACK as it following RFC4960 MUST would be sent also to
>>> X.
>>>=20
>>> However were the INIT_ACK instead send to Y, an association would =
come
>>> up with peer addresses Y and Z.
>>>=20
>>> The same will happen when the local side eventually decides to send
>>> the INIT to Y instead (after timeout of original INIT).
>>>=20
>>> The policy of RFC4960 to MUST send the INIT_ACK to X does not seem
>>> like a very good thing to do.
>>>=20
>>> This is the point of the example.
>> OK. Understood. I agree with your analysis. I see three conditions
>> involved:
>> (a) The INIT-ACK MUST only be sent to an address configured by the =
upper
>> layer
>> (b) The INIT-ACK MUST only be sent to an address reported in the =
incoming
>> INIT
>> (c) The INIT-ACK SHOULD be sent to the source address of the received =
INIT.
>>=20
>> I think the RFC actually needs to require (a) instead of limiting it =
to the
>> one
>> address where the original INIT was sent to. (b) restricts the =
candidates
>> from
>> (a). And I always prefer (c) in case of response packets.
>>>=20
>>> NB:
>>> I understand that we need a MUST to return the INIT_ACK to an =
address
>>> that is common to what has been specified locally as peer address
>>> candidates (here X and Y) and to what the peer indicates in the INIT
>>> (here Y and Z).
>> Correct.
>>>=20
>>> Indeed if a malicious peer owning W, sends in an INIT, from source =
W,
>>> claiming to own also Z, then the INIT_ACK should not be returned to =
W
>>> as this could result in association high-jacking by C.  And RFC4960
>>> Path Verification would do no good here to prevent this for the
>>> following two
>>> reasons:
>>> * Y is auto Path Verified as it has been provided from ULP =
(according
>>> to RFC4960).
>>> (Besides that peer owning address Y would not send  ABORT to HBs
>>> coming in to Y if it continues to try to sends INITs (each INIT of
>>> course is answered with ABORT))
>>>=20
>>> But why we need a MUST to have the INIT_ACK be sent to same address =
as
>>> original INIT (sent to X) is not clear to me. And this is a _MUST_
>>> (added by RFC4460).
>> The rule we are discussing was introduced in
>> https://tools.ietf.org/html/rfc4460#section-2.6
>>=20
>> The path verification and the statement that the upper layer can =
provide
>> multiple peer addresses to the sender of the INIT chunk is described =
in
>> https://tools.ietf.org/html/rfc4460#section-2.36
>> which is later introduced later.
>>=20
>> The associate primitive in described in B) of
>> https://tools.ietf.org/html/rfc4960#section-10.1
>> also deals only with the possibility to provide a single remote IP =
address
>> (like
>> the connect() call in the socket API).
>>=20
>> So I guess that the idea of providing multiple addresses was =
introduce
>> after
>> https://tools.ietf.org/html/rfc4460#section-2.6
>> was written. The rule is correct, if you only have a single remote =
address.
>> So at
>> the writing, it was correct.
>>=20
>> Later, when the idea of providing multiple peer addresses was =
introduced
>> (and sctp_connectx() was defined), neither the definition of the
>> Associate()
>> primitive was updated nor the rule we are discussing right now... At =
least
>> this
>> is what I suspect...
>>=20
>> Best regards
>> Michael
>>>=20
>>> Thanks !
>>>=20
>>> BR, Karen
>>>=20
>>>> -----Original Message-----
>>>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>>>> Sent: Wednesday, January 28, 2015 10:06 PM
>>>> To: Karen Elisabeth Egede Nielsen
>>>> Cc: tsvwg@ietf.org; Randall Stewart
>>>> Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and =
RFC4960
>>>> MUST
>>>>=20
>>>>=20
>>>>> On 28 Jan 2015, at 14:07, Karen Elisabeth Egede Nielsen
>>>> <karen.nielsen@tieto.com> wrote:
>>>>>=20
>>>>> Hi,
>>>>>=20
>>>>> We have stumbled into an issue with a MUST in RFC4960 text on INIT
>>>> Collision handling.
>>>>> We hope that the wg could help resolve the issue.
>>>>>=20
>>>>> The issue is the following underlined text of RFC4960 (from =
RC4460).
>>>>>=20
>>>>> Section 5.2.1 of RFC4960:
>>>>>=20
>>>>>=20
>>>>>  Upon receipt of an INIT in the COOKIE-WAIT state, an endpoint =
MUST
>>>>>  respond with an INIT ACK using the same parameters it sent in its
>>>>>  original INIT chunk (including its Initiation Tag, unchanged).
>>>>>=20
>>>>>  When responding, the endpoint MUST send the INIT ACK back to the
>>>>> same
>>>>>=20
>>>>=20
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> ^^^^^^^^^^^
>>>>>  address that the original INIT (sent by this endpoint) was sent =
to.
>>>>>=20
>>>>>=20
>>>>=20
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> ^^^^^^^^^
>>>>>=20
>>>>>  Upon receipt of an INIT in the COOKIE-ECHOED state, an endpoint =
MUST
>>>>>  respond with an INIT ACK using the same parameters it sent in its
>>>>>  original INIT chunk (including its Initiation Tag, unchanged),
>>>>>  provided that no NEW address has been added to the forming
>>>>>  association.  If the INIT message indicates that a new address =
has
>>>>>  been added to the association, then the entire INIT MUST be
>>>>>  discarded, and NO changes should be made to the existing =
association.
>>>>>  An ABORT SHOULD be sent in response that MAY include the error
>>>>>  'Restart of an association with new addresses'.  The error SHOULD
>>>>>  list the addresses that were added to the restarting association.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> The issue we have can be illustrated by the following example:
>>>>>=20
>>>>>       A connect() towards peer address X and Y has been made at
>>>>> local EP.
>>>> INIT is sent to Peer address X.
>>>> Do you mean sctp_connectx()? So the peer EP owns X and Y. The INIT =
is
>>>> sent to X.
>>>>>=20
>>>>>      Peer EP in fact have local addresses Y and Z and an incoming
>>>>> collision INIT
>>>> is sent from Y including Y and Z as address parameters.
>>>> So the peer EP does not own X and Y, but Y and Z? So the INIT sent
>>>> above would be dropped...
>>>> I'm not sure if I understand your example...
>>>>=20
>>>> Best regards
>>>> Michael
>>>>>=20
>>>>>      According to the above MUST the INIT ACK should be returned =
to
>>>>> X
>>>> which will be completely in vain (of course).
>>>>>=20
>>>>>=20
>>>>> Note:
>>>>>=20
>>>>> It is understood that the in order to prevent association high
>>>>> jacking then it is imperative that the INIT ACK be not returned to =
a
>>>>> peer address not
>>>> specified on the local EP side as a remote address for the
>>>> association (in cookie_wait). Thus the INIT ACK cannot simply be
>>>> reflected to sender address.
>>>>>=20
>>>>> Question:
>>>>>=20
>>>>> Is this the intention of the RFC4960 MUST to prescribe for this
>>>>> exact
>>>> operation.
>>>>>=20
>>>>> Possible answers:
>>>>>=20
>>>>> =C2=B7         Yes this is the intention, hopefully the =
association will be
>>>>> established
>>>> when local EP re-send INIT to alternative address Y
>>>>> =C2=B7         No,  the =E2=80=9CMUST=E2=80=9D is wrong and should =
have read =E2=80=93 =E2=80=9CSHOULD
>>>>> return
>>>>> to a
>>>> destination address provided in  the INIT which also is specified
>>>> locally as a peer address for the association (in cookie_wait)=E2=80=9D=

>>>>>=20
>>>>> Thanks !
>>>>>=20
>>>>> BR, Karen
>>>=20
>=20


From nobody Thu Jan 29 06:03:31 2015
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8B61A06FD for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:03:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 k5xwjsG2kubl for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:03:27 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11DCB1A0072 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:03:26 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0TE3Dls030858; Thu, 29 Jan 2015 07:03:13 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0TE3Dkl024209; Thu, 29 Jan 2015 07:03:13 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id t0TE3CLE024208; Thu, 29 Jan 2015 07:03:12 -0700
Date: Thu, 29 Jan 2015 07:03:12 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20150129140312.GA23554@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, tsvwg@ietf.org, Randall Stewart <rrs@netflix.com>, Michael Tuexen <tuexen@fh-muenster.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12c48c203fe56af6569f4056e6add852@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/PdP5CVeO6oN93moJO8WhUzxiouQ>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 14:03:29 -0000

Karen,

Karen Elisabeth Egede Nielsen wrote:        (Wed, 28 Jan 2015 14:07:48)
>    The issue we have can be illustrated by the following example:
> 
>    A connect() towards peer address X and Y has been made at local
>    EP. INIT is sent to Peer address X.
> 
>    Peer EP in fact have local addresses Y and Z and an incoming
>    collision INIT is sent from Y including Y and Z as address
>    parameters.
> 
>    According to the above MUST the INIT ACK should be returned to
>    X which will be completely in vain (of course).


  INIT --------------------> X

  <------------------------- Y INIT (Y,Z)

  INIT ACK ----------------> X

  Why is this in vain?

  X is an address of the peer.  The state cookie contains (Y,Z).
  Why would the peer not process this INIT ACK and form the
  association?


--brian


-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Jan 29 06:08:40 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 799EC1A07BD for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:08:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 gYpFL0AH-D32 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:08:31 -0800 (PST)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F17E1A047A for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:08:31 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id r20so26816975wiv.0 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:08:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=SEwFl+YsCC+6RbB4xwfdCYLWcH7zFakV1Z745LOJgY4=; b=1xstwz8kqykregTyrHUpfYb4/xjm5MITT74RPMC8sdfIQnTi86G98NIGcN4I5AnI02 fdSGEoly+wyhRwOgatEXyGX+25r4qks794dFyCnZfW5OFbKhiM8qO+cbZ99LrbfsC7GO W5w4ER2qEV1q5ktlfxwFoYbLZ8W85K36Xlfik=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=SEwFl+YsCC+6RbB4xwfdCYLWcH7zFakV1Z745LOJgY4=; b=m+FG9mT8UtK81zcN3zFm2Z2UDpjbwgs9MwRgHWy2Xi4zRrprwpQsl4GMF5cK1/9Ftz fBsxqWt4HLQ9JlO7U7n1Nhc0ShoDwvz0sp4DKbozNp94br7EQFHYBWYte2kFg5SgElNE CytBUgJ/dMYn/iOyiYvl0HDf9oGtunVt541tM3Kar92O1SltzY+hYk3TiFTM4cEUWm3C SRDeYmfTH0tRcKIJAnT5nen/I9QOYvFFwgh2MWJyQVuugzNnpK0Dsf83rUeZs75ceMfX mhBU3uPRFT7aIMsEwC6qAqrynD5MrZ1DUeNMh33iTlLLNo+4m9ZyHAGXK8P/34A2OI7M xkAQ==
X-Gm-Message-State: ALoCoQlUVs+ywwL6p7YcaNLAT3N9U04kkPyy6jWb0ympEItmmbuI17uPX28fjXNN79vE4ZyKz4e6vJkcRYZj6EZZmf488B0drPrqmLNZcjwpg7KkHn5OSHk=
X-Received: by 10.180.73.239 with SMTP id o15mr525473wiv.14.1422540509822; Thu, 29 Jan 2015 06:08:29 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org>
In-Reply-To: <20150129140312.GA23554@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/6VYolOppVTY59nckiuBBdiyn8gKm26hpmuKPgVA=
Date: Thu, 29 Jan 2015 15:08:29 +0100
Message-ID: <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/cNh7mjNuwp983qw1mfwEmsLPofE>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 14:08:32 -0000

Hi Brian,

In my example  X is not an address of the peer.

BR, Karen

>-----Original Message-----
>From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
>Sent: Thursday, January 29, 2015 3:03 PM
>To: Karen Elisabeth Egede Nielsen
>Cc: tsvwg@ietf.org; Randall Stewart; Michael Tuexen
>Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
>
>Karen,
>
>Karen Elisabeth Egede Nielsen wrote:        (Wed, 28 Jan 2015 14:07:48)
>>    The issue we have can be illustrated by the following example:
>>
>>    A connect() towards peer address X and Y has been made at local
>>    EP. INIT is sent to Peer address X.
>>
>>    Peer EP in fact have local addresses Y and Z and an incoming
>>    collision INIT is sent from Y including Y and Z as address
>>    parameters.
>>
>>    According to the above MUST the INIT ACK should be returned to
>>    X which will be completely in vain (of course).
>
>
>  INIT --------------------> X
>
>  <------------------------- Y INIT (Y,Z)
>
>  INIT ACK ----------------> X
>
>  Why is this in vain?
>
>  X is an address of the peer.  The state cookie contains (Y,Z).
>  Why would the peer not process this INIT ACK and form the
>  association?
>
>
>--brian
>
>
>--
>Brian F. G. Bidulock
>bidulock@openss7.org
>http://www.openss7.org/


From nobody Thu Jan 29 06:16:11 2015
Return-Path: <ka-cheong.poon@oracle.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4C81A19E9 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 oteHis829odO for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:16:05 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEDDB1A047A for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:16:05 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t0TEG4qu027438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Thu, 29 Jan 2015 14:16:05 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t0TEG3GZ006732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 29 Jan 2015 14:16:04 GMT
Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id t0TEG2vH028228 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 14:16:02 GMT
Received: from [141.144.23.227] (/141.144.23.227) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 29 Jan 2015 06:16:01 -0800
Message-ID: <54CA409F.5080403@oracle.com>
Date: Thu, 29 Jan 2015 22:15:59 +0800
From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com>
In-Reply-To: <12c48c203fe56af6569f4056e6add852@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080002010507010304060505"
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/WQtIaw80fDYmiQi028pARAanhqc>
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 14:16:08 -0000

This is a multi-part message in MIME format.
--------------080002010507010304060505
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 01/28/15 09:07 PM, Karen Elisabeth Egede Nielsen wrote:
>
> Hi,
>
> We have stumbled into an issue with a MUST in RFC4960 text on INIT 
> Collision handling.
>
> We hope that the wg could help resolve the issue.
>
> The issue is the following underlined text of RFC4960 (from RC4460).
>
> Section 5.2.1 of RFC4960:
>
>    Upon receipt of an INIT in the COOKIE-WAIT state, an endpoint MUST
>
>    respond with an INIT ACK using the same parameters it sent in its
>
>    original INIT chunk (including its Initiation Tag, unchanged).
>
>    When responding, the endpoint MUST send the INIT ACK back to the same
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>    address that the original INIT (sent by this endpoint) was sent to.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>    Upon receipt of an INIT in the COOKIE-ECHOED state, an endpoint MUST
>
>    respond with an INIT ACK using the same parameters it sent in its
>
>    original INIT chunk (including its Initiation Tag, unchanged),
>
>    provided that no NEW address has been added to the forming
>
>    association.  If the INIT message indicates that a new address has
>
>    been added to the association, then the entire INIT MUST be
>
>    discarded, and NO changes should be made to the existing association.
>
>    An ABORT SHOULD be sent in response that MAY include the error
>
>    'Restart of an association with new addresses'.  The error SHOULD
>
>    list the addresses that were added to the restarting association.
>
> The issue we have can be illustrated by the following example:
>
>         A connect() towards peer address X and Y has been made at 
> local EP. INIT is sent to Peer address X.
>


So no INIT has been sent to Y yet?


>        Peer EP in fact have local addresses Y and Z and an incoming 
> collision INIT is sent from Y including Y and Z as address parameters.
>
>        According to the above MUST the INIT ACK should be returned to 
> X which will be completely in vain (of course).
>


If no INIT has been sent to Y, I guess the local SCTP probably should 
drop this INIT.  It is not an INIT collision.  If an INIT has also been 
sent to Y, the INIT-ACK responding to this crossed INIT should be sent 
back to Y, as described in RFC 4960.


> Note:
>
> It is understood that the in order to prevent association high jacking 
> then it is imperative that the INIT ACK be not returned to a peer address
>
> not  specified on the local EP side as a remote address for the 
> association (in cookie_wait). Thus the INIT ACK cannot simply be 
> reflected to sender address.
>
> Question:
>
> Is this the intention of the RFC4960 MUST to prescribe for this exact 
> operation.
>
> Possible answers:
>
> Â·Yes this is the intention, hopefully the association will be 
> established when local EP re-send INIT to alternative address Y
>


I think this is correct since there is no INIT sent to Y at all and no 
INIT-ACK should be triggered since the INIT from Y is dropped.


> Â·No,  the â€śMUSTâ€ť is wrong and should have read â€“ â€śSHOULD return to a 
> destination address provided in  the INIT which also is specified 
> locally as a peer address for the association (in cookie_wait)â€ť
>


I think we should not confuse protocol behavior with API goodies. At the 
protocol level, there is no INIT sent to Y, so this is not INIT 
collision and section 5.2.1. is not applicable.  If there is an INIT 
sent to Y, 5.2.1. should be followed and the INIT-ACK should be sent to Y.

-- 
K. Poon.
ka-cheong.poon@oracle.com



--------------080002010507010304060505
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 01/28/15 09:07 PM, Karen Elisabeth
      Egede Nielsen wrote:<br>
    </div>
    <blockquote
      cite="mid:12c48c203fe56af6569f4056e6add852@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1971130912;
	mso-list-type:hybrid;
	mso-list-template-ids:151650630 -912466146 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style>
      <div class="WordSection1">
        <p class="MsoNormal">Hi,</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">We have stumbled into an issue with a MUST
          in RFC4960 text on INIT Collision handling.</p>
        <p class="MsoNormal">We hope that the wg could help resolve the
          issue.</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">The issue is the following underlined text
          of RFC4960 (from RC4460). </p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">Section 5.2.1 of RFC4960:</p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  </span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â </span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  Upon receipt of an INIT in the
            COOKIE-WAIT state, an endpoint MUST</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  respond with an INIT ACK using the
            same parameters it sent in its</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  original INIT chunk (including its
            Initiation Tag, unchanged). <br>
            <br>
          </span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â Â When responding, the endpoint MUST
            send the INIT ACK back to the same</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â 
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  address that the original INIT
            (sent by this endpoint) was sent to.</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â 
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
          </span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â </span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  Upon receipt of an INIT in the
            COOKIE-ECHOED state, an endpoint MUST</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  respond with an INIT ACK using the
            same parameters it sent in its</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  original INIT chunk (including its
            Initiation Tag, unchanged),</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  provided that no NEW address has
            been added to the forming</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  association.Â  If the INIT message
            indicates that a new address has</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  been added to the association,
            then the entire INIT MUST be</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  discarded, and NO changes should
            be made to the existing association.</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  An ABORT SHOULD be sent in
            response that MAY include the error</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  'Restart of an association with
            new addresses'.Â  The error SHOULD</span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:black">Â Â  list the addresses that were added
            to the restarting association.</span></p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">The issue we have can be illustrated by the
          following example:</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">Â Â Â Â Â Â Â  A connect() towards peer address X
          and Y has been made at local EP. INIT is sent to Peer address
          X.</p>
      </div>
    </blockquote>
    <br>
    <br>
    So no INIT has been sent to Y yet?<br>
    <br>
    <br>
    <blockquote
      cite="mid:12c48c203fe56af6569f4056e6add852@mail.gmail.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">Â Â Â Â Â Â  Peer EP in fact have local addresses
          Y and Z and an incoming collision INIT is sent from Y
          including Y and Z as address parameters.</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">Â Â Â Â Â Â  According to the above MUST the INIT
          ACK should be returned to X which will be completely in vain
          (of course).</p>
      </div>
    </blockquote>
    <br>
    <br>
    If no INIT has been sent to Y, I guess the local SCTP probably
    should drop this INIT.Â  It is not an INIT collision.Â  If an INIT has
    also been sent to Y, the INIT-ACK responding to this crossed INIT
    should be sent back to Y, as described in RFC 4960.<br>
    <br>
    <br>
    <blockquote
      cite="mid:12c48c203fe56af6569f4056e6add852@mail.gmail.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal">Note:</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">It is understood that the in order to
          prevent association high jacking then it is imperative that
          the INIT ACK be not returned to a peer address </p>
        <p class="MsoNormal">not Â specified on the local EP side as a
          remote address for the association (in cookie_wait). Thus the
          INIT ACK cannot simply be reflected to sender address.</p>
        <p class="MsoNormal">Â Â Â  </p>
        <p class="MsoNormal">Question:</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">Is this the intention of the RFC4960 MUST
          to prescribe for this exact operation.</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoNormal">Possible answers:</p>
        <p class="MsoNormal">Â </p>
        <p class="MsoListParagraph" style=""><span
            style="font-family:Symbol"><span style="">Â·<span
                style="font:7.0pt &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â 
              </span></span></span>Yes this is the intention, hopefully
          the association will be established when local EP re-send INIT
          to alternative address Y</p>
      </div>
    </blockquote>
    <br>
    <br>
    I think this is correct since there is no INIT sent to Y at all and
    no INIT-ACK should be triggered since the INIT from Y is dropped.<br>
    <br>
    <br>
    <blockquote
      cite="mid:12c48c203fe56af6569f4056e6add852@mail.gmail.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoListParagraph" style=""><span
            style="font-family:Symbol"><span style="">Â·<span
                style="font:7.0pt &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â 
              </span></span></span>No, Â the â€śMUSTâ€ť is wrong and should
          have read â€“ â€śSHOULD return to a destination address provided
          in Â the INIT which also is specified locally as a peer address
          for the association (in cookie_wait)â€ť</p>
      </div>
    </blockquote>
    <br>
    <br>
    I think we should not confuse protocol behavior with API goodies.Â 
    At the protocol level, there is no INIT sent to Y, so this is not
    INIT collision and section 5.2.1. is not applicable.Â  If there is an
    INIT sent to Y, 5.2.1. should be followed and the INIT-ACK should be
    sent to Y.<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
K. Poon.
<a class="moz-txt-link-abbreviated" href="mailto:ka-cheong.poon@oracle.com">ka-cheong.poon@oracle.com</a>


</pre>
  </body>
</html>

--------------080002010507010304060505--


From nobody Thu Jan 29 06:19:22 2015
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B381A047A for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:19:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 6jFofGsiZBbu for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:19:17 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D95B1A03A3 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:19:17 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0TEJ9og030919; Thu, 29 Jan 2015 07:19:09 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0TEJ9K9024515; Thu, 29 Jan 2015 07:19:09 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id t0TEJ9n2024514; Thu, 29 Jan 2015 07:19:09 -0700
Date: Thu, 29 Jan 2015 07:19:09 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20150129141909.GA24413@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/e7Pwhun_Zp9qZsbnGRuEuvL6ykU>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 14:19:19 -0000

Karen,

If X does not belong to the peer, Why would it think that the
INIT from Y belongs to the association it is trying to form?
I don't see how it figures it is in the COOKIE-WAIT state...

--brian

Karen Elisabeth Egede Nielsen wrote:                                      (Thu, 29 Jan 2015 15:08:29)
> Hi Brian,
> 
> In my example  X is not an address of the peer.
> 
> BR, Karen
> 
> >-----Original Message-----
> >From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> >Sent: Thursday, January 29, 2015 3:03 PM
> >To: Karen Elisabeth Egede Nielsen
> >Cc: tsvwg@ietf.org; Randall Stewart; Michael Tuexen
> >Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
> >
> >Karen,
> >
> >Karen Elisabeth Egede Nielsen wrote:        (Wed, 28 Jan 2015 14:07:48)
> >>    The issue we have can be illustrated by the following example:
> >>
> >>    A connect() towards peer address X and Y has been made at local
> >>    EP. INIT is sent to Peer address X.
> >>
> >>    Peer EP in fact have local addresses Y and Z and an incoming
> >>    collision INIT is sent from Y including Y and Z as address
> >>    parameters.
> >>
> >>    According to the above MUST the INIT ACK should be returned to
> >>    X which will be completely in vain (of course).
> >
> >
> >  INIT --------------------> X
> >
> >  <------------------------- Y INIT (Y,Z)
> >
> >  INIT ACK ----------------> X
> >
> >  Why is this in vain?
> >
> >  X is an address of the peer.  The state cookie contains (Y,Z).
> >  Why would the peer not process this INIT ACK and form the
> >  association?
> >
> >
> >--brian
> >
> >
> >--
> >Brian F. G. Bidulock
> >bidulock@openss7.org
> >http://www.openss7.org/

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Jan 29 06:21:22 2015
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE3F1A19E9 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 v4-KOMQIRLhc for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:21:17 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A96CF1A064C for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:21:17 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0TELGk3030950; Thu, 29 Jan 2015 07:21:16 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0TELGsa024730; Thu, 29 Jan 2015 07:21:16 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id t0TELG1v024729; Thu, 29 Jan 2015 07:21:16 -0700
Date: Thu, 29 Jan 2015 07:21:16 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Message-ID: <20150129142116.GB24413@openss7.org>
Mail-Followup-To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>, tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <54CA409F.5080403@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54CA409F.5080403@oracle.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/Hh5msnPyJxEiMS2fQQyB3pEz6WY>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 14:21:19 -0000

Ka-Cheong,

Ka-Cheong Poon wrote:                     (Thu, 29 Jan 2015 22:15:59)
> 
>    I think we should not confuse protocol behavior with API goodies.  At
>    the protocol level, there is no INIT sent to Y, so this is not INIT
>    collision and section 5.2.1. is not applicable.  If there is an INIT
>    sent to Y, 5.2.1. should be followed and the INIT-ACK should be sent to
>    Y.

+1

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Jan 29 06:30:04 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 420BC1A008F for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:30:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 2Lx7TFrAZBMq for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:29:59 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BE5D1A1A02 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:29:59 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id fb4so27104083wid.2 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:29:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=QU4HkUA3JVS+9YvSExZqhNj/sidhzJoiX5PN7LW0ioE=; b=Ch3xpQCH3BSiswXYzLv5sLAUJ7GwGLIyfpSnIKy+wAClUopjB7y25u8mOjL386UExs mECAGt5vKFaEKOSTxuZB1d8S+Faok2O2/kQ/lv/Z6xnis30Lx771xfvGztgXOvzHagyw g5xtUP+KmQcnbJliU45EFgQEzi4cCIaVfMMKc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=QU4HkUA3JVS+9YvSExZqhNj/sidhzJoiX5PN7LW0ioE=; b=TKyURbdqXrNkRkCyUxVy/yOEVSdy+Wfur6+xDxkxVtJWCvlry460NLf/nWKPrWPK5N dQpHndN0arBxjr+SjgCoQIUnYVqAweOs9N9U1HKqnsvHg1CkDUQ14flY5zE5ep5IndOM YOBG6o7u+zbS5DNVLk4CqVhp0eBabQc/j3P8SyQI+sbPX3yaGTAR+2K/Gp76WxApzvV+ WKhrg+gLQGnVv5i2HEo7Iw8SNnTUWkcuGCa6BNGkKcYI7/Vz/wU+hH0rPit0ykH77L4M 4xx627OKs4MQ2e0DhnQTI29gyseU9vXW0S7aqK0xPRzWhVL80NL9ZJhJ8f9blyYyXrBH eELA==
X-Gm-Message-State: ALoCoQm+5vjs30DsefG+tjWOhu93lahKG6pFziteUdST3Cl8rwYEO7B3EDJqO4YLgVPDEqtHvfHmagBdDBYQIxQciNzfpNMNlwtMAzSK79SnczBsYb1nusY=
X-Received: by 10.180.73.239 with SMTP id o15mr707486wiv.14.1422541798066; Thu, 29 Jan 2015 06:29:58 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org>
In-Reply-To: <20150129141909.GA24413@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/6VYolOppVTY59nckiuBBdiyn8gKm26hpAkmbHLIB0aw/OprBuk/A
Date: Thu, 29 Jan 2015 15:29:57 +0100
Message-ID: <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/FPfLVdH1VTfLQKUur1RphvUvrdI>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 14:30:01 -0000

Hi,

The local side is in cookie_wait state as it has sent an INIT.  There can
be no question about that.
Perhaps you question is more along the lines of whether this really is  an
INIT collision scenario - ?

The local side is via connectx() configured with peer addresses X and Y,
please note that the
connectx() information is only tentative - please refer to the following
text of RFC6458 copied in below.

There is no stipulation that all the addresses given in connectx()
necessarily will become part of the association.

It this policy is assumed then the situation is much different, I agree.

BR, Karen

9.9.  sctp_connectx()

   An implementation may provide a library function (or possibly system
   call) to assist the user with associating to an endpoint that is
   multi-homed.  Much like sctp_bindx(), this call allows a caller to
   specify multiple addresses at which a peer can be reached.  The way
   the SCTP stack uses the list of addresses to set up the association
   is implementation dependent.  This function only specifies that the
   stack will try to make use of all of the addresses in the list when
   needed.

   Note that the list of addresses passed in is only used for setting up
   the association.  It does not necessarily equal the set of addresses
   the peer uses for the resulting association.  If the caller wants to
   find out the set of peer addresses, it must use sctp_getpaddrs() to
   retrieve them after the association has been set up.

>-----Original Message-----
>From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
>Sent: Thursday, January 29, 2015 3:19 PM
>To: Karen Elisabeth Egede Nielsen
>Cc: Michael Tuexen; tsvwg@ietf.org
>Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
>
>Karen,
>
>If X does not belong to the peer, Why would it think that the INIT from Y
>belongs to the association it is trying to form?
>I don't see how it figures it is in the COOKIE-WAIT state...
>
>--brian
>
>Karen Elisabeth Egede Nielsen wrote:
(Thu, 29 Jan 2015
>15:08:29)
>> Hi Brian,
>>
>> In my example  X is not an address of the peer.
>>
>> BR, Karen
>>
>> >-----Original Message-----
>> >From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
>> >Sent: Thursday, January 29, 2015 3:03 PM
>> >To: Karen Elisabeth Egede Nielsen
>> >Cc: tsvwg@ietf.org; Randall Stewart; Michael Tuexen
>> >Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960
>> >MUST
>> >
>> >Karen,
>> >
>> >Karen Elisabeth Egede Nielsen wrote:        (Wed, 28 Jan 2015
14:07:48)
>> >>    The issue we have can be illustrated by the following example:
>> >>
>> >>    A connect() towards peer address X and Y has been made at local
>> >>    EP. INIT is sent to Peer address X.
>> >>
>> >>    Peer EP in fact have local addresses Y and Z and an incoming
>> >>    collision INIT is sent from Y including Y and Z as address
>> >>    parameters.
>> >>
>> >>    According to the above MUST the INIT ACK should be returned to
>> >>    X which will be completely in vain (of course).
>> >
>> >
>> >  INIT --------------------> X
>> >
>> >  <------------------------- Y INIT (Y,Z)
>> >
>> >  INIT ACK ----------------> X
>> >
>> >  Why is this in vain?
>> >
>> >  X is an address of the peer.  The state cookie contains (Y,Z).
>> >  Why would the peer not process this INIT ACK and form the
>> > association?
>> >
>> >
>> >--brian
>> >
>> >
>> >--
>> >Brian F. G. Bidulock
>> >bidulock@openss7.org
>> >http://www.openss7.org/
>
>--
>Brian F. G. Bidulock
>bidulock@openss7.org
>http://www.openss7.org/


From nobody Thu Jan 29 06:41:38 2015
Return-Path: <ka-cheong.poon@oracle.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8A121A1A09 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:41:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 By3hGvLE43Ro for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 06:41:25 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5EAB1A038A for <tsvwg@ietf.org>; Thu, 29 Jan 2015 06:41:25 -0800 (PST)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t0TEfOns028868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Thu, 29 Jan 2015 14:41:25 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t0TEfO91004889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 29 Jan 2015 14:41:24 GMT
Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id t0TEfNMF012351 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 14:41:23 GMT
Received: from [141.144.23.227] (/141.144.23.227) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 29 Jan 2015 06:41:22 -0800
Message-ID: <54CA4690.9080605@oracle.com>
Date: Thu, 29 Jan 2015 22:41:20 +0800
From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com>
In-Reply-To: <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/2RSwGVJfTHC1e8aCqKFgwQDJ93Q>
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 14:41:31 -0000

On 01/29/15 10:29 PM, Karen Elisabeth Egede Nielsen wrote:

> The local side is in cookie_wait state as it has sent an INIT.  There can
> be no question about that.
> Perhaps you question is more along the lines of whether this really is  an
> INIT collision scenario - ?
>
> The local side is via connectx() configured with peer addresses X and Y,
> please note that the
> connectx() information is only tentative - please refer to the following
> text of RFC6458 copied in below.
>
> There is no stipulation that all the addresses given in connectx()
> necessarily will become part of the association.


Conceptually, when sctp_connectx() is used, it can be viewed as
multiple local endpoints operating independently.  This is the
reason behind the quoted paragraph below in RFC 6458.

Using your example in the previous email, conceptually there are 2
local endpoints, one tries to talk to X and the other tries to talk
to Y.  But if the endpoint trying to talk to Y has not even sent an
INIT, an incoming INIT from Y should not be considered as an INIT
collision.  But if an INIT has been sent, the INIT-ACK should be
sent back to Y as described in RFC 4960.


> It this policy is assumed then the situation is much different, I agree.
>
> BR, Karen
>
> 9.9.  sctp_connectx()
>
>     An implementation may provide a library function (or possibly system
>     call) to assist the user with associating to an endpoint that is
>     multi-homed.  Much like sctp_bindx(), this call allows a caller to
>     specify multiple addresses at which a peer can be reached.  The way
>     the SCTP stack uses the list of addresses to set up the association
>     is implementation dependent.  This function only specifies that the
>     stack will try to make use of all of the addresses in the list when
>     needed.
>
>     Note that the list of addresses passed in is only used for setting up
>     the association.  It does not necessarily equal the set of addresses
>     the peer uses for the resulting association.  If the caller wants to
>     find out the set of peer addresses, it must use sctp_getpaddrs() to
>     retrieve them after the association has been set up.



-- 
K. Poon.
ka-cheong.poon@oracle.com



From nobody Thu Jan 29 07:24:03 2015
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF421A1A9C for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 07:24:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 X3Ui_pQibGRg for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 07:23:58 -0800 (PST)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 595BC1A0092 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 07:23:57 -0800 (PST)
Received: from EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) by EVMHR67-UKRD.bt.com (10.187.101.22) with Microsoft SMTP Server (TLS) id 8.3.348.2; Thu, 29 Jan 2015 15:23:55 +0000
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) with Microsoft SMTP Server (TLS) id 8.3.348.2; Thu, 29 Jan 2015 15:23:54 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.3.181.6; Thu, 29 Jan 2015 15:23:50 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.111.16.78])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id t0TFNjU0003045;	Thu, 29 Jan 2015 15:23:47 GMT
Message-ID: <201501291523.t0TFNjU0003045@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 29 Jan 2015 15:23:46 +0000
To: "Black, David" <david.black@emc.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936319E14@MX104CL02.corp.emc. com>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com> <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm> <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk> <CE03DB3D7B45C245BCA0D24327794936276347@MX104CL02.corp.emc.com> <201501261630.t0QGUNDL016261@bagheera.jungle.bt.co.uk> <CE03DB3D7B45C245BCA0D24327794936319E14@MX104CL02.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/huByl9dsUy9QNm18Vq-nxzF00f0>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 15:24:01 -0000

David,

OK. Understood.


Bob

At 08:37 27/01/2015, Black, David wrote:
> > A specification like Lucy's is surely solely for
> > an implementer audience.
>
>With my OPS Directorate member hat on (and WG chair hat off), I
>definitely disagree ...
>
>... we routinely review all drafts for appropriate operational
>considerations - see RFC 5706, and in particular Appendix A.1,
>which is definitely applicable to this draft.
>
>Thanks,
>--David
>
> > -----Original Message-----
> > From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> > Sent: Monday, January 26, 2015 8:47 AM
> > To: Black, David
> > Cc: tsvwg@ietf.org
> > Subject: RE: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
> >
> > David,
> >
> > Apologies for the ultra-long RTT. Inline...
> >
> > At 19:03 21/11/2014, Black, David wrote:
> > >Bob,
> > >
> > > > 1) Regarding congestion control, I do not share the position of some
> > > > others in tsvwg. Congestion responsiveness is determined by how the
> > > > source spaces out the packets (i.e. their instantaneous rate). Just
> > > > because a tunnel ingress encapsulates a packet with a UDP header does
> > > > not suddenly make it unresponsive to congestion. The spacing between
> > > > packets is still determined by the source. So there is no need to
> > > > even mention congestion control considerations in a tunneling
> > > > document, except to say in the scoping at the start that the addition
> > > > of tunnel headers is completely orthogonal to congestion avoidance and
> > > > control.
> > >
> > >Unfortunately, it's not "completely orthogonal" because UDP goes many
> > >places that the encapsulated protocols can't.  Hence "can't get there
> > >from here" protection in NATs and other middleboxes that drop the
> > >unencapsulated protocol won't stop non-congestion controlled UDP-
> > >encapsulated traffic from getting into places that it shouldn't and
> > >causing damage.  Also, please take note of the text in the mpls-in-udp
> > >draft that recommends filters to block such traffic from going where
> > >it shouldn't, which restores some of these protections.
> >
> > OK, that's correct, but I should have phrased my concern differently.
> >
> > Advice on where an operator should not deploy tunnel endpoints is a
> > run-time concern, for which it is appropriate to advise operators
> > (and maybe users). A specification like Lucy's is surely solely for
> > an implementer audience. Unless we can say there is something that
> > must be implemented along with the tunnel encap/decap, surely we
> > should not hold Lucy back.
> >
> > Yes, we should work on circuit breakers for tunnels. But that's for
> > the operator audience. We should not take out our frustrations with
> > operators on implementers. We should not hold Lucy and others like
> > her back for this. She is innocent in this battle.
> >
> >
> > Bob
> >
> >
> >
> > >Thanks,
> > >--David
> > >
> > > > -----Original Message-----
> > > > From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> > > > Sent: Friday, November 21, 2014 12:30 PM
> > > > To: Lucy yong
> > > > Cc: Black, David; tsvwg@ietf.org
> > > > Subject: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
> > > >
> > > > Lucy,
> > > >
> > > > I'll wait for David's promised proposal to the list before commenting
> > > > on the checksum issue.
> > > >
> > > > 1) Regarding congestion control, I do not share the position of some
> > > > others in tsvwg. Congestion responsiveness is determined by how the
> > > > source spaces out the packets (i.e. their instantaneous rate). Just
> > > > because a tunnel ingress encapsulates a packet with a UDP header does
> > > > not suddenly make it unresponsive to congestion. The spacing between
> > > > packets is still determined by the source. So there is no need to
> > > > even mention congestion control considerations in a tunnelling
> > > > document, except to say in the scoping at the start that the addition
> > > > of tunnel headers is completely orthogonal to congestion avoidance and
> > > > control.
> > > >
> > > > 2)
> > > > Please replace:
> > > >     Tunnel end points that support
> > > >     ECN MUST use the method described in [RFC6040] for ECN marking
> > > >     propagation.
> > > > With:
> > > >     Tunnel end points need to use the method described in [RFC6040]
> > > > for ECN marking
> > > >     propagation.
> > > > Rationale:
> > > >     i) There is no such thing as a tunnel end point that does not
> > > > support ECN - it has to put something in the ECN field, and it would
> > > > not be appropriate to put anything in there other than what 
> RFC6040 says.
> > > >    ii) Generally it is not a good idea to fill one draft with
> > > > normative statements that repeat normative statements made in other
> > > > drafts. Otherwise updating an RFC gets very difficult - we have to
> > > > update all the other RFCs that gratuitously repeat what it says.
> > > >
> > > > 3) Nit in section 3.1.
> > > >     Section 5 of RFC6936 [RFC6936] specifies the additional 
> requirements
> > > >     that implementation of UDP zero-checksum over IPv6 MUST compliant
> > > >     with. To compliant with it, the following additional requirements
> > > >     apply
> > > > s/compliant/comply/ (twice)
> > > >
> > > > There are other nits, but they can be dealt with later.
> > > >
> > > >
> > > > Cheers
> > > >
> > > >
> > > > Bob
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________________________________________
> > > > Bob Briscoe,                                                  BT
> >
> > ________________________________________________________________
> > Bob Briscoe,                                                  BT

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Thu Jan 29 09:50:55 2015
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C81D1A1BDE for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 09:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 FSeXMgzro2Hx for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 09:50:32 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB47C1A1B76 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 09:50:29 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0THoO8d032176; Thu, 29 Jan 2015 10:50:24 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0THoOqn029013; Thu, 29 Jan 2015 10:50:24 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id t0THoNUZ029012; Thu, 29 Jan 2015 10:50:23 -0700
Date: Thu, 29 Jan 2015 10:50:23 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20150129175023.GA28807@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/RTtHYEVUpYvxKyEftLlFJhZk-og>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 17:50:43 -0000

Karen,

Karen Elisabeth Egede Nielsen wrote:           (Thu, 29 Jan 2015 15:29:57)
> Hi,
> 
> The local side is in cookie_wait state as it has sent an INIT.  There can
> be no question about that.

OK, but for the wrong TCB.

> Perhaps you question is more along the lines of whether this really is  an
> INIT collision scenario - ?

It is not.

> The local side is via connectx() configured with peer addresses X and Y,
> please note that the
> connectx() information is only tentative - please refer to the following
> text of RFC6458 copied in below.
> 
> There is no stipulation that all the addresses given in connectx()
> necessarily will become part of the association.

RFC6458 is INFORMATIONAL.

> It this policy is assumed then the situation is much different, I agree.

See Ka-Cheong's remarks as to why the situation is different.

Passing a list of addresses to connect is just a way of avoiding
waiting for the entire init retries and timeout between trying
another known address.  Passing it an invalid address does not
set up a collision.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Jan 29 12:35:31 2015
Return-Path: <therbert@google.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62FA01A1A28 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 uQ6E0NFhOUY6 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:35:28 -0800 (PST)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 010071A07BE for <tsvwg@ietf.org>; Thu, 29 Jan 2015 12:35:27 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id rl12so38912521iec.0 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 12:35:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jeBMPlw5CqVpvS8JqwbzVFVD+kuUAhDqedeExHrPO44=; b=ev5uyvjm8jYpaKcnNAQWPFOTpHRAKRE2c6TbFBzvFSdy3vfmSKuyKTE5Ti+SkQt3km N01oTTLIm1d8YwT47n3nlVrCX0yqIiPVr6+EqxHqt+u/cjeWHCPNDrIIU08juMK4GKue u96oZ9rM0OKI5Cx9X4mIkicCOVPQmtlRtWxHFBreiWi5k+3SKG9NusX28Nsgp87iGvnl 4p7AHtTr0KZHBzE8Z9daCaXOx2lZMjNG1czq/f5k7F84TgNvLV5ij5H70tk49sC3lxr8 GlVdN3D3mdHpkTiBvFgcLeedYrqF+30T+1cO2lRIt9jfPxiRdrTT/DT2IjN5K+f8yKU1 4f0g==
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=jeBMPlw5CqVpvS8JqwbzVFVD+kuUAhDqedeExHrPO44=; b=JVmck0iSYXkMyFgQB8CYE8sYTJ1PuNzy7eFipTpC8ECsixJ4VXgUDxcwm1yX1dGzuW cYUyWiRHiXTo+pOKURVbb9tjX/vHK/CLCyOvfVTLCk0AWQz2afOqYbVOw6yLXaHaf9OU juOnTnzR6fLJuuwU15Cej+jj/bF/4CUbf7NH5PpG0CGqEZ8+TA6u7pvSNTlrpQS+jJUB fYqHmOL8tGq78GOZeD6iDF2EcGFMGQFQ/ZU8q1o4fRPPB+dfWn7W4z2azF5gfFWecerF xnaa3gwlX0tVZ3OL0Ff/qkuFXeavE5v46W9UVmCE80BxtTLJd81G4PD8etYmD6IfMBuO wtwA==
X-Gm-Message-State: ALoCoQnNQEea0a7w7aBgX2lY/9O03jyqm2WJREswoiOOZBIqdjdwXJ3hvY6tc/wxOzivWqGSds1T
MIME-Version: 1.0
X-Received: by 10.107.39.67 with SMTP id n64mr3159145ion.36.1422563726908; Thu, 29 Jan 2015 12:35:26 -0800 (PST)
Received: by 10.64.128.129 with HTTP; Thu, 29 Jan 2015 12:35:26 -0800 (PST)
In-Reply-To: <54C2DF5D.8040800@isi.edu>
References: <20150123220911.26781.11988.idtracker@ietfa.amsl.com> <54C2DF5D.8040800@isi.edu>
Date: Thu, 29 Jan 2015 12:35:26 -0800
Message-ID: <CA+mtBx9QcCLXNMj=V1eSRCpN4a=onxgFpFimBFnupjdT40WmxQ@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/Wswta04rG2tNunRAgww-NLV_t9o>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 20:35:29 -0000

Hi Joe,

Can you clarify bullet in section 7.1 "Port numbers not intended for
intra-machine communication..."?

I assume that this means that port numbers should not be requested for
an IPC service, but using transport protocols that have ports for
intra-machine communications is reasonable (this is already a
prevalent use case). Is this interpretation correct?

For the second part of the bullet, I'm not sure why a client
connecting to server within the same host needs to be highlighted as
special case.  Rather a client is connecting to a server on the same
host, or on a different host should have the same semantics at the
network and transport layers I would think. Am I missing something?

Thanks,
Tom


On Fri, Jan 23, 2015 at 3:55 PM, Joe Touch <touch@isi.edu> wrote:
> Hi, all,
>
> This update includes minor changes to address IETF LC comments.
>
> Joe
>
> On 1/23/2015 2:09 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 Transport Area Working Group Working Group of the IETF.
>>
>>         Title           : Recommendations for Transport Port Number Uses
>>         Author          : Joe Touch
>>       Filename        : draft-ietf-tsvwg-port-use-07.txt
>>       Pages           : 22
>>       Date            : 2015-01-23
>>
>> Abstract:
>>    This document provides recommendations to application and service
>>    designers on how to use the transport protocol port number space. It
>>    complements (but does not update) RFC6335, which focuses on IANA
>>    process.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-port-use-07
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-07
>>
>>
>> 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 Jan 29 12:36:13 2015
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0824E1A7022 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 Yv9laJY3QGdu for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:36:03 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBB301A7011 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 12:36:02 -0800 (PST)
Received: from [192.168.1.200] (p508F0344.dip0.t-ipconnect.de [80.143.3.68]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 7D4701C104363; Thu, 29 Jan 2015 21:36:00 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <20150129175023.GA28807@openss7.org>
Date: Thu, 29 Jan 2015 21:35:55 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <91FD139A-1A9B-451E-BAB0-A921AA832499@fh-muenster.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org>
To: bidulock@openss7.org
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/rdtxE-DQVhy__J1OF7xJ6zVE-H8>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 20:36:05 -0000

> On 29 Jan 2015, at 18:50, Brian F. G. Bidulock <bidulock@openss7.org> =
wrote:
>=20
> Karen,
>=20
> Karen Elisabeth Egede Nielsen wrote:           (Thu, 29 Jan 2015 =
15:29:57)
>> Hi,
>>=20
>> The local side is in cookie_wait state as it has sent an INIT.  There =
can
>> be no question about that.
>=20
> OK, but for the wrong TCB.
It depends, I think.

RFC 4960 allows the upper layer to provide multiple IP addresses for the =
peer
to connect to. See the first bullet in
https://tools.ietf.org/html/rfc4960#section-5.4
When using the socket API, this might be done by using the =
sctp_connectx() call
as described in
https://tools.ietf.org/html/rfc6458#section-9.9

The question is what happens when the upper layer provides more than one =
address.
You are assuming that a TCB can have only one peer address during =
initialisation.
But this is not necessary true. A TCB could have multiple peer =
addresses. At
least in FreeBSD we allow this.
If only one address is provided, there is no doubt what has to happen. =
So let us assume
endpoint A having addresses A1 and A2 and endpoint B having B1 an B2. =
Assume that the
routing is setup such that packets flow A1 <-> B1 and A2 <-> B2. And =
assume that the
flow from A1 to B1 is broken.

A binds(A1, A2);
B binds(B1, B2);
A calls sctp_connectx(B1, B2);
Now the TCB contains local addresses A1 and A2 and remote addresses B1 =
and B2.
Now an INIT[A1, A2] is sent from A1 to B1, but it never reaches B
B calls sctp_connectx(A1, A2)
Now the TCB contains local addresses B1 and B2 and remote addresses A1 =
and A2.
Now an INIT[B1,B2] is sent from B2 to A2 and it reaches A.
This is an INIT collision. Following the RFC, endpoint A has to send the =
INIT-ACK[A1, A2]
to B1, which is dropped again. What Karen is suggesting is that sending =
the INIT-ACK[A1, A2]
from A2 to B2 should also be allowed.

If you restrict TCBs to a single peer address you avoid the above, but I =
don't see
any reason why it is not allowed (I also see no requirement in RFC 4960 =
that it must be supported).

Best regards
Michael
>=20
>> Perhaps you question is more along the lines of whether this really =
is  an
>> INIT collision scenario - ?
>=20
> It is not.
>=20
>> The local side is via connectx() configured with peer addresses X and =
Y,
>> please note that the
>> connectx() information is only tentative - please refer to the =
following
>> text of RFC6458 copied in below.
>>=20
>> There is no stipulation that all the addresses given in connectx()
>> necessarily will become part of the association.
>=20
> RFC6458 is INFORMATIONAL.
>=20
>> It this policy is assumed then the situation is much different, I =
agree.
>=20
> See Ka-Cheong's remarks as to why the situation is different.
>=20
> Passing a list of addresses to connect is just a way of avoiding
> waiting for the entire init retries and timeout between trying
> another known address.  Passing it an invalid address does not
> set up a collision.
>=20
> --brian
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
>=20


From nobody Thu Jan 29 12:38:51 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB3C1A1B0A for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:38:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 l_dZs4WCZbfE for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:38:44 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CFA91A1A2C for <tsvwg@ietf.org>; Thu, 29 Jan 2015 12:38:44 -0800 (PST)
Received: from [192.168.1.200] (p508F0344.dip0.t-ipconnect.de [80.143.3.68]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id B27D81C104363; Thu, 29 Jan 2015 21:38:42 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <54CA4690.9080605@oracle.com>
Date: Thu, 29 Jan 2015 21:38:37 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <48621834-231B-4AAC-A8DE-FA0C911992FA@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <54CA4690.9080605@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/b884rQEB_AZbhCwxVTkgvQYKsjk>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 20:38:47 -0000

> On 29 Jan 2015, at 15:41, Ka-Cheong Poon <ka-cheong.poon@oracle.com> wrote:
> 
> On 01/29/15 10:29 PM, Karen Elisabeth Egede Nielsen wrote:
> 
>> The local side is in cookie_wait state as it has sent an INIT.  There can
>> be no question about that.
>> Perhaps you question is more along the lines of whether this really is  an
>> INIT collision scenario - ?
>> 
>> The local side is via connectx() configured with peer addresses X and Y,
>> please note that the
>> connectx() information is only tentative - please refer to the following
>> text of RFC6458 copied in below.
>> 
>> There is no stipulation that all the addresses given in connectx()
>> necessarily will become part of the association.
> 
> 
> Conceptually, when sctp_connectx() is used, it can be viewed as
> multiple local endpoints operating independently.  This is the
> reason behind the quoted paragraph below in RFC 6458.
You are right, it "can" be viewed like that. The wording is very vague
(intentionally, if I remember correctly). But you could also view
it as one end-point with multiple remote addresses... In that case
Karens argument is correct. In you case you always have only one
peer address and there is no difference between RFC 4960 and what
Karen is suggesting.

Best regards
Michael
> 
> Using your example in the previous email, conceptually there are 2
> local endpoints, one tries to talk to X and the other tries to talk
> to Y.  But if the endpoint trying to talk to Y has not even sent an
> INIT, an incoming INIT from Y should not be considered as an INIT
> collision.  But if an INIT has been sent, the INIT-ACK should be
> sent back to Y as described in RFC 4960.
> 
> 
>> It this policy is assumed then the situation is much different, I agree.
>> 
>> BR, Karen
>> 
>> 9.9.  sctp_connectx()
>> 
>>    An implementation may provide a library function (or possibly system
>>    call) to assist the user with associating to an endpoint that is
>>    multi-homed.  Much like sctp_bindx(), this call allows a caller to
>>    specify multiple addresses at which a peer can be reached.  The way
>>    the SCTP stack uses the list of addresses to set up the association
>>    is implementation dependent.  This function only specifies that the
>>    stack will try to make use of all of the addresses in the list when
>>    needed.
>> 
>>    Note that the list of addresses passed in is only used for setting up
>>    the association.  It does not necessarily equal the set of addresses
>>    the peer uses for the resulting association.  If the caller wants to
>>    find out the set of peer addresses, it must use sctp_getpaddrs() to
>>    retrieve them after the association has been set up.
> 
> 
> 
> -- 
> K. Poon.
> ka-cheong.poon@oracle.com
> 
> 
> 


From nobody Thu Jan 29 12:58:41 2015
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51BF91A0210 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 QE7n-ZntX3NG for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 12:58:37 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 291381A011B for <tsvwg@ietf.org>; Thu, 29 Jan 2015 12:58:37 -0800 (PST)
Received: from [192.168.1.11] (pool-71-103-148-202.lsanca.dsl-w.verizon.net [71.103.148.202]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t0TKvAFG000798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 29 Jan 2015 12:57:27 -0800 (PST)
Message-ID: <54CA9EA1.5020103@isi.edu>
Date: Thu, 29 Jan 2015 12:57:05 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Tom Herbert <therbert@google.com>
References: <20150123220911.26781.11988.idtracker@ietfa.amsl.com>	<54C2DF5D.8040800@isi.edu> <CA+mtBx9QcCLXNMj=V1eSRCpN4a=onxgFpFimBFnupjdT40WmxQ@mail.gmail.com>
In-Reply-To: <CA+mtBx9QcCLXNMj=V1eSRCpN4a=onxgFpFimBFnupjdT40WmxQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/qCBS_IGnx5kq2kZFcsGOLRmw5VE>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 20:58:40 -0000

Hi, Tom,

On 1/29/2015 12:35 PM, Tom Herbert wrote:
> Hi Joe,
>
> Can you clarify bullet in section 7.1 "Port numbers not intended for
> intra-machine communication..."?
>
> I assume that this means that port numbers should not be requested for
> an IPC service, but using transport protocols that have ports for
> intra-machine communications is reasonable (this is already a
> prevalent use case). Is this interpretation correct?

It probably would be more precise to say that "assigned port 
numbers...". It's fine to use ports for intra-machine communication, 
it's just that there should never be a need to reserve a port for that 
purpose.

> For the second part of the bullet, I'm not sure why a client
> connecting to server within the same host needs to be highlighted as
> special case.  Rather a client is connecting to a server on the same
> host, or on a different host should have the same semantics at the
> network and transport layers I would think. Am I missing something?

Port assignments are required for two machines to initiate 
communication; they need to know "where to meet".

Within a single machine, there are a variety of other methods to do that 
sort of thing - use a dynamic port and record it in a file, e.g. Thus 
intramachine comms can still use transport protocols, but need not have 
an assigned one to coordinate.

I'll see if I can insert "assigned" in the sentence above during the 
next edit round (in response to IESG review).

Thanks,

Joe

> On Fri, Jan 23, 2015 at 3:55 PM, Joe Touch <touch@isi.edu> wrote:
>> Hi, all,
>>
>> This update includes minor changes to address IETF LC comments.
>>
>> Joe
>>
>> On 1/23/2015 2:09 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 Transport Area Working Group Working Group of the IETF.
>>>
>>>          Title           : Recommendations for Transport Port Number Uses
>>>          Author          : Joe Touch
>>>        Filename        : draft-ietf-tsvwg-port-use-07.txt
>>>        Pages           : 22
>>>        Date            : 2015-01-23
>>>
>>> Abstract:
>>>     This document provides recommendations to application and service
>>>     designers on how to use the transport protocol port number space. It
>>>     complements (but does not update) RFC6335, which focuses on IANA
>>>     process.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-tsvwg-port-use-07
>>>
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-07
>>>
>>>
>>> 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 Jan 29 23:54:28 2015
Return-Path: <ka-cheong.poon@oracle.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2661A89A7 for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 23:54:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.511
X-Spam-Level: 
X-Spam-Status: No, score=-1.511 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 QCjFcnDKeS7b for <tsvwg@ietfa.amsl.com>; Thu, 29 Jan 2015 23:54:23 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 473ED1A89A4 for <tsvwg@ietf.org>; Thu, 29 Jan 2015 23:54:23 -0800 (PST)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t0U7sM7t003752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 07:54:22 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id t0U7sLkc019086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 07:54:22 GMT
Received: from abhmp0001.oracle.com (abhmp0001.oracle.com [141.146.116.7]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t0U7sLUJ010042 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 07:54:21 GMT
Received: from [141.144.23.227] (/141.144.23.227) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 29 Jan 2015 23:54:20 -0800
Message-ID: <54CB38AA.1050407@oracle.com>
Date: Fri, 30 Jan 2015 15:54:18 +0800
From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <91FD139A-1A9B-451E-BAB0-A921AA832499@fh-muenster.de>
In-Reply-To: <91FD139A-1A9B-451E-BAB0-A921AA832499@fh-muenster.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/Rh02JVln2C3NMHRUCIhF20GSBeY>
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 07:54:25 -0000

On 01/30/15 04:35 AM, Michael Tuexen wrote:
>> On 29 Jan 2015, at 18:50, Brian F. G. Bidulock <bidulock@openss7.org> wrote:
>>
>> Karen,
>>
>> Karen Elisabeth Egede Nielsen wrote:           (Thu, 29 Jan 2015 15:29:57)
>>> Hi,
>>>
>>> The local side is in cookie_wait state as it has sent an INIT.  There can
>>> be no question about that.
>>
>> OK, but for the wrong TCB.
> It depends, I think.
>
> RFC 4960 allows the upper layer to provide multiple IP addresses for the peer
> to connect to. See the first bullet in
> https://tools.ietf.org/html/rfc4960#section-5.4


It does not seem to me that point (1) in 5.4 actually means that.
The address used to send an INIT is considered confirmed because
it is this INIT packet which triggers the peer to send an INIT-ACK.
So this address cannot be "invalid", otherwise no INIT-ACK will be
sent back.  Using Karen's original example, can SCTP mark X as
confirmed in the new association?  No, it cannot.  SCTP cannot even
include X in the peer address list of the new association.  SCTP
cannot know which address is available and is being used at the peer.
It only knows that the peer responds to its INIT, so the address INIT
uses to reach the peer is valid, hence confirmed.  One INIT cannot
and must not confirm multiple peer addresses.  This is against the
spirit of section 5.4, Path Verification.


> When using the socket API, this might be done by using the sctp_connectx() call
> as described in
> https://tools.ietf.org/html/rfc6458#section-9.9
>
> The question is what happens when the upper layer provides more than one address.
> You are assuming that a TCB can have only one peer address during initialisation.


Note that I am not talking about API nor implementation.  I am
talking strictly at the protocol level.


> But this is not necessary true. A TCB could have multiple peer addresses. At
> least in FreeBSD we allow this.


Sure.  I expect that all SCTP implementations' PCB can hold more
than one peer address since it is SCTP which supports the use of
multiple addresses :-)


> If only one address is provided, there is no doubt what has to happen. So let us assume
> endpoint A having addresses A1 and A2 and endpoint B having B1 an B2. Assume that the
> routing is setup such that packets flow A1 <-> B1 and A2 <-> B2. And assume that the
> flow from A1 to B1 is broken.
>
> A binds(A1, A2);
> B binds(B1, B2);
> A calls sctp_connectx(B1, B2);
> Now the TCB contains local addresses A1 and A2 and remote addresses B1 and B2.
> Now an INIT[A1, A2] is sent from A1 to B1, but it never reaches B
> B calls sctp_connectx(A1, A2)
> Now the TCB contains local addresses B1 and B2 and remote addresses A1 and A2.
> Now an INIT[B1,B2] is sent from B2 to A2 and it reaches A.
> This is an INIT collision.


I think this is not an INIT collision.  No INIT from A has been sent
to B2.  So an INIT from B2 to A2 does not "collide" with the INIT
from A1 to B1.


> Following the RFC, endpoint A has to send the INIT-ACK[A1, A2]
> to B1, which is dropped again. What Karen is suggesting is that sending the INIT-ACK[A1, A2]
> from A2 to B2 should also be allowed.


IMHO, this is not the proper way to think of SCTP.  This is making
the protocol semantics much more complicated as it unnecessarily
ties the protocol to implementation details.

 From an implementation point of view, using 1-1 style socket, the
example can be considered as following.  Suppose listen() has been
called by A.  When A gets the INIT (B2 to A2) from B, it can be
considered as an initialization request from B.  So an INIT-ACK
(A2 to B2) will be sent to B.  Suppose listen() has not been called,
the INIT (B2 to A2) needs to be dropped.


> If you restrict TCBs to a single peer address you avoid the above, but I don't see
> any reason why it is not allowed (I also see no requirement in RFC 4960 that it must be supported).


An implementation does not need to disallow that.  But it is
implementation details.


-- 
K. Poon.
ka-cheong.poon@oracle.com



From nobody Fri Jan 30 00:03:33 2015
Return-Path: <ka-cheong.poon@oracle.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD671A89B0 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OpGPbGygfhPX for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:03:30 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D75731A89AE for <tsvwg@ietf.org>; Fri, 30 Jan 2015 00:03:29 -0800 (PST)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t0U83S12009533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 08:03:29 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t0U83RcX018901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 08:03:28 GMT
Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id t0U83Qcm028388 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 08:03:27 GMT
Received: from [141.144.23.227] (/141.144.23.227) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 30 Jan 2015 00:03:26 -0800
Message-ID: <54CB3ACC.2070207@oracle.com>
Date: Fri, 30 Jan 2015 16:03:24 +0800
From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <54CA4690.9080605@oracle.com> <48621834-231B-4AAC-A8DE-FA0C911992FA@lurchi.franken.de>
In-Reply-To: <48621834-231B-4AAC-A8DE-FA0C911992FA@lurchi.franken.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/zM_3O0FQNleGJu8yYiRACa8986c>
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 08:03:31 -0000

On 01/30/15 04:38 AM, Michael Tuexen wrote:
>> On 29 Jan 2015, at 15:41, Ka-Cheong Poon <ka-cheong.poon@oracle.com> wrote:

>> Conceptually, when sctp_connectx() is used, it can be viewed as
>> multiple local endpoints operating independently.  This is the
>> reason behind the quoted paragraph below in RFC 6458.
> You are right, it "can" be viewed like that. The wording is very vague
> (intentionally, if I remember correctly). But you could also view
> it as one end-point with multiple remote addresses... In that case
> Karens argument is correct. In you case you always have only one
> peer address and there is no difference between RFC 4960 and what
> Karen is suggesting.


What I am trying to say is that we should not mix implementation
details with protocol semantics.  An SCTP endpoint can certainly
have multiple peer addresses (this is required by SCTP) from an
implementation's perspective.  But IMHO, INIT collision has a
clear semantics in SCTP.  Karen's example is not an INIT collision
scenario.


-- 
K. Poon.
ka-cheong.poon@oracle.com



From nobody Fri Jan 30 00:22:29 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 675551A8A10 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:22:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 kUYULlXA6ah2 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:22:14 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5B9C1A8A0F for <tsvwg@ietf.org>; Fri, 30 Jan 2015 00:22:14 -0800 (PST)
Received: from [192.168.1.200] (p508F1C6A.dip0.t-ipconnect.de [80.143.28.106]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 312611C104E8D; Fri, 30 Jan 2015 09:22:12 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <54CB3ACC.2070207@oracle.com>
Date: Fri, 30 Jan 2015 09:22:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C095EF45-F6EA-44C5-A00F-7C1909B375B0@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <54CA4690.9080605@oracle.com> <48621834-231B-4AAC-A8DE-FA0C911992FA@lurchi.franken.de> <54CB3ACC.2070207@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/aDTA9FCiOh4RnPX90jGqoNpNAck>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 08:22:16 -0000

> On 30 Jan 2015, at 09:03, Ka-Cheong Poon <ka-cheong.poon@oracle.com> =
wrote:
>=20
> On 01/30/15 04:38 AM, Michael Tuexen wrote:
>>> On 29 Jan 2015, at 15:41, Ka-Cheong Poon <ka-cheong.poon@oracle.com> =
wrote:
>=20
>>> Conceptually, when sctp_connectx() is used, it can be viewed as
>>> multiple local endpoints operating independently.  This is the
>>> reason behind the quoted paragraph below in RFC 6458.
>> You are right, it "can" be viewed like that. The wording is very =
vague
>> (intentionally, if I remember correctly). But you could also view
>> it as one end-point with multiple remote addresses... In that case
>> Karens argument is correct. In you case you always have only one
>> peer address and there is no difference between RFC 4960 and what
>> Karen is suggesting.
>=20
>=20
> What I am trying to say is that we should not mix implementation
> details with protocol semantics.  An SCTP endpoint can certainly
I agree.
> have multiple peer addresses (this is required by SCTP) from an
> implementation's perspective.  But IMHO, INIT collision has a
> clear semantics in SCTP.  Karen's example is not an INIT collision
> scenario.
Well, I intentionally looked at another example, where I think we
have an INIT collision. The INIT collision is not between address
pairs, but between endpoints.

Best regards
Michael
>=20
>=20
> --=20
> K. Poon.
> ka-cheong.poon@oracle.com
>=20
>=20
>=20


From nobody Fri Jan 30 00:34:16 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7031A0187 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:34:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.52
X-Spam-Level: 
X-Spam-Status: No, score=0.52 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 P1gr60krhsSy for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:34:13 -0800 (PST)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (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 58C5D1A1A5D for <tsvwg@ietf.org>; Fri, 30 Jan 2015 00:34:13 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id h11so1300487wiw.5 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 00:34:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=uaASM38E/oNGbF/C4G/WhKWSY9D2c4lk5V6MBIT6qks=; b=CLcJ++YHxSY0CebU2zIphrDAUAdGdtcEXn1OxWlXzvWzV8/hBxOpp3CbJMis03lgQT pHDm287N4u6FjAR8uwNSe/zov5hCAwBUlKN3GnXgaEsgPZuHCUF/w4hQfHRPeMtYkp5H j4f2aMa1gNwEqtB+PNCh7RVbJ1oDxu9WskgO4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=uaASM38E/oNGbF/C4G/WhKWSY9D2c4lk5V6MBIT6qks=; b=jqBFnc/Yt9EPxvOfirg0QQiB4TI9flROLZBLiqsPk6Iii0CUcT8qtud2ycLvZGwFEc /EvzT6ny/s278S/zS4JJlpsE/ymqAuOxgUTIJm686wYyNR36p+QVZFQYaMdVW+Gk5CLB Kn6UhuXwfu95rSfrC0df3FNeLsHj6v/1sUqWpdTxWxq+iTXmFZo2HAFwZ7PR+XEbBPo9 GJpuozH+z63Y3l/xOGgSNxgsiZ0EHr1+r+wxnXFdMqKbLpeNSYHOlNdt643POUVxu7oR YK2CPCm+hF/J7lbdrNqdUWsDV877ZrqLyTsZ+UkMqOeSADWvpK2I2JfEQX2h4eb9sApj dGWg==
X-Gm-Message-State: ALoCoQmzkMFeHGpyNHIkhH6TLxI7FP3Udq23tRZGjkDA9amjiFHyL0lpXAgyOt8EBSiaQNsBSfueEyvEIOBvly6Q7ghQ3y0Ezh+ZgHLsiVWQhS3b98QDjEs=
X-Received: by 10.180.84.98 with SMTP id x2mr2537256wiy.14.1422606852124; Fri, 30 Jan 2015 00:34:12 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org>
In-Reply-To: <20150129175023.GA28807@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/6VYolOppVTY59nckiuBBdiyn8gKm26hpAkmbHLIB0aw/OgFA4Ez5AZG7+E2arEMVIA==
Date: Fri, 30 Jan 2015 09:34:11 +0100
Message-ID: <921a2bc2751ec2912b13ba07360f186d@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/SEEKLHq3mOItVlqSyBojn1jmHlc>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 08:34:15 -0000

Hi Brian,


>-----Original Message-----
>From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
>Sent: Thursday, January 29, 2015 6:50 PM
>To: Karen Elisabeth Egede Nielsen
>Cc: Michael Tuexen; tsvwg@ietf.org
>Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
>
>Karen,
>
>Karen Elisabeth Egede Nielsen wrote:           (Thu, 29 Jan 2015
15:29:57)
>> Hi,
>>
>> The local side is in cookie_wait state as it has sent an INIT.  There
>> can be no question about that.
>
>OK, but for the wrong TCB.

[Karen ] The local address and peer address Y matches the TCB.
There is definitively a collision ! :-)

>
>> Perhaps you question is more along the lines of whether this really is
>> an INIT collision scenario - ?
>
>It is not.

[Karen ] There is definitively a collision on Y address.

>
>> The local side is via connectx() configured with peer addresses X and
>> Y, please note that the
>> connectx() information is only tentative - please refer to the
>> following text of RFC6458 copied in below.
>>
>> There is no stipulation that all the addresses given in connectx()
>> necessarily will become part of the association.
>
>RFC6458 is INFORMATIONAL.
>
>> It this policy is assumed then the situation is much different, I
agree.
>
>See Ka-Cheong's remarks as to why the situation is different.
>
>Passing a list of addresses to connect is just a way of avoiding waiting
for the
>entire init retries and timeout between trying another known address.
>Passing it an invalid address does not set up a collision.

[Karen ]
The X is the address in error in this situation, not the Y address.
A MUST policy in RFC4960 to give precedence to X over Y as a valid address
does not seem very constructive.

I am fully aligned with saying that the incoming INIT should not be
rejected due to the presence of X.

Further It would not be viable to disregard the existence of the TCB when
processing the incoming INIT (if for example, the local side also would
accept
such an incoming INIT, e.g., due to it having a listening EP) and the
reasons for that is that it would open up for association high-jacking as
described from peer C.


Could you be so kind as to point to where I can find Ka-Cheong's remark ?
Thanks.

BR, Karen

>
>--brian
>
>--
>Brian F. G. Bidulock
>bidulock@openss7.org
>http://www.openss7.org/


From nobody Fri Jan 30 00:54:14 2015
Return-Path: <ka-cheong.poon@oracle.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8581A8A3D for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 fYmuxX3_ez7k for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:54:09 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC6D31A8A27 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 00:54:09 -0800 (PST)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t0U8s8TR006462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 08:54:09 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id t0U8s7w8011854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 08:54:08 GMT
Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t0U8s7RD010541 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 08:54:07 GMT
Received: from [141.144.23.227] (/141.144.23.227) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 30 Jan 2015 00:54:07 -0800
Message-ID: <54CB46AD.9040003@oracle.com>
Date: Fri, 30 Jan 2015 16:54:05 +0800
From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <54CA4690.9080605@oracle.com> <48621834-231B-4AAC-A8DE-FA0C911992FA@lurchi.franken.de> <54CB3ACC.2070207@oracle.com> <C095EF45-F6EA-44C5-A00F-7C1909B375B0@lurchi.franken.de>
In-Reply-To: <C095EF45-F6EA-44C5-A00F-7C1909B375B0@lurchi.franken.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/kIqrVk2LxNPym6tY5bvPY4jrAfw>
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 08:54:11 -0000

On 01/30/15 04:22 PM, Michael Tuexen wrote:
>> On 30 Jan 2015, at 09:03, Ka-Cheong Poon <ka-cheong.poon@oracle.com> wrote:
>>
>> On 01/30/15 04:38 AM, Michael Tuexen wrote:
>>>> On 29 Jan 2015, at 15:41, Ka-Cheong Poon <ka-cheong.poon@oracle.com> wrote:
>>
>>>> Conceptually, when sctp_connectx() is used, it can be viewed as
>>>> multiple local endpoints operating independently.  This is the
>>>> reason behind the quoted paragraph below in RFC 6458.
>>> You are right, it "can" be viewed like that. The wording is very vague
>>> (intentionally, if I remember correctly). But you could also view
>>> it as one end-point with multiple remote addresses... In that case
>>> Karens argument is correct. In you case you always have only one
>>> peer address and there is no difference between RFC 4960 and what
>>> Karen is suggesting.
>>
>>
>> What I am trying to say is that we should not mix implementation
>> details with protocol semantics.  An SCTP endpoint can certainly
> I agree.
>> have multiple peer addresses (this is required by SCTP) from an
>> implementation's perspective.  But IMHO, INIT collision has a
>> clear semantics in SCTP.  Karen's example is not an INIT collision
>> scenario.
> Well, I intentionally looked at another example, where I think we
> have an INIT collision. The INIT collision is not between address
> pairs, but between endpoints.


You are mixing implementation details with protocol semantics.
Before an association is established, there is no way an SCTP
endpoint can know the list of peer addresses will be used in
the to be established association, except the one used to send
the INIT will be there.  So in this sense, how can you say that
the above is an INIT collision?  SCTP cannot assume that B2 will
be used in the new association created because of the INIT (A1
to B1).  Then how can the INIT (B2 to A2) be considered a
collision?  As far as SCTP is concerned, INIT (B2 to A2) is an
out of the blue packet from B2.


-- 
K. Poon.
ka-cheong.poon@oracle.com



From nobody Fri Jan 30 00:56:47 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD661A8A3F for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 dVqQDJG0c1Dz for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:56:43 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 745421A8994 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 00:56:43 -0800 (PST)
Received: from [192.168.1.200] (p508F1C6A.dip0.t-ipconnect.de [80.143.28.106]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id B751E1C104E8D; Fri, 30 Jan 2015 09:56:41 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <54CB38AA.1050407@oracle.com>
Date: Fri, 30 Jan 2015 09:56:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF0D4470-E6D2-4FFD-9D77-3BAD130B9FF7@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <91FD139A-1A9B-451E-BAB0-A921AA832499@fh-muenster.de> <54CB38AA.1050407@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/NZKWINvVEu8jWC6t6lJeBwxAtRk>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 08:56:45 -0000

> On 30 Jan 2015, at 08:54, Ka-Cheong Poon <ka-cheong.poon@oracle.com> =
wrote:
>=20
> On 01/30/15 04:35 AM, Michael Tuexen wrote:
>>> On 29 Jan 2015, at 18:50, Brian F. G. Bidulock =
<bidulock@openss7.org> wrote:
>>>=20
>>> Karen,
>>>=20
>>> Karen Elisabeth Egede Nielsen wrote:           (Thu, 29 Jan 2015 =
15:29:57)
>>>> Hi,
>>>>=20
>>>> The local side is in cookie_wait state as it has sent an INIT.  =
There can
>>>> be no question about that.
>>>=20
>>> OK, but for the wrong TCB.
>> It depends, I think.
>>=20
>> RFC 4960 allows the upper layer to provide multiple IP addresses for =
the peer
>> to connect to. See the first bullet in
>> https://tools.ietf.org/html/rfc4960#section-5.4
>=20
>=20
> It does not seem to me that point (1) in 5.4 actually means that.
Well, I think it makes clear that the upper layer can provide multiple
addresses during association setup. One way to handle this is to
create an end-point with multiple peer addresses (all of them =
confirmed).
> The address used to send an INIT is considered confirmed because
> it is this INIT packet which triggers the peer to send an INIT-ACK.
One way to look at it. Another way: All addresses provided by the
upper layer are considered confirmed. This is what section 5.4 says.

Assume the client calls
sctp_bindx(A1, A2);
sctp_connectx(B1, B2);
Then you see on the wire:
A1->B1: INIT[A1, A2]
B1->A1: INIT-ACK[B1, b2]
A1->B1: COOKIE-ECHO
B1->A1: COOKIE-ACK
Now the client send user data and it is valid that you see
A2->B2: DATA

This would not be OK, if the client would have called connect(B1) or =
sctp_connectx(B1).
> So this address cannot be "invalid", otherwise no INIT-ACK will be
> sent back.  Using Karen's original example, can SCTP mark X as
> confirmed in the new association?  No, it cannot.  SCTP cannot even
> include X in the peer address list of the new association.  SCTP
> cannot know which address is available and is being used at the peer.
Well, it would be when the end-point is in COOKIE-WAIT. After the
handshake has completed, the peer address would be removed from the =
association.
> It only knows that the peer responds to its INIT, so the address INIT
> uses to reach the peer is valid, hence confirmed.  One INIT cannot
> and must not confirm multiple peer addresses.  This is against the
> spirit of section 5.4, Path Verification.
The spirit of section 5.4 in my understanding is that path verification
makes sure that the peer doesn't lie about its addresses. So they need
to be confirmed via the HB procedure. However, the stack trusts its =
upper
layer. That is what point 1) of
https://tools.ietf.org/html/rfc4960#section-5.4
is about.
>=20
>=20
>> When using the socket API, this might be done by using the =
sctp_connectx() call
>> as described in
>> https://tools.ietf.org/html/rfc6458#section-9.9
>>=20
>> The question is what happens when the upper layer provides more than =
one address.
>> You are assuming that a TCB can have only one peer address during =
initialisation.
>=20
>=20
> Note that I am not talking about API nor implementation.  I am
> talking strictly at the protocol level.
I agree. If the API allows the upper layer to provide multiple addresses
or a single on is an API issue. If the upper layer allows this and you
allow an TCB to handle multiple addresses already in COOKIE-WAIT I think
my example show an INIT collision at the protocol level.
>=20
>=20
>> But this is not necessary true. A TCB could have multiple peer =
addresses. At
>> least in FreeBSD we allow this.
>=20
>=20
> Sure.  I expect that all SCTP implementations' PCB can hold more
> than one peer address since it is SCTP which supports the use of
> multiple addresses :-)
Sure... But I had the impression that when I call
fd =3D socket();
sctp_connectx(fd, {B1, B2}, 2);
you were considering it as two TCBs each having a single remote address.
I consider it a single TCB having two remote addresses.
I think we agree that we both end up with a single TCB having two remote =
addresses.
>=20
>=20
>> If only one address is provided, there is no doubt what has to =
happen. So let us assume
>> endpoint A having addresses A1 and A2 and endpoint B having B1 an B2. =
Assume that the
>> routing is setup such that packets flow A1 <-> B1 and A2 <-> B2. And =
assume that the
>> flow from A1 to B1 is broken.
>>=20
>> A binds(A1, A2);
>> B binds(B1, B2);
>> A calls sctp_connectx(B1, B2);
>> Now the TCB contains local addresses A1 and A2 and remote addresses =
B1 and B2.
>> Now an INIT[A1, A2] is sent from A1 to B1, but it never reaches B
>> B calls sctp_connectx(A1, A2)
>> Now the TCB contains local addresses B1 and B2 and remote addresses =
A1 and A2.
>> Now an INIT[B1,B2] is sent from B2 to A2 and it reaches A.
>> This is an INIT collision.
>=20
>=20
> I think this is not an INIT collision.  No INIT from A has been sent
> to B2.  So an INIT from B2 to A2 does not "collide" with the INIT
> from A1 to B1.
I consider a collision on the end-point base, not on the address pair =
base.
The INIT received by A comes from B2 goes to A1 and contains A1 and A2. =
So A
can find the TCB which has the local addresses A1 and A2 and remote =
addresses B1 and B2.
So I consider it a collision.
http://tools.ietf.org/html/rfc4960#section-5.2.1
talks about receiving an INIT in COOKIE-WAIT. Endpoint A is in =
COOKIE-WAIT...
>=20
>=20
>> Following the RFC, endpoint A has to send the INIT-ACK[A1, A2]
>> to B1, which is dropped again. What Karen is suggesting is that =
sending the INIT-ACK[A1, A2]
>> from A2 to B2 should also be allowed.
>=20
>=20
> IMHO, this is not the proper way to think of SCTP.  This is making
> the protocol semantics much more complicated as it unnecessarily
> ties the protocol to implementation details.
I think it is an INIT collision and the condition introduced when moving
from RFC 2960 to RFC 4960 is stricter than necessary.
>=20
> =46rom an implementation point of view, using 1-1 style socket, the
> example can be considered as following.  Suppose listen() has been
> called by A.  When A gets the INIT (B2 to A2) from B, it can be
> considered as an initialization request from B.  So an INIT-ACK
> (A2 to B2) will be sent to B.  Suppose listen() has not been called,
> the INIT (B2 to A2) needs to be dropped.
Sure. But I'm looking at the collision case. Concentrating on A this =
would mean
fd =3D socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP);
sctp_bindx(3, {A1, A2}, 2);
sctp_connectx(3, {B1, B2}, 2, ...);
Now you would see an INIT[A1, A2] from A1 to B1.
If endpoint now receives an INIT[B1, B2] from B2 to A2, it looks up the =
TCB
and finds it (because the upper layer provided B2 as a peer address),
it is in COOKIE-WAIT and therefore it is an INIT collision.
It should be allowed to send the INIT-ACK[A1, A2] from A2 to B2.
>> A binds(A1, A2);
>> B binds(B1, B2);
>> A calls sctp_connectx(B1, B2);
>> Now the TCB contains local addresses A1 and A2 and remote addresses =
B1 and B2.
>> Now an INIT[A1, A2] is sent from A1 to B1, but it never reaches B
>> B calls sctp_connectx(A1, A2)
>> Now the TCB contains local addresses B1 and B2 and remote addresses =
A1 and A2.
>> Now an INIT[B1,B2] is sent from B2 to A2 and it reaches A.
>> This is an INIT collision.
>=20
>=20
>> If you restrict TCBs to a single peer address you avoid the above, =
but I don't see
>> any reason why it is not allowed (I also see no requirement in RFC =
4960 that it must be supported).
>=20
>=20
> An implementation does not need to disallow that.  But it is
> implementation details.
Agreed.

Best regards
Michael
>=20
>=20
> --=20
> K. Poon.
> ka-cheong.poon@oracle.com
>=20
>=20
>=20


From nobody Fri Jan 30 00:58:43 2015
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18ECA1A8A43 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 FW-T_-B0TNCF for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 00:58:38 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2819D1A8A41 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 00:58:38 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0U8wWO2003872; Fri, 30 Jan 2015 01:58:32 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0U8wWno009181; Fri, 30 Jan 2015 01:58:32 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id t0U8wWBA009180; Fri, 30 Jan 2015 01:58:32 -0700
Date: Fri, 30 Jan 2015 01:58:32 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20150130085832.GA8986@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <921a2bc2751ec2912b13ba07360f186d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <921a2bc2751ec2912b13ba07360f186d@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/fGJyh4M8-Sx6AmnkxjX5FP0fs00>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 08:58:40 -0000

Karen,

Karen Elisabeth Egede Nielsen wrote:           (Fri, 30 Jan 2015 09:34:11)
> >>
> >> The local side is in cookie_wait state as it has sent an INIT.  There
> >> can be no question about that.
> >
> >OK, but for the wrong TCB.
> 
> [Karen ] The local address and peer address Y matches the TCB.
> There is definitively a collision ! :-)

Well, no.

INIT #1   (A,B) --- (X)

INIT #2   (Y,Z) --- (A)

This is a disjoint set of transport addresses.
By definition, there is no collision.

If you are adding (Y)--an unverified address--to 
the TCB of INIT #1 before forming the association,
that is your problem, not that of the protocol or
the peer.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Fri Jan 30 01:06:03 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 331101A016C for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 01:05:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 4bJq-dvq1pgH for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 01:05:52 -0800 (PST)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 094E81A8A47 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 01:05:50 -0800 (PST)
Received: by mail-we0-f169.google.com with SMTP id u56so25939540wes.0 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 01:05:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=DvCaV3IHiq6uyYXzdyy83WPp6pVW83SIg76XyADsldI=; b=WQ10QhWOcUccoVIFYQDrvTtZywysbibav68wCufIrnaorrKtce0eRVdxlJK1qM6sCr DJSoo5RXuO/MZOZPBlPfC2Oz7gYT8untmp/fTclWPK2E8GM6ESW5HITIQc0VCrhbhj4s fK+ORH9AP9K7r3D27VjLLIURkN16I0D6a+gX0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=DvCaV3IHiq6uyYXzdyy83WPp6pVW83SIg76XyADsldI=; b=LRGWs8o9N16wnqmsIQFrQpc09JsBP4b6jtXAlu5d62/0pP3jZdvRqVvCktdidGh7f9 cI6w/Kcl/Ds+FkpdsilE//gcg1s4GgMXVRoCwtTleVhB/8nfEhIVLPXqMaQ6yL7z0gaZ J/IBR5Wemk4IsxWPYG8mmRtPw6BvH9nNVkSTrgLpJXVhYH5MBDPhSj6NzOro4TKEBwer yzD3RoEgIRz62C0hLLODQ6WW9VgJLJO48OUORgyHzvta0128lsFenxBXux0Benb/OxqR kzZt4u5Vv8x+5+mg6MTA1lmrQ7GOY4A3grv/KMD97flXfzkPw3S9+reRN0nMURK4gggk AmYQ==
X-Gm-Message-State: ALoCoQnY57lKqHttZNUG6Zmrzf22FKaCXaAUF7cS2RlIX0syL1cvT9RLoh0aiEcKlL9S/Rdn5zjJtJ762cdVJZfuiafe1dunG8Gy4mPRQUeNAZuan7qfjXQ=
X-Received: by 10.180.73.239 with SMTP id o15mr2759501wiv.14.1422608749295; Fri, 30 Jan 2015 01:05:49 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <921a2bc2751ec2912b13ba07360f186d@mail.gmail.com> <20150130085832.GA8986@openss7.org>
In-Reply-To: <20150130085832.GA8986@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/6VYolOppVTY59nckiuBBdiyn8gKm26hpAkmbHLIB0aw/OgFA4Ez5AZG7+E0CPNlqcwG5HNNimoytw4A=
Date: Fri, 30 Jan 2015 10:05:48 +0100
Message-ID: <ef901de82e06329e4c20aab9275c69b1@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/z11z909FPrerQP_kVPwfqafd2Jo>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 09:05:56 -0000

Hi Brian,

The X is just as verified as the Y. There really is no difference from a
protocol perspective. Both X and Y are configured by the ULP.

The RFC4960 MUST text seems to refer to a situation where only one peer
address is given to the SCTP layer.
This protocol restrictions is not in the RFC4960 and further it is a
restriction not followed by SCTP socket api implementations
supporting connextx(). (And I think that we can could write a book about
the deployment merits of connectx() in terms of providing a robust
interworkable operation...)

I would say that the RFC4960 MUST seems to refer to a particular situation
and that the general text should indeed by as specified by Michael:

 The INIT-ACK MUST only be sent to an address configured by the upper
layer
 The INIT-ACK MUST only be sent to an address reported in the incoming
INIT
 The INIT-ACK SHOULD be sent to the source address of the received INIT.


BR, Karen



>-----Original Message-----
>From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
>Sent: Friday, January 30, 2015 9:59 AM
>To: Karen Elisabeth Egede Nielsen
>Cc: Michael Tuexen; tsvwg@ietf.org
>Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
>
>Karen,
>
>Karen Elisabeth Egede Nielsen wrote:           (Fri, 30 Jan 2015
09:34:11)
>> >>
>> >> The local side is in cookie_wait state as it has sent an INIT.
>> >> There can be no question about that.
>> >
>> >OK, but for the wrong TCB.
>>
>> [Karen ] The local address and peer address Y matches the TCB.
>> There is definitively a collision ! :-)
>
>Well, no.
>
>INIT #1   (A,B) --- (X)
>
>INIT #2   (Y,Z) --- (A)
>
>This is a disjoint set of transport addresses.
>By definition, there is no collision.
>
>If you are adding (Y)--an unverified address--to the TCB of INIT #1
before
>forming the association, that is your problem, not that of the protocol
or the
>peer.
>
>--
>Brian F. G. Bidulock
>bidulock@openss7.org
>http://www.openss7.org/


From nobody Fri Jan 30 01:20:22 2015
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 126C51A8A43 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 01:20:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 IfBqBFCBuVKr for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 01:20:18 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14F1B1A8A74 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 01:20:17 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0U9KE3K003984; Fri, 30 Jan 2015 02:20:14 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id t0U9KEHm009540; Fri, 30 Jan 2015 02:20:14 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id t0U9KEhT009539; Fri, 30 Jan 2015 02:20:14 -0700
Date: Fri, 30 Jan 2015 02:20:14 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20150130092014.GB8986@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <921a2bc2751ec2912b13ba07360f186d@mail.gmail.com> <20150130085832.GA8986@openss7.org> <ef901de82e06329e4c20aab9275c69b1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ef901de82e06329e4c20aab9275c69b1@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/97bg67db3GHBbZNsS4e_zvBFfHk>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 09:20:20 -0000

Karen,

Karen Elisabeth Egede Nielsen wrote:        (Fri, 30 Jan 2015 10:05:48)
> Hi Brian,
> 
> The X is just as verified as the Y. There really is no difference from a
> protocol perspective. Both X and Y are configured by the ULP.

No, when I launch the INIT to X, I cannot know that Y
will be part of the association.  So Y is not part of
the association until the peer tells me so in an INIT-ACK.
When the peer sends it in an INIT-ACK, I can treat Y
as "confirmed" and not send nonces to it; but until I
receive it in the INIT-ACK it is not part of the association.
I cannot predict (particularly based solely on erroneous
user input) what addresses the peer might want to add
to the association.  I only know that X is part of it.

Thus,

INIT #1 (A,B) -- (X)

INIT #2 (Y,Z) -- (A)

Remember, INITs are OOTB.  INIT #2 could have come
from anywhere.  We do not let A/B send INIT #1 to any
other address just because an OOTB packet told it to.

It is only harmless for us to send INIT#1 to the same
address that it was originally sent.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Fri Jan 30 01:30:08 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 271A11A8A6D for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 01:30:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 MjDmhl1LqLFW for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 01:30:06 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5C6B1A8A75 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 01:30:05 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id m14so26026463wev.11 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 01:30:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=A5MUKEafVPOlUlPZLiC703wCjEStwJ6PVAeqcOndVlY=; b=4dMnRycHloOtVR6cb7UMO9IPQGfjGfBmGNzS3yuj8XE5eXZVHg4PSNYmtNcggYZRj1 asHuUo11kPzaOf9MU/bUVHaDbkfHOpn22H6YNdwILK9VO7NhvpkwveklTZUhrDtHAizL /PfMKHMUAPc3rTWlp/lT90RnDl4ilxQL3OMbE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=A5MUKEafVPOlUlPZLiC703wCjEStwJ6PVAeqcOndVlY=; b=EHQ0I9NAENld+Hamu3xGr7t2PVzuw5JRMa2//9jU1VYeUm0VkhXhIadO2N/vxOxrRT 4IO4roMG007Xl7FuSwj2BBLfJnnG8OZmW0PDZFC7+sLOg7YJqkcWEwY7DtzVQf6u85+n PZHV3yn9gVTzdYzw8XOObpINwZWlnJGXji/iTPZO8gQ2pftXh6N3ayG90kcfv051rRVC ynI+NyhN7X9TkAtC5f3ot4DlDS0JPWk2CMiDKV3dZYNFaHjGjOOlL8/88PhtVO8Pgw9G kAPrXCTqRu9TzC+C9relFxZwqRPluNBvQ/HGImaWfDRZLcllS2EgimwVlqt3EDXH/AWy b9nw==
X-Gm-Message-State: ALoCoQmWKMaQJaJYUul1loC23W1k6mVBvOuouL37jDRNqvkADRAhGzCToa2C4bfa5W+ISY3znscTMSk8MsUYWyeqzq6YrXkvzjxElorPXNWYH7gFeESNO+4=
X-Received: by 10.194.78.97 with SMTP id a1mr9920693wjx.104.1422610204399; Fri, 30 Jan 2015 01:30:04 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <921a2bc2751ec2912b13ba07360f186d@mail.gmail.com> <20150130085832.GA8986@openss7.org> <ef901de82e06329e4c20aab9275c69b1@mail.gmail.com> <20150130092014.GB8986@openss7.org>
In-Reply-To: <20150130092014.GB8986@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/6VYolOppVTY59nckiuBBdiyn8gKm26hpAkmbHLIB0aw/OgFA4Ez5AZG7+E0CPNlqcwG5HNNiAWeSSMkChzTbgZptPfpQ
Date: Fri, 30 Jan 2015 10:30:03 +0100
Message-ID: <d958096aff90e58e4c1322bf5f7ad836@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/sf5yGfAFWnlx7hLzhghFodbgEsg>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 09:30:07 -0000

Hi Brian,

>
>No, when I launch the INIT to X, I cannot know that Y will be part of the
>association.
[Karen ]

You must then be referring to your particular implementation of SCTP.

An SCTP implementation supporting connectx() are aware of this.

NO WHERE in the normative parts of RFC4960 is it said that you only know
one peer address when you send your (first) INIT.

Further in section 5.4 of RFC4960 it is said:

   1)  Any address passed to the sender of the INIT by its upper layer
      is automatically considered to be CONFIRMED.


>So Y is not part of the association until the peer tells me so in an
>INIT-ACK.
>When the peer sends it in an INIT-ACK, I can treat Y as "confirmed"
[Karen ]
You can definitively NOT consider Y as CONFIRMED just because peer gives
it to you.
This is why Path Verification is specified. This is explained in RFC5062.

and not
>send nonces to it; but until I receive it in the INIT-ACK it is not part
of the
>association.
>I cannot predict (particularly based solely on erroneous user input) what
>addresses the peer might want to add to the association.  I only know
that X is
>part of it.
[Karen ] You know no more about X than you know about Y at this time in
stage.
>
>Thus,
>
>INIT #1 (A,B) -- (X)
>
>INIT #2 (Y,Z) -- (A)
>
>Remember, INITs are OOTB.  INIT #2 could have come from anywhere.  We do
>not let A/B send INIT #1 to any other address just because an OOTB packet
>told it to.
>
[Karen ] This is NOT the situation described. The situation described is
the situation where ULP has specified Y as well as X.

BR, Karen
>It is only harmless for us to send INIT#1 to the same address that it was
>originally sent.
>
>--brian
>
>--
>Brian F. G. Bidulock
>bidulock@openss7.org
>http://www.openss7.org/


From nobody Fri Jan 30 02:08:27 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40EDA1A8A8C for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 02:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] 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 HqrT-HhknOkB for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 02:08:23 -0800 (PST)
Received: from mailms.fh-muenster.de (mail.fh-muenster.de [212.201.120.190]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC21D1A8986 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 02:08:22 -0800 (PST)
Received: from wl-pool4-pnt-02561.uni-muenster.de (unknown [193.175.4.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: tuexen) by mailms.fh-muenster.de (Postfix) with ESMTPSA id C83E8282F65; Fri, 30 Jan 2015 11:08:20 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <20150130085832.GA8986@openss7.org>
Date: Fri, 30 Jan 2015 11:08:21 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D18807E-E9BE-4FB3-8671-2DB75689326A@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <921a2bc2751ec2912b13ba07360f186d@mail.gmail.com> <20150130085832.GA8986@openss7.org>
To: bidulock@openss7.org
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/RTBCIxHj_fOUGn475etEWDksFpo>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 10:08:24 -0000

> On 30 Jan 2015, at 09:58, Brian F. G. Bidulock <bidulock@openss7.org> =
wrote:
>=20
> Karen,
>=20
> Karen Elisabeth Egede Nielsen wrote:           (Fri, 30 Jan 2015 =
09:34:11)
>>>>=20
>>>> The local side is in cookie_wait state as it has sent an INIT.  =
There
>>>> can be no question about that.
>>>=20
>>> OK, but for the wrong TCB.
>>=20
>> [Karen ] The local address and peer address Y matches the TCB.
>> There is definitively a collision ! :-)
>=20
> Well, no.
>=20
> INIT #1   (A,B) --- (X)
>=20
> INIT #2   (Y,Z) --- (A)
>=20
> This is a disjoint set of transport addresses.
> By definition, there is no collision.
Brian,

Karens example mixes two issues:
1. X is contained in the addresses by the upper layer but is actually =
not
   an address of the peer.
2. You receive an INIT and can find the TCB if you take all addresses
   provided by the upper layer into account.
Let discuss them separately.

The issue with the text in the RFC is related to the second issue. That =
is
why I provided a different example.

Taking the multiple addresses into account, in the your scenario above =
you
show correctly the addresses on the the wire. However, the lokal =
endpoint sending
the first INIT has X and Y configured as remote addressees. Therefore it =
can
find the TCB for the second INIT.
>=20
> If you are adding (Y)--an unverified address--to=20
> the TCB of INIT #1 before forming the association,
> that is your problem, not that of the protocol or
> the peer.
Well, the protocol allows that (I wouldn't say it  requires it), but
if you all adding Y to the association, you can retransmit the INIT #1
after a timeout sending it to Y.

Dealing with the case that X actually doesn't belong to the peer adds
some complexity to the implementation is a consequence of supporting
multiple addresses during setup.
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
>=20


From nobody Fri Jan 30 08:08:53 2015
Return-Path: <ka-cheong.poon@oracle.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D06E51A90E2 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 08:08:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gfRdwcikzXvj for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 08:08:49 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEE3B1A90E0 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 08:08:48 -0800 (PST)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t0UG8la3024272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 16:08:48 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t0UG8k2f029592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <tsvwg@ietf.org>; Fri, 30 Jan 2015 16:08:47 GMT
Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t0UG8kkp018691 for <tsvwg@ietf.org>; Fri, 30 Jan 2015 16:08:46 GMT
Received: from [141.144.23.227] (/141.144.23.227) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 30 Jan 2015 08:08:46 -0800
Message-ID: <54CBAC8A.8030706@oracle.com>
Date: Sat, 31 Jan 2015 00:08:42 +0800
From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <91FD139A-1A9B-451E-BAB0-A921AA832499@fh-muenster.de> <54CB38AA.1050407@oracle.com> <AF0D4470-E6D2-4FFD-9D77-3BAD130B9FF7@lurchi.franken.de>
In-Reply-To: <AF0D4470-E6D2-4FFD-9D77-3BAD130B9FF7@lurchi.franken.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/p5p5D-Cxw-CC3K2wrIDCO5ALrDc>
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 16:08:51 -0000

On 01/30/15 04:56 PM, Michael Tuexen wrote:

>>> RFC 4960 allows the upper layer to provide multiple IP addresses for the peer
>>> to connect to. See the first bullet in
>>> https://tools.ietf.org/html/rfc4960#section-5.4
>>
>>
>> It does not seem to me that point (1) in 5.4 actually means that.
> Well, I think it makes clear that the upper layer can provide multiple
> addresses during association setup. One way to handle this is to
> create an end-point with multiple peer addresses (all of them confirmed).
>> The address used to send an INIT is considered confirmed because
>> it is this INIT packet which triggers the peer to send an INIT-ACK.
> One way to look at it. Another way: All addresses provided by the
> upper layer are considered confirmed. This is what section 5.4 says.


I guess you are saying that "Any address" used in 5.4 means "all
address".  My re-collection of RFC 4460 (discussed during SCTP
inter-ops) is that an address can only be confirmed if SCTP has
sent a packet to that address and this triggers a reply from peer.
It never occurred to me that the sentence may mean what you wrote
above since IMHO it is against the spirit of path verification.


> Assume the client calls
> sctp_bindx(A1, A2);
> sctp_connectx(B1, B2);
> Then you see on the wire:
> A1->B1: INIT[A1, A2]
> B1->A1: INIT-ACK[B1, b2]
> A1->B1: COOKIE-ECHO
> B1->A1: COOKIE-ACK
> Now the client send user data and it is valid that you see
> A2->B2: DATA


I'd say this is not valid since B2 is not confirmed as nothing
has ever been sent there.  And from a practical point of view, it
is also not desirable since SCTP does not even know if B2 is
reachable.  It makes more sense to start sending data to a known
reachable address.


> This would not be OK, if the client would have called connect(B1) or sctp_connectx(B1).
>> So this address cannot be "invalid", otherwise no INIT-ACK will be
>> sent back.  Using Karen's original example, can SCTP mark X as
>> confirmed in the new association?  No, it cannot.  SCTP cannot even
>> include X in the peer address list of the new association.  SCTP
>> cannot know which address is available and is being used at the peer.
> Well, it would be when the end-point is in COOKIE-WAIT. After the
> handshake has completed, the peer address would be removed from the association.


This is very strange.  And this kind of "automatic" address removal
is never mentioned anywhere in the protocol spec.  I think this is
introducing something new which is not covered in RFC 4960.  It is
also not talked about in RFC 5061.  Correct?  And you are saying
that RFC 4960 has an issue and this new introduction illustrates the
problem.  Right?


>> It only knows that the peer responds to its INIT, so the address INIT
>> uses to reach the peer is valid, hence confirmed.  One INIT cannot
>> and must not confirm multiple peer addresses.  This is against the
>> spirit of section 5.4, Path Verification.
> The spirit of section 5.4 in my understanding is that path verification
> makes sure that the peer doesn't lie about its addresses. So they need
> to be confirmed via the HB procedure. However, the stack trusts its upper
> layer. That is what point 1) of
> https://tools.ietf.org/html/rfc4960#section-5.4
> is about.


I guess we both understand what we are disagreeing with.  Is the
following summary correct?  Your interpretation introduces a
protocol detail (automatic peer address removal) not covered in
RFC 4960 and this causes an issue in sending INIT-ACK.  My
understanding of RFC 4960 is that things are OK and at the same
time, implementation can send the INIT-ACK without a problem.
Do you agree?


-- 
K. Poon.
ka-cheong.poon@oracle.com



From nobody Fri Jan 30 13:48:36 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A9C1A1A96 for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 13:48:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 uxdwVViiQtBs for <tsvwg@ietfa.amsl.com>; Fri, 30 Jan 2015 13:48:32 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D44641A016A for <tsvwg@ietf.org>; Fri, 30 Jan 2015 13:48:31 -0800 (PST)
Received: from [192.168.1.200] (p508F1C6A.dip0.t-ipconnect.de [80.143.28.106]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 7DAA71C10461F; Fri, 30 Jan 2015 22:48:29 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <54CBAC8A.8030706@oracle.com>
Date: Fri, 30 Jan 2015 22:48:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C204E69C-9E59-445A-8D94-B1CABEA909D9@lurchi.franken.de>
References: <12c48c203fe56af6569f4056e6add852@mail.gmail.com> <20150129140312.GA23554@openss7.org> <a2cd2c68119d5775b968e8668da1b09f@mail.gmail.com> <20150129141909.GA24413@openss7.org> <59e78fc5dde7247ab24d8e137f6622c7@mail.gmail.com> <20150129175023.GA28807@openss7.org> <91FD139A-1A9B-451E-BAB0-A921AA832499@fh-muenster.de> <54CB38AA.1050407@oracle.com> <AF0D4470-E6D2-4FFD-9D77-3BAD130B9FF7@lurchi.franken.de> <54CBAC8A.8030706@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/1RQ4jOx02Ddow664MqaCHLg-DOo>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP MH connectx(), INIT collisions and RFC4960 MUST
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 21:48:34 -0000

> On 30 Jan 2015, at 17:08, Ka-Cheong Poon <ka-cheong.poon@oracle.com> =
wrote:
>=20
> On 01/30/15 04:56 PM, Michael Tuexen wrote:
>=20
>>>> RFC 4960 allows the upper layer to provide multiple IP addresses =
for the peer
>>>> to connect to. See the first bullet in
>>>> https://tools.ietf.org/html/rfc4960#section-5.4
>>>=20
>>>=20
>>> It does not seem to me that point (1) in 5.4 actually means that.
>> Well, I think it makes clear that the upper layer can provide =
multiple
>> addresses during association setup. One way to handle this is to
>> create an end-point with multiple peer addresses (all of them =
confirmed).
>>> The address used to send an INIT is considered confirmed because
>>> it is this INIT packet which triggers the peer to send an INIT-ACK.
>> One way to look at it. Another way: All addresses provided by the
>> upper layer are considered confirmed. This is what section 5.4 says.
>=20
>=20
> I guess you are saying that "Any address" used in 5.4 means "all
> address".  My re-collection of RFC 4460 (discussed during SCTP
I'm not a native speaker so I might not got the meaning right.
If the upper layers passes B1 and B2 to the sender of the INIT
and the INIT-ACK contains B1, B2, B3 and B4.
My understanding is that B1 and B2 are confirmed by point (1) and
B3 and B4 are not confirmed by point (3). What is your understanding
of the text?
> inter-ops) is that an address can only be confirmed if SCTP has
> sent a packet to that address and this triggers a reply from peer.
My understanding is that addresses passed to the sender of the INIT
are also confirmed. In case only a single address is provided, our
views are the same. The difference is only when passing multiple =
addresses.
> It never occurred to me that the sentence may mean what you wrote
> above since IMHO it is against the spirit of path verification.
I don't think so. As I wrote: The spirit of  path verification is
to deal with the problem that the peer can lie about the addresses
the peer owns. I think this is expressed clearly in
https://tools.ietf.org/html/rfc4460#section-2.36.1
>=20
>=20
>> Assume the client calls
>> sctp_bindx(A1, A2);
>> sctp_connectx(B1, B2);
>> Then you see on the wire:
>> A1->B1: INIT[A1, A2]
>> B1->A1: INIT-ACK[B1, b2]
>> A1->B1: COOKIE-ECHO
>> B1->A1: COOKIE-ACK
>> Now the client send user data and it is valid that you see
>> A2->B2: DATA
>=20
>=20
> I'd say this is not valid since B2 is not confirmed as nothing
> has ever been sent there.  And from a practical point of view, it
It is confirmed by point (1) of
https://tools.ietf.org/html/rfc4960#section-5.4
not by the heartbeat procedure.
> is also not desirable since SCTP does not even know if B2 is
> reachable.  It makes more sense to start sending data to a known
> reachable address.
True. I only wanted to make clear what is allowed, what not.
>=20
>=20
>> This would not be OK, if the client would have called connect(B1) or =
sctp_connectx(B1).
>>> So this address cannot be "invalid", otherwise no INIT-ACK will be
>>> sent back.  Using Karen's original example, can SCTP mark X as
>>> confirmed in the new association?  No, it cannot.  SCTP cannot even
>>> include X in the peer address list of the new association.  SCTP
>>> cannot know which address is available and is being used at the =
peer.
>> Well, it would be when the end-point is in COOKIE-WAIT. After the
>> handshake has completed, the peer address would be removed from the =
association.
>=20
>=20
> This is very strange.  And this kind of "automatic" address removal
> is never mentioned anywhere in the protocol spec.  I think this is
That is correct. When the upper layer provides multiple peer addresses
you need to deal with the case the list of addresses peer provided in =
the
INIT-ACK is different from that. That is why
https://tools.ietf.org/html/rfc6458#section-9.9
contains
   Note that the list of addresses passed in is only used for setting up
   the association.  It does not necessarily equal the set of addresses
   the peer uses for the resulting association.
The way how to deal with this is implementation dependent. In FreeBSD
we just remove the peer address.
> introducing something new which is not covered in RFC 4960.  It is
> also not talked about in RFC 5061.  Correct?  And you are saying
Correct. Since no ASCONF is on the wire.
> that RFC 4960 has an issue and this new introduction illustrates the
> problem.  Right?
No.

The whole argument is that it is allowed (not required)
that an endpoint can have multiple peer addresses in COOKIE-WAIT state
and when receiving an INIT it is OK to send the INIT-ACK to any address
which is (provided by the upper layer) AND (presented in the INIT),
preferably the source address of the received INIT. That was the issue
reported by Karen. Not more, not less.
>=20
>=20
>>> It only knows that the peer responds to its INIT, so the address =
INIT
>>> uses to reach the peer is valid, hence confirmed.  One INIT cannot
>>> and must not confirm multiple peer addresses.  This is against the
>>> spirit of section 5.4, Path Verification.
>> The spirit of section 5.4 in my understanding is that path =
verification
>> makes sure that the peer doesn't lie about its addresses. So they =
need
>> to be confirmed via the HB procedure. However, the stack trusts its =
upper
>> layer. That is what point 1) of
>> https://tools.ietf.org/html/rfc4960#section-5.4
>> is about.
>=20
>=20
> I guess we both understand what we are disagreeing with.  Is the
> following summary correct?  Your interpretation introduces a
> protocol detail (automatic peer address removal) not covered in
> RFC 4960 and this causes an issue in sending INIT-ACK.  My
> understanding of RFC 4960 is that things are OK and at the same
> time, implementation can send the INIT-ACK without a problem.
> Do you agree?
The whole point of the discussion is that RFC 4960 says in
https://tools.ietf.org/html/rfc4960#section-5.2.1

   When
   responding, the endpoint MUST send the INIT ACK back to the same
   address that the original INIT (sent by this endpoint) was sent.

and it would be better to say
   When
   responding, the endpoint MUST send the INIT ACK back to an address
   which is provided by the upper layer and which is also present in
   the received INIT. If possible, it SHOULD be sent to the source
   address of the received packet containing the INIT chunk.

Please note that in the case that only a single address is provided
by the upper layer (for example connect() was used), both texts
are equivalent. If more addresses are provided, the suggested text
is a bit more flexible.

The other issue related to the removal of an address is another issue
not currently under discussion and I think we don't need a text change =
for this.
So what do you think regarding the above text change?

Best regards
Michael
>=20
>=20
> --=20
> K. Poon.
> ka-cheong.poon@oracle.com
>=20
>=20
>=20


From nobody Sat Jan 31 05:50:38 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309FE1A02BE for <tsvwg@ietfa.amsl.com>; Sat, 31 Jan 2015 05:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.789
X-Spam-Level: 
X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 obJqy0Hi95w6 for <tsvwg@ietfa.amsl.com>; Sat, 31 Jan 2015 05:50:19 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2A11A01F0 for <tsvwg@ietf.org>; Sat, 31 Jan 2015 05:50:18 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id DAA1A1B00897 for <tsvwg@ietf.org>; Sat, 31 Jan 2015 13:50:42 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Sat, 31 Jan 2015 13:50:05 -0000
Message-ID: <0442116505fe7ce3f90dd404ec3605f0.squirrel@erg.abdn.ac.uk>
Date: Sat, 31 Jan 2015 13:50:05 -0000
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/2jQ6DIINC7Csq3Lk582LZSZ2Sog>
Subject: [tsvwg] TSVWG Status Update February 2015
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 13:50:25 -0000

The list below shows the status of the working group documents as we see
it. Please check below and comment on drafts using the list. Please do
send any corrections/omissions to the chairs.

Gorry & David
(TSVWG Chairs)
February 2015

-------------------------------------------------------------------
Document recently published:

RFC 7417 draft-ietf-tsvwg-rsvp-pcn - Document Shepherd: David

-------------------------------------------------------------------
IDs in RFC Editor Queue (http://www.rfc-editor.org/queue.html) :

draft-ietf-tsvwg-sctp-dtls-encaps - PS - Document Shepherd: Gorry
Replaces: draft-tuexen-tsvwg-sctp-dtls-encaps-01
WG adopted 13/12/2013. Support {AB, IR, SL, MB, TD}
[Milestone: Jan 2014, PS] Implemented in Firefox (FF21).
Required by RTCweb. Comments received.
WGLC ended 28th February 2014.
Comments from Joe Touch (draft updated)
Review comments and revised ID published.
Eric Rescorla has reviewed this.
All authors confirmed no IPR
Write-up submitted, Comments and revised ID.
IESG evaluation: Completed.
----------------------------------------------------------

IDs in IESG evaluation:

draft-ietf-tsvwg-sctp-prpolicies - PS - Document Shepherd: Gorry
Replaces: draft-tuexen-tsvwg-sctp-prpolicies
Nov 2013, Adopted SCTP PR Polices intended for publication as a PS RFC
March 2014, Next revision expected for WGLC.
Gorry read 20-May-2014, needs to be PS, explain Info section in wrietup
Revised ID May 2014.
1-Jul-2014 Gorry reviewed standards language
WGLC started to end July 21st, 2014
- support JHS, KN, MB, IR, GF; comments from Karen Nielson, Brian
Bidulock, Gorry
Note: the socket API stuff, which is informational, is completely
implemented in FreeBSD and will be released in FreeBSD 10.1
Revised ID after WGLC
All Authors responded to IPR check.
WG Shepherd write-up 27th Oct 2014
IESG evaluation: On agenda of 2015-02-05 IESG telechat.
---
draft-ietf-tsvwg-port-use - Document Shepherd: Gorry
Replaces: draft-touch-tsvwg-port-use-00
- Intended to be advice to protocol designers needing a port.
5 people looked at this document, Prague IETF-80
Individual -01 July 2011
IETF-81 insufficient feedback from WG at this time.
IETF-82, discussed.
Adopted by WG Presented IETF-86, March 2013
Milestone updated to June 2014
Mar 2014, Chairs WGLC to be started after current WG actions.
- IANA review comments received
- Sent review requests to RAI, APPS, and SEC areas during 1st WGLC.
+ Comments May 2014: Paul Hoffman; Lars Eggert; IANA; David Black;
5 Jun 2014, WGLC completed - comments received.
Revised ID after WGLC; Elliot OK with changes;
Working Group Last Call for comments 14/10/2014, concluded 29/10/2014:
Reviewers EL, GF, DB.
All appropriate IPR disclosures have been declared 30-10-2014.
Write-up submitted. LC comments received, and revised ID submitted.
IESG evaluation: On agenda of 2015-02-19 IESG telechat

-------------------------------------------------------------------
WG Drafts with Chairs:

draft-ietf-tsvwg-sctp-failover - Document Shepherd: Gorry (was James)
Replaces: draft-nishida-tsvwg-sctp-failover
Individual-00 Presented in Prague, IETF-80.
- Understood not to conflict with draft-tuexen-tsvwg-sctp-multipath
- PF has been implemented in FreeBSD; Linux SCTP implements partially,
that they intend to implement full support and have no comments to the
technical solution; Ericsson have an implementation;
Adopted by WG 26/6/2012. [Milestone: Jul 2013, EXP]
Thought ready for WGLC, four people volunteered to review.
Review done by GF with a view to the milestone becoming PS.
++ Committed reviewers : Michael Tuexen (more if possible)
Milestone request submitted to AD/IESG
Implementation status:
PF has been coded into FreeBSD.
This feature is supported in Ericsson in-house SCTP SW implementation.
It is partially implemented in Linux SCTP SW (July 2014) with the intent
to implement.
WGLC concluded 19th November, 2014. Writeup being prepared.
Detailed standards language review being prepared (will likely require new
rev).
-------------------------------------------------------------------
Work to be discussed at next meeting:
TBD.
-------------------------------------------------------------------

WG Drafts

---
draft-ietf-tsvwg-sctp-ndata - PS - Document Shepherd: Gorry
- replaces: draft-stewart-tsvwg-sctp-ndata-03 Nov 2013,
Adopted , intended for publication as a PS RFC
Mar 2014, 5-6 people had read.
• Name change proposed at IETF-90, but needs WG consensus (Interleaved data?)
• Describe Stream Schedulers
–  Address comments received on the mailing list.
• Clarification of use-case.
• Make clear what also applies when regular DATA chunks are used.
DUE: Revised ID needed.
---
draft-ietf-tsvwg-rfc5405bis - BCP -  Document Shepherd: David
formerly draft-eggert-tsvwg-rfc5405bis - Individual,  ‘Multicast UDP
Guidelines’ incorporated
Mar 2014, the ADs proposed the WG re-open the UDP Guidelines RFC for
update to include this work and other topics.
The authors of both drafts agreed to progress this work.
Presented IETF-90, Hum supporting adoption, none against.
++ Brian Trammell and Jana agreed to review this.
Adopted as a TSVWG work item.
DUE: Please comment on list (revised ID needed)
DUE: TSVAREA presentation based on IIAB SEMI workshop - making UDP encap
easier to specify.
---
draft-ietf-tsvwg-rtcweb-qos - PS - Document Shepherd: David
- Replaces: draft-dhesikan-tsvwg-rtcweb-qos
- RTCweb and QoS Markings
- Authors requested TSVWG adoption.
- Who has read the draft? (lots 10's of people)
25-Mar-2014, Adopted by tsvwg
- Who thinks it is important to do work in the IETF? (Many)
I-D updated after initial TSVWG feedback
Mar 2014, Adoption call (strong support in WG meeting London)
Adoption call concluded 24 Match 2014: intended as a PS RFC for Sept 2014
++ Magnus agreed to review this.
Early OPS-Dir review received from Fred Baker.
Related draft Oct 2014, DART draft (draft-ietf-dart-dscp-rtp): IETF LC
completed.
DUE: Revised draft (David had concall w/authors on Jan 22).  Plan to
discuss in Dallas
---
draft-tsvwg-gre-in-udp-encap - PS - Document Contact: Gorry (Document
Shepherd: David)
- replaces: draft-yong-tsvwg-gre-in-udp-encap
Dec 2013, Adopted , intended for publication as a PS RFC
Feb 2014, discussion of scope and applicability of circuit breakers
Mar 2014 consider MUST implement, SHOULD use in these environments for CB
DUE: Revised ID needed to address congestion control and UDP Zero Checksum
for IPv6.  Revised text has been developed for MPLS-in-UDP draft, but
needs adaptation and generalization for GRE (vs. MPLS).
DUE: Revised ID expected for Dallas (was Honolulu) with initial adaptation
- expect to discuss generalization in meeting.
---
draft-ietf-tsvwg-circuit-breaker - Document Shepherd: David
- (Editor: Gorry Fairhurst)
Call for WG adoption issued - August 2014, adopted 28th Aug.
Current target is BCP, will re-evaluate (BCP vs. INFO) when draft is ready
for WGLC.
DUE: Please comment on list
---
draft-ietf-tsvwg-diffserv-intercon - Info- Document Contact: David
(Document Shepherd: Gorry)
formerly: draft-geib-tsvwg-diffserv-interco
DiffServ interconnection classes
New ID presented in Atlanta, IETF-85.
ID presented in Orlando, IETF-86, Mar 2013. Mar 2014, intended scope
unclear at IETF London Adoption call to be considered, but scope needs to
be first refined and a revised draft is necessary to avoid implications of
broader applicability.
July 2014 - ID presented in Toronto. Strong hum of support to work on
this, but a revised draft is needed first.
WG adoption call completed 2014-12-01.
DUE: Please comment on list (revised ID needed)
---
draft-ietf-tsvwg-ecn-encap-guidelines - Document Shepherd: David
replaced draft-briscoe-tsvwg-ecn-encap-guidelines
-00 Presented in Prague, IETF-80.
- comments at IETF-80 (see minutes)
New ID presented in Atlanta, IETF-85. ID presented in IETF-88,89
++ forward an appropriate message (perhaps your note to the mailing list
for approval to adopt) to ieee-ietf-coord@ietf.org)
++ Reviewers: Andrew McGregor, Dirk Kutscher, Richard Sheffnegger, Brian
Trammell, Gorry.
Mar 2014, WG Call for adoption started, to end 4th March 2014
19 for, 1 against. 8 echoed on the list
Adoption call concluded and document adopted.
* ecn-encap-guidelines and AQM are the main new things they need to know
about.
on <http://www.ietf.org/proceedings/86/train-3.html>IEEE802.1Q)
Liaison sent to IEEE 802 (Nov  24, 2014), also need to send one to 3GPP.
DUE: Please comment on list.
--
draft-ietf-tsvwg-rsvp-app-id-vv-profiles - Document Shepherd: David
Replaces: draft-polk-tsvwg-rsvp-app-id-vv-profiles
-01 Presented in Beijing, IETF-79.
-02, 14-Mar-2011
Presented IETF-80.
Seek to coordinate with music with partner ID:
draft-polk-mmusic-traffic-class-for-sdp
Gorry liaised with MMUSIC WG Chairs on companion draft (norm ref from this
tsvwg draft).
Adopted as a TSVWG work item, December 2013, [Milestone Jul 2013].
This will update a RFC 2872 (PS).
Presented at IETF-86,
Mar 2013 (no comments)
Expected ready for WGLC (waiting on MMUSIC)
DUE: Reviewers are needed to prepare for a WGLC (recently expired)
---
draft-ietf-tsvwg-natsupp - Document Shepherd: David (was James)
Replaces: draft-stewart-natsupp-tsvwg
Dependency from BEHAVE WG (no longer applicable).
Adopted as a work item 21 Sept 2010 (Gorry).
WG -00, 29/11/2010 Uploaded as: draft-ietf-natsupp-tsvwg
Authors restructured draft (-03)
Added support for single and multi-homed support.
IETF-86: 3 people in meeting had read -04 or -05.
Feb 2014, Authors please update following comments and align to related
draft on SCTP NAT (conflicts found in language)
Authors expected to produce a single document to replace both.
++ Dan Wing has committed to review this.
++ Fred Baker has committed to review this.
Chairs: We plan to start a WGLC, but are expecting this document to be
restructured and merged with draft-ietf-tsvwg-sctpnat
---
draft-ietf-tsvwg-sctpnat - Document Shepherd: Gorry
Will replace: draft-ietf-behave-sctpnat-03.txt Adopted Nov 2013.
Former BEHAVE WG work item that defines SCTP NAT support
Feb 2014, Authors please update following comments and align to related
draft on SCTP NAT (conflicts found in language)
Chairs: - authors have requested a single document to replace both.
++ Fred Baker will review next version.
Separated the simpler case for single-homed use - this separation should
be clearer
Chairs: We plan to start a WGLC, but are expecting this document to be
restructured and merged with draft-ietf-tsvwg-sctpnat

-------------------------------------------------------------------
Expired WG documents:
---
draft-ietf-tsvwg-intserv-multiple-tspec - Document Shepherd: David
WG interest in this topic recorded at IETF-78.
Charter update needed to progress this work.
5 Reviews needed to determine energy/technical direction.
WG -05 (presented in Beijing, IETF-79)
WG -06 (presented in Prague, IETF-80)
2 reviews from RSVP-DIR received (Bruce Davie, ?)
2 additional reviews promised (Ken Carlberg, Francois LeF)
Chairs asked AD for a Charter update (IESG agreed)
Draft discussed at IETF-80, and request to update charter agreed
- AD advised 4 named reviewers will be required
Adopted for progression as PS, for May 2012
- New name: 'RSVP Multiple Instance'.
Draft is now expired and dead.
DUE: Draft authors will request replacement with
draft-polk-rsvp-multi-instance-object (and WG adoption call for that draft
in Honolulu, IETF-91)
---
draft-ietf-tsvwg-behave-requirements-update - Document Shepherd: David
Replaces: draft-ietf-behave-requirements-update-00
Nov 2013, Former BEHAVE WG work item intended for publication as a BCP
Mar 2014, Irene R reviewed this and found no conflict with SCTP drafts.
Some suggestions (in no particular order) for a shepherd:
++ Dave Thaler, may review, as former behave co-chair
++ David Harrington, has been around in behave, and he knows how to do
this and volunteered multiple times.
++ Ask Jana to review this.
++ Dan has committed to review this.
Chairs: Check intention and planned timeline.
DUE: Please comment on list
---
Other drafts and work items linked to TSVWG:
draft-ietf-mpls-in-udp (IESG approval expected shortly)
draft-kumar-softwire-uet-00
draft-xu-softwire-ip-in-udp-01
draft-ietf-aqm-ecn-benefits replaces draft-welzl-ecn-benefits, to be LC'ed
in TSVWG
---
Liaisons:
ITU-T Study Group 12 Liaison on QoS Classes & markings for interconnection
IEEE liaison to support L2/L3 work on ECN marking


From nobody Sat Jan 31 17:21:02 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F56C1A7011 for <tsvwg@ietfa.amsl.com>; Sat, 31 Jan 2015 17:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.013
X-Spam-Level: 
X-Spam-Status: No, score=-105.013 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 cA8TXcXHiEll for <tsvwg@ietfa.amsl.com>; Sat, 31 Jan 2015 17:20:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACC91A1A23 for <tsvwg@ietf.org>; Sat, 31 Jan 2015 17:20:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 95D8C181CF0; Sat, 31 Jan 2015 17:20:52 -0800 (PST)
To: randall@lakerest.net, spencerdawkins.ietf@gmail.com, mls.ietf@gmail.com, gorry@erg.abdn.ac.uk, david.black@emc.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150201012052.95D8C181CF0@rfc-editor.org>
Date: Sat, 31 Jan 2015 17:20:52 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/9wBLrLUEM0XC9Xe0EHpjhxQgnEE>
Cc: tidopham@gmail.com, tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [tsvwg] [Technical Errata Reported] RFC4960 (4250)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 01:21:00 -0000

The following errata report has been submitted for RFC4960,
"Stream Control Transmission Protocol".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4960&eid=4250

--------------------------------------
Type: Technical
Reported by: Phung Pham <tidopham@gmail.com>

Section: 3.3.4

Original Text
-------------
                     +--------------------------------+
                     |   Cumulative TSN Ack = 12      |
                     +--------------------------------+
                     |        a_rwnd = 4660           |
                     +----------------+---------------+
                     | num of block=2 | num of dup=0  |
                     +----------------+---------------+
                     |block #1 strt=2 |block #1 end=3 |
                     +----------------+---------------+
                     |block #2 strt=5 |block #2 end=5 |
                     +----------------+---------------+

Corrected Text
--------------
                     +--------------------------------+
                     |   Cumulative TSN Ack = 12      |
                     +--------------------------------+
                     |        a_rwnd = 4660           |
                     +----------------+---------------+
                     | num of block=2 | num of dup=0  |
                     +----------------+---------------+
                     |block #1 strt=2 |block #1 end=3 |
                     +----------------+---------------+
                     |block #2 strt=5 |block #2 end=6 |
                     +----------------+---------------+

Notes
-----
According to the illustration of the DATA chunks just above it, with "still missing" TSN 13 and TSN 16, the block #2 end=6 not 5.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC4960 (draft-ietf-tsvwg-2960bis-05)
--------------------------------------
Title               : Stream Control Transmission Protocol
Publication Date    : September 2007
Author(s)           : R. Stewart, Ed.
Category            : PROPOSED STANDARD
Source              : Transport Area Working Group
Area                : Transport
Stream              : IETF
Verifying Party     : IESG


From nobody Sat Jan 31 23:51:32 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D95C1A8757 for <tsvwg@ietfa.amsl.com>; Sat, 31 Jan 2015 23:51:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 PMmtaROlR12u for <tsvwg@ietfa.amsl.com>; Sat, 31 Jan 2015 23:51:28 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFE481A8755 for <tsvwg@ietf.org>; Sat, 31 Jan 2015 23:51:27 -0800 (PST)
Received: from [192.168.1.200] (p508F1389.dip0.t-ipconnect.de [80.143.19.137]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 4E2771C104DA3; Sun,  1 Feb 2015 08:51:24 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <20150201012052.95D8C181CF0@rfc-editor.org>
Date: Sun, 1 Feb 2015 08:51:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <79C3D163-3B90-4723-BCF5-908317B962CD@lurchi.franken.de>
References: <20150201012052.95D8C181CF0@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/9HmxH18jYJEdoYzdMeeE09p10Cc>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tidopham@gmail.com, tsvwg@ietf.org, mls.ietf@gmail.com
Subject: Re: [tsvwg] [Technical Errata Reported] RFC4960 (4250)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 07:51:30 -0000

> On 01 Feb 2015, at 02:20, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC4960,
> "Stream Control Transmission Protocol".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D4960&eid=3D4250
>=20
> --------------------------------------
> Type: Technical
> Reported by: Phung Pham <tidopham@gmail.com>
>=20
> Section: 3.3.4
>=20
> Original Text
> -------------
>                     +--------------------------------+
>                     |   Cumulative TSN Ack =3D 12      |
>                     +--------------------------------+
>                     |        a_rwnd =3D 4660           |
>                     +----------------+---------------+
>                     | num of block=3D2 | num of dup=3D0  |
>                     +----------------+---------------+
>                     |block #1 strt=3D2 |block #1 end=3D3 |
>                     +----------------+---------------+
>                     |block #2 strt=3D5 |block #2 end=3D5 |
>                     +----------------+---------------+
>=20
> Corrected Text
> --------------
>                     +--------------------------------+
>                     |   Cumulative TSN Ack =3D 12      |
>                     +--------------------------------+
>                     |        a_rwnd =3D 4660           |
>                     +----------------+---------------+
>                     | num of block=3D2 | num of dup=3D0  |
>                     +----------------+---------------+
>                     |block #1 strt=3D2 |block #1 end=3D3 |
>                     +----------------+---------------+
>                     |block #2 strt=3D5 |block #2 end=3D6 |
>                     +----------------+---------------+
>=20
> Notes
> -----
> According to the illustration of the DATA chunks just above it, with =
"still missing" TSN 13 and TSN 16, the block #2 end=3D6 not 5.
I think the RFC is correct. The first block is TSN 14 and TSN 15. Since =
the cumulative TSN ack is 12, this
is [2, 3]. The second block consists only of TSN 17. Therefore is is =
reported as [5, 5].
The block [5, 6] as you suggest would mean that TSN 17 and TSN 18 would =
have been received, which
is not the case described in the illustration.

Best regards
Michael
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC4960 (draft-ietf-tsvwg-2960bis-05)
> --------------------------------------
> Title               : Stream Control Transmission Protocol
> Publication Date    : September 2007
> Author(s)           : R. Stewart, Ed.
> Category            : PROPOSED STANDARD
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
>=20
>=20

