
From brian.e.carpenter@gmail.com  Sun Jun  2 13:47:08 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B290421F9104 for <gen-art@ietfa.amsl.com>; Sun,  2 Jun 2013 13:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMUjyLIxqb1l for <gen-art@ietfa.amsl.com>; Sun,  2 Jun 2013 13:47:08 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC1721F909A for <gen-art@ietf.org>; Sun,  2 Jun 2013 13:47:08 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id x14so8494275ief.40 for <gen-art@ietf.org>; Sun, 02 Jun 2013 13:47:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=d7vMHBsbRAelU7bVY+KGgctDhP/7wlJeMmPw7qUAVAY=; b=rOmhXfyPhIPnqBvByYyFgoubuMT3LFuPDZYuSbFD4aUD82sJ613g30FAQn+Pssk0vS 6AQ20P7TMtpZeAGfpaLAoFfFlyNZeMN2dyyZPrcw1kjcCWkcL0sn81qnHwh6dSS09Etn Efxd7iC8uldP1r6Hr9EnLz29sq87vn4kCwQF0BN+33jXkAvDGl+Vgg+h8O9/V2RPWQqD Ov3+tj5jxXIkZrqziDd5O198oHRZ4WgRG9xUCRLDpxIqwS6Zi//hCsB9QPLNdFRcMXmb mpWxVoqffWeiXpv7c4ui15Lx3h/PjQg5OSyvkbC6sDrqzMhlnTjj/EE8gLZsDsEl+GsU 7FeA==
X-Received: by 10.50.80.101 with SMTP id q5mr6640455igx.2.1370206027751; Sun, 02 Jun 2013 13:47:07 -0700 (PDT)
Received: from [192.168.1.2] (224.171.252.27.dyn.cust.vf.net.nz. [27.252.171.224]) by mx.google.com with ESMTPSA id ct8sm15655998igb.7.2013.06.02.13.47.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Jun 2013 13:47:06 -0700 (PDT)
Message-ID: <51ABAF46.7090005@gmail.com>
Date: Mon, 03 Jun 2013 08:47:02 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-avtcore-avp-codecs.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART LC review of draft-ietf-avtcore-avp-codecs-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2013 20:47:08 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-avtcore-avp-codecs-02.txt
Reviewer: Brian Carpenter
Review Date: 2013-06-03
IETF LC End Date: 2013-06-11
IESG Telechat date:

Summary:  Ready
--------

Comments:
---------

This removes a bit of cruft from an established standard, and that seems
like a good thing to do.

Nit:
----

According to normal practice, the abstract should also specifically mention RFC 3551:

"This document updates the RTP/AVP profile (RFC 3551)..."



From hartmans@mit.edu  Sun Jun  2 15:34:52 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8473D21F8FE8; Sun,  2 Jun 2013 15:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nem9eKKnMZXU; Sun,  2 Jun 2013 15:34:46 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7170221F8FA5; Sun,  2 Jun 2013 15:34:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 55F382062F; Sun,  2 Jun 2013 18:31:19 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQnEOLlxFZpC; Sun,  2 Jun 2013 18:31:17 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Sun,  2 Jun 2013 18:31:17 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 87A89440A; Sun,  2 Jun 2013 18:34:37 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com>
Date: Sun, 02 Jun 2013 18:34:37 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> (David Black's message of "Thu, 25 Apr 2013 11:21:36 -0400")
Message-ID: <tsly5asuooy.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2013 22:34:52 -0000

>>>>> "David" == Black, David <david.black@emc.com> writes:

    David> Document: draft-ietf-karp-crypto-key-table-07 Reviewer: David
    David> L. Black Review Date: April 25, 2013 IETF LC End Date: April
    David> 29, 2013

    David> (Section 2)

    David> [1] LocalKeyName and PeerKeyName are strings.  What character
    David> set?  If Unicode (e.g., UTF-8?), add text on Unicode
    David> considerations (e.g., normalization).  Finding a Unicode
    David> expert will help in getting this done quickly.  I have
    David> similar concerns for other strings, and in particular, IANA
    David> should be told what a "string" is for any registry field that
    David> contains one.
Proposed fix;
The LocalKeyName field contains a string identifying the
key. It can be used to retrieve the key in the local database when
received in a packet.  As discussed in Section 4,  the protocol
defines  the form of this field. For example, many routing protocols
restrict the format of their key names to integers that can be
represented in 16 or 32 bits. Typically this field does not contain
data in human character sets requiring internationalization.
If there ever are any Protocols with key names requiring
internationalization, those specifications MUST address
issues of canonicalization and normalization so that key names can be
compared using binary comparison.

    David> [2] I'm not sure that I understand what a KDF really is from
    David> its high level description in this draft.  At the least, I'm
    David> surprised that the importance of non-invertibility of a KDF
    David> is not mentioned - beyond that, a functional description of
    David> inputs and outputs would help, including a strong
    David> recommendation to inject unpredictable nonce material.  This
    David> could be handled by referencing material on what a KDF is
    David> that exists elsewhere.
The KDF field indicates the key derivation function which is used to
generate short-lived keys from the long-lived value in the Key field.
When the long-lived value in the Key field is intended for direct use,
the KDF field is set to "none".  A key derivation function is a
one-way function that provides cryptographic separation of key
material.  The KDF MAY use inputs from the row in the key table and
the packet being sent or received but MUST NOT depend on other
configuration state.

    David> (Section 4)

    David> [3] It's important that this section cover all the fields
    David> involved in the database lookups in Section 3 whose format
    David> may be protocol-specific (the Direction and various time
    David> fields aren't).  Protocol should be covered by the IANA
    David> registry, peers and key names are covered here, but interface
    David> appears to be missing - item (9) covers presence vs.  absence
    David> of interface information, but not its format.
The form of the interfaces field is not protocol-specific but instead
is shared among all protocols on an implementation.  If a protocol
needs to distinguish instances running over the same interface, this
is included in the specification of peers.  Generally it is desirable
to define the specification of peers so that an operator can use the
interfaces field to refer to all instances of a protocol on a link
without having to specify both generic interfaces information and
protocol-specific peer information.

    David> --- Lots of issues with the IANA Considerations (Section 8)

I could really use some help from one of the other authors resolving the
IANA issues.
I've made the trivial fix of getting info vs values consistent.

    David> [7] Should some sort of formats for Peers and Interfaces be
    David> included in registering a Protocol?  If not, the lookups in
    David> section 3 may be implementation-dependent (strings that work
    David> w/one implementation may not work w/other implementations of
    David> the same protocol).  The specification reference may suffice
    David> based on the requirements in section 4 for what has to be in
    David> each referenced specification.

I think section 4 should  handle this.
We could add a bit of text reminding people that the specification needs
to address the issues brought up in section 4.


    David> [9] I suggest Expert Review for these registries, not just
    David> First Come First Served, so that someone with a security
    David> "clue" can check that the proposed registrations are
    David> reasonable.

I don't think I've seen support for this on the WG list.

    David> Minor issues:


I don't think it does even conceptually.
It's much closer to the SPD.
However there are no plans I'm aware of to use this to configure IPsec
and I think several of us might push back against that.

    David> [B] (Section 2) Where is key size recorded?  Is that an
    David> implicit attribute of Key?

yes.

    David> [C] (Section 3) Where does key selection occur?  I would
    David> suggest that the database return all possible keys and let
    David> the protocol figure out what to use.  This is particularly
    David> important for inbound traffic for obvious reasons.

No, the hope is that the key selection can be shared among protocols;
that's one of the main things that you get out of something like this.
The intent is that the protocol passes the things described in section 3
into the key table which pops out the right row.

We think this is solid for received packets; if you think we've missed
something please let us know: much easier to fix now!

From Francis.Dupont@fdupont.fr  Mon Jun  3 02:40:18 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E430D21F854E for <gen-art@ietfa.amsl.com>; Mon,  3 Jun 2013 02:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tma91kUuZWtM for <gen-art@ietfa.amsl.com>; Mon,  3 Jun 2013 02:40:17 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 72C5921F8C4C for <gen-art@ietf.org>; Mon,  3 Jun 2013 02:40:16 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r539eEsH093352; Mon, 3 Jun 2013 11:40:14 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201306030940.r539eEsH093352@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 03 Jun 2013 11:40:14 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-mpls-ldp-dod.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-mpls-ldp-dod-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2013 09:40:18 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-mpls-ldp-dod-08.txt
Reviewer: Francis Dupont
Review Date: 20130527
IETF LC End Date: 20130527
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 (Note most of them should be handled by the RFC Editor)

 - "Requirement Language" section page 1 is not in the body

 - the requirement keywords are not used everywhere in the document,
  if I understand well there is a normative part. BTW the question
  stands too about the Security Considerations.

 - ToC page 2 and 8 page 31: Acknowledgements -> Acknowledgments

 - I have some problems with the abbrevs, I suggest:
  * refer to the RFC Editor list to know if an abbrev is well known or not,
   in the second case consider to introduce it
  * IMHO all not well known abbrev required to understand the text or used
   more than once must be introduced at the first use
  * another way is to refer to a terminology RFC

 - 2 pages 4 and 5: figure 1 should be on one page (BTW this is a good
  example of something which could be handled by the RFC Editor)

 - same figure problems for figures 2

 - 2.1 page 8: examples of the abbrev issue with ECMP, LAG and FEC.

 - 4.1 page 19: i.e. -> i.e.,

 - 4.3.2 page 23: [RFC5036] (section A.1.1, page# 100) ->
  ([RFC5036] section A.1.1, page 100) ??

 - 4.4 page 23 and 5 page 25: the title should not be at the last line

 - 4.4 page 24, 7 page 28 and 7.1.2 page 29: e.g. -> e.g.,

 - 5 is a normative part so uses KEYWORDS (IMHO this should be explained,
  for instance in the Requirement Language section if it is moved to
  a more standard position)

 - 5 page 26: the Queue Request Type is TBD but is 0x0971 in the schema?

 - 6.1 page 27: I suggest to add a reference for RFC5036
  (i.e., RFC5036 -> [RFC5036] as it is in other positions)

 - 7: I have no problem at all (:-) with using KEYWORDS in Security
  Considerations!

 - 7 page 28: are considered as -> are applied as ?

 - 7.2 page 30 (about keywords): for instance 'should NOT' ->
  'SHOULD NOT' and keep the MAY in 5.

 - 7.3 page 30: a more questionable 'may'

 - 7.4 page 31: two should's which should be IMHO 'SHOULD'

 - Authors' Addresses page 32: another paging (?) issue

 - Authors' Addresses page 33: some issues:
 * French ZIP codes are in front (but is it possible to change from
  the XML? I don't know so if you find a simple way to fix it please
  both fix it and explain it to me)
 * ITU TS E.123 requires no optional part in the middle of a phone
  number, i.e., 1-(978)-589-8861 -> +1-978-589-8861
 * no ZIP code for London? BTW grep finds 'FELTHAM  TW14 8HA'
  (Cisco's communication department should know the canonical
   address. BTW in my company we had to agree about the canonical
   company name... :-)

Regards

Francis.Dupont@fdupont.fr

From bill.wu@huawei.com  Mon Jun  3 05:55:21 2013
Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A816321F9607 for <gen-art@ietfa.amsl.com>; Mon,  3 Jun 2013 05:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZ7nKYN5iCG8 for <gen-art@ietfa.amsl.com>; Mon,  3 Jun 2013 05:55:17 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9842621F9698 for <gen-art@ietf.org>; Mon,  3 Jun 2013 05:55:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATN35042; Mon, 03 Jun 2013 12:55:14 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 3 Jun 2013 13:54:29 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 3 Jun 2013 13:55:10 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.43]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Mon, 3 Jun 2013 20:55:06 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>, "draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-xrblock-rtcp-xr-jb-11
Thread-Index: Ac5eOyaaatHCk+4mRSSRvWQFHkZijQCHdEhQ
Date: Mon, 3 Jun 2013 12:55:05 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43B3E9BE@nkgeml501-mbs.china.huawei.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A105266@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A105266@eusaamb107.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.149]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA43B3E9BEnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-xrblock-rtcp-xr-jb-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2013 12:55:21 -0000

--_000_B8F9A780D330094D99AF023C5877DABA43B3E9BEnkgeml501mbschi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi, Meral:
Thanks for your valuable review, see my reply inline below.

Regards!
-Qin

From: Meral Shirazipour [mailto:meral.shirazipour@ericsson.com]
Sent: Saturday, June 01, 2013 4:14 AM
To: draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org; gen-art@ietf.org
Subject: Gen-ART Last Call review of draft-ietf-xrblock-rtcp-xr-jb-11

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq  .

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-xrblock-rtcp-xr-jb-11
Reviewer: Meral Shirazipour
Review Date: 2013-05-31
IETF LC End Date: 2013-05-31
IESG Telechat date: NA


Summary:
This draft is almost ready to be published as Standard RFC but I do have so=
me comments.

Nits/editorial comments:
-[Page 3], Section 1.4, Suggestion for clarity:
Old:"These metrics are used to report how the jitter buffer at the receivin=
g end of RTP stream behaves
as a result of jitter in the network and are applicable to a range of RTP a=
pplications."

New:"These metrics are used to report how the jitter buffer at the receivin=
g end of RTP stream behaves
as a result of jitter in the network; and they are applicable to a range of=
 RTP applications."

[Qin]: Okay.

-[Page 5], Section 3, paragraph 5, Suggestion for consistency:
"The Jitter Buffer"---->"The jitter buffer"

[Qin]: Okay.

-[Page 5], last sentence, Suggestion for clarity:
"Assume that both are normalized in ticks."----->
"Assume that both are normalized in ticks (there are 10 000 ticks in a mill=
isecond).

[Qin]: Okay.

-[Page 6], point (iii), Suggestion for clarity:
"If r =3D t" --suggestion--> "If r =3D=3D t"

[Qin]: Okay.

-[Page 6], point (iv), Possible inconsistance:
"Delay playout of packet by D + (r-t)"
Comment: D is not normalized in ticks. r and t are.

[Qin]:It doesn't matter, adding them together implies there is implicit uni=
t conversion for D (from ms to ticks).

-[Page 7], Section 4.1, Suggestion for consistency:
"JB Metrics Block"---->"Jitter Block (JB) Metrics Block"

[Qin]: Okay, but it should be s/JB Metrics Blocks/Jitter Buffer(JB) Metrics=
 BLock
-[Page 8], 3 lines before last, "the time spend"--typo-->"the time spent"

[Qin]: Okay.

-[Page 9], line 9, missing "." before "In simple":
"It is calculated based on the time spent in the jitter buffer for the earl=
iest arriving packet In simple..."


[Qin]: Okay.
-[Page 16], Section 10.2 Reference [QMB] does not point to latest version.


[Qin]: Okay.
Best Regards,
Meral

---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_B8F9A780D330094D99AF023C5877DABA43B3E9BEnkgeml501mbschi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.Char
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:SimSun;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,</span> Meral:<o:p>=
</o:p></p>
<p class=3D"MsoNormal">Thanks for your valuable review, see my reply inline=
 below.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards!<o:p></o:p></p>
<p class=3D"MsoNormal">-Qin<span style=3D"color:#1F497D"><o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Meral Sh=
irazipour [mailto:meral.shirazipour@ericsson.com]
<br>
<b>Sent:</b> Saturday, June 01, 2013 4:14 AM<br>
<b>To:</b> draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org; gen-art@ietf.o=
rg<br>
<b>Subject:</b> Gen-ART Last Call review of draft-ietf-xrblock-rtcp-xr-jb-1=
1<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> &nbsp;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-xrblock-rtcp-xr-jb-11<o:p></o:p=
></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-05-31<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-05-31<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Standa=
rd RFC but I do have some comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 3], Section 1.4, Suggestion for clarity:<o:p>=
</o:p></p>
<p class=3D"MsoNormal">Old:&quot;These metrics are used to report how the j=
itter buffer at the receiving end of RTP stream behaves
<o:p></o:p></p>
<p class=3D"MsoNormal">as a result of jitter in the network and are applica=
ble to a range of RTP applications.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">New:&quot;These metrics are used to report how the j=
itter buffer at the receiving end of RTP stream behaves
<o:p></o:p></p>
<p class=3D"MsoNormal">as a result of jitter in the network; and they are a=
pplicable to a range of RTP applications.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">-[Page 5], Section 3, paragraph 5, Suggestion for co=
nsistency:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;The Jitter Buffer&quot;----&gt;&quot;The jitte=
r buffer&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 5], last sentence, Suggestion for clarity:<o:=
p></o:p></p>
<p class=3D"MsoNormal">&quot;Assume that both are normalized in ticks.&quot=
;-----&gt;<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;Assume that both are normalized in ticks (ther=
e are 10 000 ticks in a millisecond).<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 6], point (iii), Suggestion for clarity:<o:p>=
</o:p></p>
<p class=3D"MsoNormal">&quot;If r =3D t&quot; --suggestion--&gt; &quot;If r=
 =3D=3D t&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">-[Page 6], point (iv), Possible=
 inconsistance:<o:p></o:p></span></p>
<p class=3D"MsoNormal">&quot;Delay playout of packet by D &#43; (r-t)&quot;=
<o:p></o:p></p>
<p class=3D"MsoNormal">Comment: D is not normalized in ticks. r and t are. =
<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]:It doesn&#8217;t=
 matter, adding them together implies there is implicit unit conversion for=
 D (from ms to ticks).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 7], Section 4.1, Suggestion for consistency:<=
o:p></o:p></p>
<p class=3D"MsoNormal">&quot;JB Metrics Block&quot;----&gt;&quot;Jitter Blo=
ck (JB) Metrics Block&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay, but it sh=
ould be s/JB Metrics Blocks/Jitter Buffer(JB) Metrics BLock<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal">-[Page 8], 3 lines before last, &quot;the time spend=
&quot;--typo--&gt;&quot;the time spent&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">-[Page 9], line 9, missing &quot;.&quot; before &quo=
t;In simple&quot;:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;It is calculated based on the time spent in th=
e jitter buffer for the earliest arriving packet In simple...&quot;<o:p></o=
:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay.</span><o:=
p></o:p></p>
<p class=3D"MsoNormal">-[Page 16], Section 10.2 Reference [QMB] does not po=
int to latest version.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Qin]: Okay.</span><o:=
p></o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_B8F9A780D330094D99AF023C5877DABA43B3E9BEnkgeml501mbschi_--

From ron.even.tlv@gmail.com  Mon Jun  3 16:36:45 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95F4121E80BC; Mon,  3 Jun 2013 16:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=0.374,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDDCUOeFSCk9; Mon,  3 Jun 2013 16:36:31 -0700 (PDT)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id E3D3B21E8084; Mon,  3 Jun 2013 16:27:21 -0700 (PDT)
Received: by mail-ea0-f171.google.com with SMTP id m14so1357626eaj.2 for <multiple recipients>; Mon, 03 Jun 2013 16:27:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=+dw+/0rEAOgmZOjiNqe9xKF7OccO5uSxv9hXkYO+wPw=; b=TrElih34RBk9LJj58N+1Ml8+606WQDTUZLLtjhbEV1hADfuVpxhJLpwbknmF0wDcBh CT+F1jZjhGjAqmzM1hUX3sZdpaaPBZFD81odTis6S/pYljWquhiBxhF2cX27YBYW7AE/ l56gOSYj4xX4PFU5c7jU62RgDFaOBmJoEQ8ep/X++tbG0zhhF6eqPM9lbE78w5g0sctb 30DzKZQC82DyLglEEbUkLWwnoftRi8ZA/ZbM/aWrcKrJzpZ72lkA91ZCYpfFtRzheGOf 3d2gvO3l3ZoZZiQpJL6B2ORIHxQl0j7s2woBQqk4VSnWknfSqxagkIWtATqXfy05EDah 1JSA==
X-Received: by 10.14.179.68 with SMTP id g44mr24650241eem.18.1370302040836; Mon, 03 Jun 2013 16:27:20 -0700 (PDT)
Received: from RoniE ([109.64.225.31]) by mx.google.com with ESMTPSA id c5sm72183724eeu.8.2013.06.03.16.27.18 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 03 Jun 2013 16:27:20 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <Simo.Veikkolainen@nokia.com>, <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com>
In-Reply-To: <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com>
Date: Tue, 4 Jun 2013 02:26:05 +0300
Message-ID: <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0271_01CE60CA.DF7D1560"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD2ctd9kjZ9dlpMJt4mULENla+sLwGDWn0omshh2mA=
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2013 23:36:45 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0271_01CE60CA.DF7D1560
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Simo,

For the PSTN case the document explain how to construct the m-line PSTN is
used based on the ccap using port 9. This is not specified for the ATM case.
So if it is not mentioned it should be clear that using  ccap for ATM is not
specified and need another document

Roni

 

From: Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com] 
Sent: 31 May, 2013 1:14 PM
To: ron.even.tlv@gmail.com;
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

 

Hello Roni,

Please see my answer below prefixed with [SV].

 

From: ext Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: 29. toukokuuta 2013 21:13
To: draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013-5-29

IETF LC End Date: 2013-6-4

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

1.       I can understand from the draft that when you have IP and PSTN
nettype it is requires that the ccap will be for the PSTN. What happens if
you want to have the ccap nettype as ATM to be used with IP in the c=

 

[SV] If either endpoint does not support ATM, the "c=" line with the ATM
address would not get used (either it is not offered, or the Answerer
removes that from the SDP configurations). In case both endpoints actually
support and want to use ATM as alternative to IP based bearer, the
conventions in RFC3108 would need to be followed when crafting the SDP
configurations. That said, I haven't taken a detailed look at RFC3108 to see
if the ATM based media can be negotiated using the SDP Capability
Negotiation framework and its current extensions.

 

Simo

 

Nits/editorial comments:

 


------=_NextPart_000_0271_01CE60CA.DF7D1560
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Simo,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>For the PSTN case the =
document explain how to construct the m-line PSTN is used based on the =
ccap using port 9. This is not specified for the ATM case. So if it is =
not mentioned it should be clear that using &nbsp;ccap for ATM is not =
specified and need another document<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com] =
<br><b>Sent:</b> 31 May, 2013 1:14 PM<br><b>To:</b> =
ron.even.tlv@gmail.com; =
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org<br><b>Cc:</b>=
 ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC =
review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05<o:p></o:p></span></p></div></=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hello Roni,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Please see my answer =
below prefixed with [SV].<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><a =
name=3D"_____replyseparator"></a><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> 29. toukokuuta 2013 21:13<br><b>To:</b> <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05<o:p></o:p></span></p></div></=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;5&#8211;29<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-6&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I can =
understand from the draft that when you have IP and PSTN nettype it is =
requires that the ccap will be for the PSTN. What happens if you want to =
have the ccap nettype as ATM to be used with IP in the =
c=3D<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[SV] If either endpoint does not support ATM, the &#8220;c=3D&#8221; =
line with the ATM address would not get used (either it is not offered, =
or the Answerer removes that from the SDP configurations). In case both =
endpoints actually support and want to use ATM as alternative to IP =
based bearer, the conventions in RFC3108 would need to be followed when =
crafting the SDP configurations. That said, I haven&#8217;t taken a =
detailed look at RFC3108 to see if the ATM based media can be negotiated =
using the SDP Capability Negotiation framework and its current =
extensions.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Simo<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0271_01CE60CA.DF7D1560--


From Simo.Veikkolainen@nokia.com  Tue Jun  4 00:43:11 2013
Return-Path: <Simo.Veikkolainen@nokia.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD60621F9B37; Tue,  4 Jun 2013 00:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bXTjU8Hhed4g; Tue,  4 Jun 2013 00:42:56 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2351D11E80E7; Mon,  3 Jun 2013 23:47:19 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (in-mx.nokia.com [10.160.244.22]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r546lE4A008845; Tue, 4 Jun 2013 09:47:14 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.26]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 4 Jun 2013 09:47:27 +0300
Received: from 008-AM1MPN1-025.mgdnok.nokia.com ([169.254.5.171]) by 008-AM1MMR1-010.mgdnok.nokia.com ([65.54.30.26]) with mapi id 14.02.0328.011; Tue, 4 Jun 2013 06:48:24 +0000
From: <Simo.Veikkolainen@nokia.com>
To: <ron.even.tlv@gmail.com>, <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Thread-Index: Ac5cmCWECo5bIU14RKqGyok1y70zYABS86TwALNw8IAAD1Rg4A==
Date: Tue, 4 Jun 2013 06:48:24 +0000
Message-ID: <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com> <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com>
In-Reply-To: <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-version: 3.5.9.3
x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None;
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IieUVVR+P20VDCzpg3HHXu3iIt34TClchC1lFMW65RFpQIjYqffJgrmfD1cpNgGbjtK8fB7f+0feePD/3lFuEnnkEez1dWv4zZaxFseCBqz9vmPplcQguUY4aymB6E2FlXKMnVmqGMRGGOklYWAKTXB+mqjHKxFjyTSbRvCSq9ZSlLCqmfs3bpHtpJ6E8hoghaVDC0dozB9AWOU7rGBrPnu/tUoAuQ7hJg97r0tWFsJFeIUou2s76WJFRrdIzzPW2JgXZ1J8xbVDQ7xySsJFM8s=
x-originating-ip: [172.21.81.94]
Content-Type: multipart/alternative; boundary="_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 04 Jun 2013 06:47:27.0982 (UTC) FILETIME=[60EB80E0:01CE60EF]
X-Nokia-AV: Clean
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2013 07:43:11 -0000

--_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Would adding a statement like this at the end of 3.1.2 address your concern=
:
                Exceptions for other network types, such as for  the "ATM" =
network type defined in [RFC3108], require additional specifications.
Regards,
Simo

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: 4. kes=E4kuuta 2013 2:26
To: Veikkolainen Simo (Nokia-CTO/Espoo); draft-ietf-mmusic-sdp-miscellaneou=
s-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-=
05

Hi Simo,
For the PSTN case the document explain how to construct the m-line PSTN is =
used based on the ccap using port 9. This is not specified for the ATM case=
. So if it is not mentioned it should be clear that using  ccap for ATM is =
not specified and need another document
Roni

From: Simo.Veikkolainen@nokia.com<mailto:Simo.Veikkolainen@nokia.com> [mail=
to:Simo.Veikkolainen@nokia.com]
Sent: 31 May, 2013 1:14 PM
To: ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>; draft-ietf-mmusi=
c-sdp-miscellaneous-caps.all@tools.ietf.org<mailto:draft-ietf-mmusic-sdp-mi=
scellaneous-caps.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-=
05

Hello Roni,
Please see my answer below prefixed with [SV].

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: 29. toukokuuta 2013 21:13
To: draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org<mailto:draf=
t-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013-5-29

IETF LC End Date: 2013-6-4

IESG Telechat date:



Summary: This draft is almost ready for publication as Standard track RFC.





Major issues:



Minor issues:

1.       I can understand from the draft that when you have IP and PSTN net=
type it is requires that the ccap will be for the PSTN. What happens if you=
 want to have the ccap nettype as ATM to be used with IP in the c=3D



[SV] If either endpoint does not support ATM, the "c=3D" line with the ATM =
address would not get used (either it is not offered, or the Answerer remov=
es that from the SDP configurations). In case both endpoints actually suppo=
rt and want to use ATM as alternative to IP based bearer, the conventions i=
n RFC3108 would need to be followed when crafting the SDP configurations. T=
hat said, I haven't taken a detailed look at RFC3108 to see if the ATM base=
d media can be negotiated using the SDP Capability Negotiation framework an=
d its current extensions.



Simo


Nits/editorial comments:


--_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Would adding a stateme=
nt like this at the end of 3.1.2 address your concern:<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Except=
ions for other network types, such as for &nbsp;the &quot;ATM&quot; network=
 type defined in [RFC3108], require additional specifications.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Simo<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<a name=3D"_____replyseparator"></a><b><span style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span st=
yle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;"> ext Roni Even [mailto:ron.even.tlv@gmail.com]
<br>
<b>Sent:</b> 4. kes=E4kuuta 2013 2:26<br>
<b>To:</b> Veikkolainen Simo (Nokia-CTO/Espoo); draft-ietf-mmusic-sdp-misce=
llaneous-caps.all@tools.ietf.org<br>
<b>Cc:</b> ietf@ietf.org; gen-art@ietf.org<br>
<b>Subject:</b> RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneou=
s-caps-05<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Simo,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">For the PSTN case the =
document explain how to construct the m-line PSTN is used based on the ccap=
 using port 9. This is not specified for the ATM case. So if it is not ment=
ioned it should be clear that using
 &nbsp;ccap for ATM is not specified and need another document<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Roni<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;font-family:=
&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:Simo.Veikkolainen@nokia.com">Simo.Veikkolainen@nokia.com<=
/a> [<a href=3D"mailto:Simo.Veikkolainen@nokia.com">mailto:Simo.Veikkolaine=
n@nokia.com</a>]
<br>
<b>Sent:</b> 31 May, 2013 1:14 PM<br>
<b>To:</b> <a href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com=
</a>; <a href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.=
ietf.org">
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"m=
ailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Subject:</b> RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneou=
s-caps-05<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello Roni,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see my answer b=
elow prefixed with [SV].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;font-family:=
&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ext Roni Even [<a href=3D"mailt=
o:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]
<br>
<b>Sent:</b> 29. toukokuuta 2013 21:13<br>
<b>To:</b> <a href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@t=
ools.ietf.org">
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"m=
ailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Subject:</b> Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-ca=
ps-05<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>=
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Document:
</span><span style=3D"font-family:&quot;Courier New&quot;">draft-ietf-mmusi=
c-sdp-miscellaneous-caps-05</span><span style=3D"font-size:11.0pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Reviewer: Roni Even<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Review Date:2013&#8211;5&#8211;29<o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">IETF LC End Date: 2013-6&#8211;4<o:p=
></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">IESG Telechat date:
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Summary: This draft is almost ready =
for publication as Standard track RFC.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Major issues:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Minor issues:<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">1.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;">I can understand from the draft=
 that when you have IP and PSTN nettype it is requires that the ccap will b=
e for the PSTN. What happens if you want to have the ccap
 nettype as ATM to be used with IP in the c=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SV] If either endpoin=
t does not support ATM, the &#8220;c=3D&#8221; line with the ATM address wo=
uld not get used (either it is not offered, or the Answerer removes that
 from the SDP configurations). In case both endpoints actually support and =
want to use ATM as alternative to IP based bearer, the conventions in RFC31=
08 would need to be followed when crafting the SDP configurations. That sai=
d, I haven&#8217;t taken a detailed look
 at RFC3108 to see if the ATM based media can be negotiated using the SDP C=
apability Negotiation framework and its current extensions.<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Simo<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_D09DAE6B636851459F7575D146EFB54B2406EA58008AM1MPN1025mg_--

From ron.even.tlv@gmail.com  Tue Jun  4 21:57:35 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD4D121F9371; Tue,  4 Jun 2013 21:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BzZM1h2j0c2L; Tue,  4 Jun 2013 21:57:33 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id BFEF721F93F8; Tue,  4 Jun 2013 21:57:32 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id hn14so4419258wib.2 for <multiple recipients>; Tue, 04 Jun 2013 21:57:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=DN7HQiaS+cJ6gFfXZNjWwjPAjjmZKuDdC//HQjp+Fjg=; b=Ct+90WIIhjARVq40FyI97CIL5kg7bAWd0bekEBRik57qJhrDNyLUsrXnlzmABNgBWo Qh1rjdHJRJCaQ21dfV19DqkyOUSH1E4YWls0tLgvwytXimHqcUJj/SK4VkPAYHUfjVMN M5iPJDdBknWkrDo9Y7w1+3ZRvYUVlYgfc2f2J8pQtHDLdDwSXbVvFEudPuuXhh1R6b2I a5e0yzTKnwDsypulokWGDIChEjyGtJkGkByjZoMR0TM46t1iOeVKw0NSDiHNdkXstdVa 9NySu7tRk8V+sPwT0tHpz0JwEdtGj90l3eKNpfAZiAnGaCg/0PCOjSc+v2hkUPopL7pc TiCQ==
X-Received: by 10.180.198.140 with SMTP id jc12mr4468790wic.53.1370408251521;  Tue, 04 Jun 2013 21:57:31 -0700 (PDT)
Received: from RoniE ([109.64.225.31]) by mx.google.com with ESMTPSA id b11sm7447741wiv.10.2013.06.04.21.57.29 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 04 Jun 2013 21:57:30 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <Simo.Veikkolainen@nokia.com>, <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com> <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com>
In-Reply-To: <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com>
Date: Wed, 5 Jun 2013 07:56:16 +0300
Message-ID: <031901ce61a9$04af7ce0$0e0e76a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_031A_01CE61C2.29FE1470"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD2ctd9kjZ9dlpMJt4mULENla+sLwGDWn0oAPcibgECiupmU5quQQiQ
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 04:57:35 -0000

This is a multipart message in MIME format.

------=_NextPart_000_031A_01CE61C2.29FE1470
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Simo,

This will be OK

Roni

=20

From: Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com]=20
Sent: 04 June, 2013 9:48 AM
To: ron.even.tlv@gmail.com;
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

Would adding a statement like this at the end of 3.1.2 address your =
concern:

                Exceptions for other network types, such as for  the =
"ATM"
network type defined in [RFC3108], require additional specifications.

Regards,

Simo

=20

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: 4. kes=E4kuuta 2013 2:26
To: Veikkolainen Simo (Nokia-CTO/Espoo);
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

Hi Simo,

For the PSTN case the document explain how to construct the m-line PSTN =
is
used based on the ccap using port 9. This is not specified for the ATM =
case.
So if it is not mentioned it should be clear that using  ccap for ATM is =
not
specified and need another document

Roni

=20

From: Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com]=20
Sent: 31 May, 2013 1:14 PM
To: ron.even.tlv@gmail.com;
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

Hello Roni,

Please see my answer below prefixed with [SV].

=20

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: 29. toukokuuta 2013 21:13
To: draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05

=20

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments =
you
may receive.

Document: draft-ietf-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013=965=9629

IETF LC End Date: 2013-6=964

IESG Telechat date:=20

=20

Summary: This draft is almost ready for publication as Standard track =
RFC.

=20

=20

Major issues:

=20

Minor issues:

1.  I can understand from the draft that when you have IP and PSTN =
nettype
it is requires that the ccap will be for the PSTN. What happens if you =
want
to have the ccap nettype as ATM to be used with IP in the c=3D

=20

[SV] If either endpoint does not support ATM, the =93c=3D=94 line with =
the ATM
address would not get used (either it is not offered, or the Answerer
removes that from the SDP configurations). In case both endpoints =
actually
support and want to use ATM as alternative to IP based bearer, the
conventions in RFC3108 would need to be followed when crafting the SDP
configurations. That said, I haven=92t taken a detailed look at RFC3108 =
to see
if the ATM based media can be negotiated using the SDP Capability
Negotiation framework and its current extensions.

=20

Simo

=20

Nits/editorial comments:

=20


------=_NextPart_000_031A_01CE61C2.29FE1470
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Simo,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>This will be =
OK<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Simo.Veikkolainen@nokia.com [mailto:Simo.Veikkolainen@nokia.com] =
<br><b>Sent:</b> 04 June, 2013 9:48 AM<br><b>To:</b> =
ron.even.tlv@gmail.com; =
draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org<br><b>Cc:</b>=
 ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC =
review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05<o:p></o:p></span></p></div></=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Would adding a statement like this at the end of =
3.1.2 address your concern:</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exceptions for other network =
types, such as for &nbsp;the &quot;ATM&quot; network type defined in =
[RFC3108], require additional specifications.</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Regards,</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Simo</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><a =
name=3D"_____replyseparator"></a><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> 4. kes=E4kuuta 2013 2:26<br><b>To:</b> Veikkolainen =
Simo (Nokia-CTO/Espoo); <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p></div></=
div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Simo,</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>For the PSTN case the =
document explain how to construct the m-line PSTN is used based on the =
ccap using port 9. This is not specified for the ATM case. So if it is =
not mentioned it should be clear that using &nbsp;ccap for ATM is not =
specified and need another document</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a =
href=3D"mailto:Simo.Veikkolainen@nokia.com">Simo.Veikkolainen@nokia.com</=
a> [<a =
href=3D"mailto:Simo.Veikkolainen@nokia.com">mailto:Simo.Veikkolainen@noki=
a.com</a>] <br><b>Sent:</b> 31 May, 2013 1:14 PM<br><b>To:</b> <a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>; <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p></div></=
div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hello Roni,</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Please see my answer =
below prefixed with [SV].</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> 29. toukokuuta 2013 21:13<br><b>To:</b> <a =
href=3D"mailto:draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.or=
g">draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org</a><br><b>=
Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
Gen-ART LC review of =
draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p></div></=
div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mmusic-sdp-miscellaneous-caps-05</span><o:p></o:p></p><p=
 class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;5&#8211;29</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-6&#8211;4</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: </span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I can =
understand from the draft that when you have IP and PSTN nettype it is =
requires that the ccap will be for the PSTN. What happens if you want to =
have the ccap nettype as ATM to be used with IP in the =
c=3D</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[SV] If either endpoint does not support ATM, the &#8220;c=3D&#8221; =
line with the ATM address would not get used (either it is not offered, =
or the Answerer removes that from the SDP configurations). In case both =
endpoints actually support and want to use ATM as alternative to IP =
based bearer, the conventions in RFC3108 would need to be followed when =
crafting the SDP configurations. That said, I haven&#8217;t taken a =
detailed look at RFC3108 to see if the ATM based media can be negotiated =
using the SDP Capability Negotiation framework and its current =
extensions.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Simo</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div></div></body></html>
------=_NextPart_000_031A_01CE61C2.29FE1470--


From rjsparks@nostrum.com  Wed Jun  5 14:56:26 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00DBC21F9193; Wed,  5 Jun 2013 14:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0c5i+IL92bII; Wed,  5 Jun 2013 14:56:24 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4170021F8B35; Wed,  5 Jun 2013 14:56:24 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-071-187.mycingular.net [166.147.71.187]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r55LuLOW065539 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Wed, 5 Jun 2013 16:56:22 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <51AFB3FF.7000009@nostrum.com>
Date: Wed, 05 Jun 2013 16:56:15 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, mmusic@ietf.org, draft-ietf-mmusic-rfc2326bis@tools.ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 166.147.71.187 is authenticated by a trusted mechanism)
Subject: [Gen-art] Gen-art last call review: draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 21:56:26 -0000

I am the assigned Gen-ART reviewer for this draft. For background on 
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments 
you may receive.

Document: draft-ietf-mmusic-rfc2326bis-34
Reviewer: Robert Sparks
Review Date: 05-Jun-2013
IETF LC End Date: 04-Jun-2013
IESG Telechat date: not yet on a telechat

Summary: This draft is on the right track but has open issues, described 
in the review.

I have not reviewed this document at the level of detail I prefer for 
Gen-art reviews, but have tried to be thorough in the sections I have 
reviewed.

In particular,
I didn't verify the tables and the text agree
I didn't carefully check the ABNF
I haven't thought about possible edge cases and race conditions as much 
as I would have liked
I didn't closely review the security mechanisms in section 19 or the 
specialized MIKEY keying mechanism in the appendix - both need careful 
review from security experts.

One observation I would like to make before calling out issues and nits:

The document is very long, and the structure is unusual - much of the 
definition of the protocol itself is in the appendices. You are missing 
an opportunity to make this document much shorter (thereby likely 
increasing its effectiveness). Much of the jump in from RFC2326 was 
importing the description of headers and responses from HTTP, tailoring 
them to RTSP. That was a good exercise in that it highlights some issues 
that would otherwise be non-obvious (and raises a few questions below). 
But you followed the style from HTTP perhaps too closely - much shorter 
descriptions without examples might have done the job better. Overall, 
separating exposition and examples from the protocol definition would 
make it much easier for an implementer to find the definition of the 
protocol, and use the document as a reference when diagnosing a failure 
to interoperate.

Major Issues

I'm not seeing what instructs an RTSP element on how to find the server 
it would try to open a connection to given an rtsp or rtsps URI? Are you 
assuming it would be doing A or AAAA DNS lookups? Should this protocol 
use NAPTR/SRV? The document should be explicit. On a related note, (and 
maybe I missed this), but where do you talk about what an element should 
check in the server's certificate when connecting over TLS? Are you 
assuming a common name match? Or are you expecting some SubjectAltName 
processing?

The document should say more about when connection reuse is appropriate, 
particularly when the connections happened because of an rtsps uri. Two 
different names might resolve to the same IP address - reusing a 
connection formed when looking at the first name (and verifying the 
server's cert) is dangerous. A new connection needs to be formed (and 
verified) instead.

The text talks about the option to queue S->C requests if there isn't a 
connection to the client available. Ostensibly, this means the request 
can go down some future connection. It's not clear how the server can 
tell the right client connected. In particular, when using rtsps, how do 
you prevent a malicious client from getting such a queued message that 
wasn't meant for him?

Given that the text talks about queuing S-C requests, it should 
explicitly call out whether a server can queue a response if the 
connection the associated request arrived on is no longer available. I 
think what you want to say is that such a response must not be queued, 
and must be dropped.

There are several places in the text that talk about using a 503 
response with a Retry-After header to push back on traffic from an 
element (the first is section 10.7).
* It's not clear what the subject of a 503 is. Is it intended to be 
scoped to requests to the resource in the RURI of the associated 
request? Is it intended to be scoped to the domain in that resource? Or 
is it, like in SIP, intended to be scoped to the server issuing the 
response, independent of what the RURI contained?
* If the intent is that the 503 talks about the server, then you should 
clarify that a proxy doesn't simply forward 503 responses (after 
rewriting CSeqs), and should probably have a response of its own. 
Otherwise, clients that might be talking to two different servers 
through one proxy would lose access to both of them when one of the 
servers 503ed.

Section 4.9.1 lists values the Seek-Style header can take, but 18.45 
lists a completely different set (which most of the rest of the document 
uses). Should 4.9.1 be changed to use the values in 18.45? Are the right 
strings being used in sections 13.4.4 through 13.4.6? Those appear to be 
using strings from 4.9.1.

The document will not stand if you delete some of the appendices. They 
aren't supplementary material. Please consider restructuring the 
normative sections back into the main document, or clearly identifying 
which ones define protocol and which are background information.

Section 15 talks about a "transparent' proxy, but there is no 
description in this document of what protocol such a thing should 
follow. What bad thing happens if you remove all mention of 
"transparent" proxies from the document? As far as I can tell, that 
won't affect the protocol definition at all.

The list of steps for establishing an SRTP cryptographic context in 
C.1.4.1 says "This specification does not specify an explicit method for 
indicating this SRTP cryptographic context establishment method, but 
future specifications may." in the context of looking at the SDP. SDP 
_has_ methods of indicating what keying mechanism is used with SRTP - 
are you talking about something different? Why doesn't this section say 
something like "the use of SRTP with RTSP is only defined with MIKEY 
with keys established as defined in this section. Future documents may 
talk about how an RTSP implementation might treat SDP that indicates 
some other key mechanism be used"? Could you provide an example in the 
document of an RTSP message carrying SDP reflecting the use of SRTP as 
defined in this document?


Minor Issues

The document uses the notion of a "control connection" (it appears first 
in section 2.5) without defining what that is, or what kind of 
connections you might have that aren't control connections.

The update to the registration of the rtsp and rtsps schema call out 
that there are changes that can result in interoperability issues. It 
doesn't say what the issues are, or who might encounter them. I can 
infer that the point is that there might be problems if a URI following 
this updated registration were to be processed by an RTSP 1.0 
implementation (or any other application that relied on the previous 
definition). It would be better to say that explicitly, and talk about 
how a previous implementation is likely to act when presented with a URI 
that exercised these new changes. (It's not clear to me that all of the 
thread at www.ietf.org—msg01567.html 
<http://www.ietf.org/mail-archive/web/uri-review/current/msg01567.html> 
concluded - I see how the fragments question ended, but what about 
things like the addition of IPV6 literals? In particular, I'm not 
finding a response where Ted Hardie agreed that the potential for 
interoperability failure had been adequately addressed).


I think you've said something different than you mean in 5.4 item 1. I 
think you mean to say that an RTSP implementation would ignore any body 
that happened to come in message that MUST NOT contain one. What you've 
said is that the part of the parser that's doing framing has to stop 
framing at the end of the headers, and that such an errant body would be 
parsed as a separate message. As written this would keep someone from 
using an Internet Message Format parser since it would have to ignore 
any Content-Length that might have appeared, even though it wasn't 
supposed to.

In section 10.4, it looks like a server can keep an RTSP transaction 
pending forever if it sends 100 responses often enough. I assume the 
client's recourse if it doesn't want to remain involved is to close the 
connection. If that's right, it's worth calling it out explicitly in 
this section.

Somewhere, probably in section 15.2, you should be explicit that a proxy 
that is multiplexing requests MUST keep the requests in the same order 
as they are folded together. You can infer that, or things simply break, 
but saying it explicitly would be better.

Both GET_PARAMETER and SET_PARAMETER are listed as keep-alive methods in 
10.5, but the note in section 13 on table 7 only uses that as a reason 
for requiring SET_PARAMETER. Why doesn't it also apply to GET_PARAMETER? 
And why is this only required at servers? "Required" in this section 
means Mandatory to Implement, I think. If that's right, it should be 
made explicit. If that's not right, what does it mean?

Section 13.8 makes a good argument for always putting parameters to be 
retrieved in a body. Why are you keeping the complexity of also allowing 
them in headers?

Section 13.10: "That should not provide any benefit." is not clear - can 
you expand it a little?

In Section 13.10 you talk about clients _sending_ media (search for 
"send or receive media"). Do you mean anything more than possibly RTCP? 
Can you make that clear in the section?

Section 15.2's second paragraph appears to be the only place the proxy 
rewriting of CSeq in order to multiplex requests is defined, and it is 
very loose. It would be easy for a reader to fail to recognize this as 
an interoperability requirement. Please consider expanding how this is 
specified when addressing the comment about above about keeping requests 
in relative order when multiplexing.

You follow the principle of saying a client should treat a response with 
an unknown response code, the same as it would treat the x00 of that 
class (e.g. 400 for an unknown 4xx). However, you do not define what a 
response code of 300 means. How is a client supposed to handle an 
unknown 3xx response?

As written, a client and server can use HTTP Basic authentication over 
TCP that is not protected with TLS. Consider restricting it's use to TLS 
only. Are you sure you don't need to say anything RTSP specific about 
DIGEST computations (I don't think you need to go as far as SIP did 
talking about DIGEST, but I'm surprised you haven't run into issues 
relying only on 2617 literally.


How does 411 Length Required for this protocol make sense? Given that 
you've restricted the protocol to TCP and require the Content-Length 
header to be present if there is a body, in what circumstance would a 
server need to send a 411?


Section 18.19 requires senders to increment CSeq by 1. We have a 
reliable transport with no request retransmission, so there should never 
be gaps at the receiver. Should the receiver check and react some way if 
there are gaps? I think you should explicitly tell them not to even 
look. If you agree, why is incrementing by one important as long as you 
are always strictly increasing?

You call out several places where RTCP is essential to allow RTSP using 
RTP to work correctly, yet section C.1.2 sets up conditions where RTCP 
MUST NOT be sent. Why are you allowing those instead of treating the 
conditions you describe as errors?


Nits


The definition of Message still talks about connectionless transports

22.14 says "These URI schemes are defined in existing registries which 
are not created by RTSP." Should it say that they are _registered_ 
rather than defined, and "not created by this document" instead of by 
RTSP? In section 4.2 in the paragraph discussing ports 554 and 322, why 
is the language different for rtsp and rtsps? "MUST be used" vs "is 
registered and MUST be assumed"?

Consider a reference in 4.4 to where SMPTE 30 drop is defined, 
particularly for where the 1/100th frame measurement comes from.

Section 4.5 introduces NPT as indicating "the absolute position" and 
then defines something that can carry a point or a range. I suggest 
adjusting the first sentence to allow for a range.

Section 4.9.1's description of Conditional Random Access contains some 
ambiguity. It would help be more explicit. I think it's trying to say 
"would move the client's play point further away from the requested play 
point than it's play point currently is."?

Section 5 : what do you mean by "tricky" switching?

Section 7: consider octets instead of bytes

Section 10.3: what is "take appropriate action" trying to say?

The document mixes using "3rr" and "3xx" to talk about redirect 
responses. Why are there two ways to say the same thing?

(Total nit, but) The examples show dates in 1997, when there could be no 
RTSP/2.0. Are there other aspects of the examples that might not have 
been updated?

Is "will need to use" at the bottom of page 85 in section 13.5.2 trying 
to say something that should be said with 2119?

Consider saying that a client must not put a Terminate-Reason in a C->S 
Teardown request, or tweak the definition of Terminate-Reason to discuss 
client use and the possibility of C->S specific values.

These two sentences in 13.7.1 are particularly hard to parse together: 
"The time period is considered extended when it is 10 times the Session 
Timeout period. Consideration of the application of the server and its 
content should be performed when configuring what is considered as 
extended period of time." I suspect they were not written at the same 
time? Can you simplify what they are trying to say, noting that the 
suggested "10 times" is a default, and that if you want to change that 
default, you need to consider the context?

Section 14: "Interleaved binary data SHOULD only be used if RTSP is 
carried over TCP". Is this leftover from when UDP was an option?

(small nit) Section 14, you mention an ASCII dollar sign - maybe you 
should just say an octet with value 0x24?

It's not clear how far up to go with "upper-layer protocol headers" in 
section 14, given that you are trying to speak generally about carrying 
things in interleaved data. Your example for RTP may cover the only case 
that matters. Consider speaking more normatively (instead of with an 
example) for RTP and provide some guidelines about where to cut the 
prefixes for other things you might want to carry (lest you end up with 
the v6 headers too when tunneling some new foo protocol?)

In section 17, you say "Status codes that have the same meaning are not 
repeated here." But you did repeat them (see 200 OK). Should that 
sentence be deleted?

304 (section 17.3.4) probably should have been a different class 
response, maybe even a 2xx. The text does call it out as "unusual" for 
the 3xx, but it would be better to say why this ended up in this 
response class.

I might be confused, but I'm not sure the redirection semantics defined 
in this document lead to the "black hole" case discussed in 17.4.14. If 
I'm confused, could you send me an example of such a redirection black 
hole happening?

Section 18.11 first paragraph should be split into two sentences.

Is "MUST be transported over TCP" in C.2.1 stale now that no 
connectionless transport is defined?

The end of Appendix G still implies that CSeq was primarily for 
unreliable transports. There are other places that out and point to 
proxy multiplexing. All of them should acknowledge that CSeq is 
necessary for associating responses with requests.


From david.black@emc.com  Wed Jun  5 15:14:04 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E19B21F9651; Wed,  5 Jun 2013 15:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WwFJsEJoAZ2l; Wed,  5 Jun 2013 15:13:59 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2D421F9649; Wed,  5 Jun 2013 15:13:59 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r55MDRjB001272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jun 2013 18:13:30 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Wed, 5 Jun 2013 18:13:08 -0400
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r55MD7QM029499; Wed, 5 Jun 2013 18:13:07 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Wed, 5 Jun 2013 18:13:06 -0400
From: "Black, David" <david.black@emc.com>
To: "d3e3e3@gmail.com" <d3e3e3@gmail.com>, "joe.abley@icann.org" <joe.abley@icann.org>, General Area Review Team <gen-art@ietf.org>
Date: Wed, 5 Jun 2013 18:13:06 -0400
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-02
Thread-Index: Ac5iOdqxPgeHIMhASdCnl829MYVBxw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "joelja@bogus.com" <joelja@bogus.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 22:14:04 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-eastlake-rfc5342bis-02
Reviewer: David L. Black
Review Date: June 5, 2013
IETF LC End Date: June 4, 2013

Summary:
This draft is on the right track but has open issues, described in the revi=
ew.

This draft updates the IANA registered Ethernet parameters for IETF use,
including recording values assigned for documentation.  It also makes some
minor changes to IANA procedures.

IANA should review this entire draft, not just its IANA Considerations sect=
ion;
Pearl Liang appears to have done that comprehensive review for IANA.

Major issues: None

Minor issues: One, the IANA review also found this issue.

Section 3.2 states:

	IANA will assign "00-00-0E-00-42" as the protocol number under the=09
	IANA OUI to be used for documentation purposes.

IANA has not made this assignment, but this assignment request is not
recorded in the IANA Considerations section where IANA actions are
requested and recorded by IANA after they have been performed.  This
assignment needs to be added to the IANA Considerations section;
see item 5 in the IANA review.

Nits/editorial comments:

Section 1: This document uses an "IESG Ratification" process for some
assignments.  This is not the same process as the "IESG Approval" process
defined in RFC 5226.  As those names could be confused by a casual reader
who is not strongly familiar with IANA processes, I suggest adding a
statement that the "IESG Ratification" process is defined in this document
and is not the same as the "IESG Approval" process in RFC 5226.  This could
be added after the sentence that cites RFC 5226.

Section 1.4: It would be helpful to point out that there is no OUI assigned
for documentation purposes, but there are identifiers based on the IANA OUI
that have been assigned for documentation purposes.

In general, the use of the acronym IAB for Individual Address Block is
unfortunate, but unavoidable, and this is clearly pointed out in the
definition of the IAB acronym in section 1.2.  Nothing can or should be
done about this.

idnits 2.12.17 did not find any nits.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From d3e3e3@gmail.com  Wed Jun  5 15:25:22 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B08221F853A; Wed,  5 Jun 2013 15:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Edrwoalnjn9; Wed,  5 Jun 2013 15:25:21 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id DE67921F842E; Wed,  5 Jun 2013 15:25:20 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n12so1640009oag.3 for <multiple recipients>; Wed, 05 Jun 2013 15:24:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fFcsCiyEWhgEBu8lyqjT6GbmlMMw0PoUVwa0WIWBeLU=; b=r0zgyulHGu2/cWQL2Ay1se2v4Yhi0DLC/siSE/99tEf3Smmv3dnfv8rxt69Gd+dDfI Ue3/JZC+rtXWN1j74F8MmenpnZm0vhAQ3dLgsRTncALsOVJfM1aijfUfksDft27/CPHn 0XVLmAQL+WIE/PGDyYQOatP++FJvhxjD6vE1nvZkfIgfBTgM/K+45SwxVI5zDi3DCiK1 iPiSb44z9WGtcodUOOXxscYNwUhQVqW5dRNsEZHacbep7GS5q1OwDDk/JC5R1uLwY4Iy qa1XW63Hkk+pMrF4ZELOuxeiODeeTscV4i4SfiojKgCSfQu7bfsiqkvfJ9INRPHt9n6G MVdw==
X-Received: by 10.60.79.68 with SMTP id h4mr16895188oex.39.1370471096719; Wed, 05 Jun 2013 15:24:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.12.65 with HTTP; Wed, 5 Jun 2013 15:24:36 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 5 Jun 2013 18:24:36 -0400
Message-ID: <CAF4+nEESGzBW51ARg-YbZ1ZZ8q5KXtj55Cx-musdkwrG+zOJWA@mail.gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "joelja@bogus.com" <joelja@bogus.com>, General Area Review Team <gen-art@ietf.org>, "joe.abley@icann.org" <joe.abley@icann.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 22:25:22 -0000

Hi David,

Thanks for this review. See below:

On Wed, Jun 5, 2013 at 6:13 PM, Black, David <david.black@emc.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-eastlake-rfc5342bis-02
> Reviewer: David L. Black
> Review Date: June 5, 2013
> IETF LC End Date: June 4, 2013
>
> Summary:
> This draft is on the right track but has open issues, described in the review.
>
> This draft updates the IANA registered Ethernet parameters for IETF use,
> including recording values assigned for documentation.  It also makes some
> minor changes to IANA procedures.
>
> IANA should review this entire draft, not just its IANA Considerations section;
> Pearl Liang appears to have done that comprehensive review for IANA.

Right, I'm working on a response to Pearl.

> Major issues: None
>
> Minor issues: One, the IANA review also found this issue.
>
> Section 3.2 states:
>
>         IANA will assign "00-00-0E-00-42" as the protocol number under the
>         IANA OUI to be used for documentation purposes.
>
> IANA has not made this assignment, but this assignment request is not
> recorded in the IANA Considerations section where IANA actions are
> requested and recorded by IANA after they have been performed.  This
> assignment needs to be added to the IANA Considerations section;
> see item 5 in the IANA review.

OK.

> Nits/editorial comments:
>
> Section 1: This document uses an "IESG Ratification" process for some
> assignments.  This is not the same process as the "IESG Approval" process
> defined in RFC 5226.  As those names could be confused by a casual reader
> who is not strongly familiar with IANA processes, I suggest adding a
> statement that the "IESG Ratification" process is defined in this document
> and is not the same as the "IESG Approval" process in RFC 5226.  This could
> be added after the sentence that cites RFC 5226.

OK.

> Section 1.4: It would be helpful to point out that there is no OUI assigned
> for documentation purposes, but there are identifiers based on the IANA OUI
> that have been assigned for documentation purposes.

OK.

> In general, the use of the acronym IAB for Individual Address Block is
> unfortunate, but unavoidable, and this is clearly pointed out in the
> definition of the IAB acronym in section 1.2.  Nothing can or should be
> done about this.
>
> idnits 2.12.17 did not find any nits.

I think your suggestions are all good.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------

From elwynd@folly.org.uk  Wed Jun  5 17:12:18 2013
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 033E211E80D1; Wed,  5 Jun 2013 17:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B1POAFCwdXkF; Wed,  5 Jun 2013 17:12:13 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB4521F9690; Wed,  5 Jun 2013 17:12:13 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1UkNo5-0004Jw-Vf; Thu, 06 Jun 2013 01:11:59 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Organization: Folly Consulting
Date: Thu, 06 Jun 2013 01:11:53 +0100
Message-Id: <1370477514.4596.9052.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-ACL-Warn: Blacklisted URL in message. (ietf.org) in. See http://lookup.uribl.com.
Cc: draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, IETF discussion <ietf@ietf.org>
Subject: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 00:12:18 -0000

I am an additional Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-mmusic-rfc2326bis
Reviewer: Elwyn Davies
Review Date: 5 June 2013
IETF LC End Date: 5 JUne 2013
IESG Telechat date: (if known) -

Summary:
Almost ready.  Generally this is an excellent and well written document,
particularly given its size.  There are a few minor issues to sort out
mainly at the nit level and some consistency issues to fix up.  The two
issues that I have brought out below are really at what the IESG would
call 'DISCUSS-DISCUSS' level.  The issue of URI scheme redefinition may
well have already been cleared by the URI expert - the draft does not do
itself any favours here by failing to explain what the syntax changes
are in s4.2; this raises immediate red flags that only start to fade a
couple of hundred pages later. The rudimentary nature of the pipeline
mechanism is carried over from RTSP 1.0.  I'd like to be sure that this
has been properly discussed in the WG as it looks pretty flaky to an
outsider.  There are several inconsistencies between various lists of
headers that need sorting out and there is no definition of
Proxy-Authorization in the ABNF.

There are also a fairly large number of editorial nits but these are all
localized and trivial to fix.  Finally I have't had time to review the
appendices (maybe there will be a follow up).

Robert Sparks is the main gen-art reviewer for the document; he asked
for additional eyes on the document given the size and his RAI
background.  Having (just) seen his review, I think we have both picked
up on the URI scheme and pipeline issues.  I am not sure that I concur
with his view that there is significant normative material in the
appendices - AFAICS the main protocol definition *is* in the main body
of the document and the bits especiially in Appendices B and C are not
the core of the protocol.  However this is based on a very cursory
glance through something like 75 pages of the document.  However, I do
concur with Robert's view that it needs a security expert to check the
security stories.

Major(ish) issues:
s4.2: This section (re-)defines the URI schemes "rtsp" and "rtsps". The 
last sentence of para 1 states that the 'details of the syntax' of the 
URIs 'have been changed'.  Is this a reasonable thing to do? Has this 
been cleared with the URI expert reviewer?  I am not entirely clear what 
the change involves and the draft doesn't explain exactly how the syntax 
has been altered  and its consequences (if any) in s4.2.  Some details
are finally given in s22.14.


Minor issues:
s11, para 3: I guess that the WG decided that sticking with the RTSP 1.0
model of sending requests and worrying about success of prior prior
pipelined requests was the right answer.  I would have thought that it
might have been helpful to provide qualifiers on the Pipelined-Requests
header that allowed subsequent requests to be suppressed unless the
previous command resulted in one of a given set of status codes with a
'reset' option to 'restart' the pipeline.  It strikes me that this would
avoid some irritating need to work out how to recover from arbitrary
failures in a command chain in a client.

Nits/editorial comments:

General: s/i.e./i.e.,/; s/e.g./e.g.,/

General:  Consistent usage of octet vs. byte (octet preferred).

General: Consistent use of '(session) keep alive' vs. '(session) keep-alive'

General: Consistent use of Base64 vs BASE64.

s1, para 2, last sentence: s/delivered as a time-synchronized 
streams/delivered as time-synchronized streams/

s1. last para: s/used terms/terms used/

s1, last para: Need to expand SDP acronym.

s2, para 1: s/considered use cases/use cases considered/

s2.1, para 1: s/completely out of bands/completely out of band/

s2.1, next to last para: It would be useful to  provide a pointer to 
where the  two URI schemes are defined (s4.2?) so it is clear these are 
internally defined and one needn't go looking for another doc.

s2.2, para 5: s/uses client-selected identifier/uses a client-selected 
identifier/

s2.2, para 5: For  consistency there should be a reference for s18.32 
with Pipelined-Requests.

s2.2, last para: For  consistency there should be a reference for s18.29 
with Media-Range.

s2.3, para 1: Expand SMPTE acronym.

s2.3, para 3: Reference s13.5 for PLAY_NOTIFY

s2.3, para 5:
> The server should also regularly send every 5
>     minutes the current media range in a PLAY_NOTIFY request.
Shouldn't this be configurable?

s2.3, last para:
> If the client waits too long
>     before resuming the pause point, the content may no longer be
>     available.  In this case the pause point will be adjusted to the end
>     of the available media.
I know this is a subjective choice, but I would have thought adjusting 
to the beginning of the available media would be what the user expects.
Later: Having read s13.4.1, I think this conflicts with (or is unclear) 
compared with s13.4.1, para 2 which states that the pause point will be
the oldest retained time - that is what I would have expected.

s2.4, para 1: For  consistency there should be a references for 
s22.11/s22.9 with RTP-Info and Range.

s2.4, para 2: s/that can be used/can be used/

s2.5.1, paras 2/3:  Should have references to ss18.48/18.44 for Scale/Speed.

s2.5.1, para 6:
OLD:
These media manipulation and when they are needed are highly media-type 
dependent.
NEW:
The nature of these media manipulations and when they are needed is 
highly media-type dependent.
--or--
The nature of this media manipulation and when it is needed is highly 
media-type dependent.

s2.5.1, para 9: s/and the currently used scale factor
    exist./and the scale factor currently in use, exists./
OLD:
    a mechanism for
    updating the media properties and the currently used scale factor
    exist.
NEW:
    a mechanism exists for
    updating the media properties and the scale factor currently in use.

s2.6, bullet 1: Need to expand RTCP acronym (RTP is 'well-known' but not 
so RTCP apparently).

s2.6, para 5: Reference s13.7 for TEARDOWN.

s2.6, para 7: s/10*times/ten times/

s2.6, last para: Reference s13.10 for REDIRECT

s2.6, last para: Reference s22.10 for Terminate-Reason

s2.7, para 2: Reference s18.41 for Require

s2.7, para 2: The reference for s18.35 for Proxy-Require should be moved 
from bullet 2.

s2.7, para 3: s/in order of the magnitude/in increasing order of the 
magnitude/

s2.7, bullet 3: s/standard/standards/

s3.1, para 3:  Clearly there won't be any smaller type paras in the 
ASCII version.. is there a PDF version that actually has smaller type?  
The one I get from the repository doesn't seem to have any smaller type 
paras.

s4.2, para 2, last sentence:
OLD:
This way RTSP 2.0 URIs for request
    can be produced from an RTSP IRI.
NEW:
This allows a URI that matches the RTSP 2.0 specification, and so is 
suitable for use in a request, to be created from an RTSP IRI.

s4.4: An external reference to the relevant Society of Motion Picture 
and Television Engineers standard (probably SMPTE 12M) ought to be 
included to define things like "SMPTE 30 drop".  [Aside: 29.97 frames 
per second?? Must be something to do with Never Twice the Same Color.  
Oh, well,  a little research job for whan I am really bored.]

s4.5: The NTP reference is interesting but gratuitous.

s4.6:  It would be useful to add the "clock=19961108T143720.25Z-" form for 
consistency with s4.4 and s4.5 as well as the 'free-standing' absolute
time which is used in Media-Properties etc.

s4.8, para 1: A more precise reference for HTTP ETag would be helpful.

s4.9, para 1: s/the below listed media properties/the media properties 
listed below/

s4.9.1: There seems to be some confusion in this section between the
values from the Seek-Style header and the values from the
Media-Properties random access property.  The section says the values
are from Seek-Style but they are actually from the random access
property.  Presumably there was some intention to interelate the media
capabilities and the play event policies?  Further this section has
Random Access, Conditional Random Access, Return to Start and No
Seeking.  This doesn't match exactly with either Seek-Style (RAP, CoRAP,
First-Prior and Next) or Media-Properties (Random-Access, Beginning-Only
and No-Seeking).

s4.9.2, "Time Limited": s/before given wallclock time/before the given 
wallclock time/

s4.9.3, para 1: s/during time/over time/

s4.9.x: It would be desirable to use the parameter names in the same 
form as they appear in s18 (e.g., Random-Access instead of Random 
Access, No-Seeking instead of No seeking) both in the definitions 
(s4.9.1 - s4.9.4) and the mapping (s4.9.5).


ss4.4/4.5/4.6: If I read the ABNF in s20.2.1 correctly, the unqualified 
values "smpte", "npt" and "clock" are valid  in the Range parameter.  
What is the meaning of such an unqualified value?

s5:  It would be sensible to note that the ABNF fragments in s5 and the 
following sections match with the full syntax productions in s20.

Table 3:  Proxy-Authorization (Section 18.34) doesn't appear in any of 
the various header categorization tables [I must have better things to 
do than checking they were all there :-( ].  I think it belongs here.

s5.3: For consistency with s9.2, this section should also say that a 
message with a body MUST contain a Content-Type header also.

s5.3, para 1:
> An example of a message body is the Session Description
>     Protocol (SDP).
Er, perhaps not the *whole* protocol?  Maybe an SDP message??

s7.2, para 1 and Table 3:  Perhaps the headers that can also be in 
Response messages could be marked?  I believe these are Range, Scale, 
Session, Supported and Transport.

s8.1.1: Should clarify that a separate registry is being defined so the
story about importing HTTP codes doesn't have any impact on the HTTP
registry.  I initially read this as if it did.

s8.1.1, para 5:  Is there some deep reason for labelling this 3rr rather 
than 3xx? (and throughout the document).  Sort of understandable but a 
bit odd.

s8.1.1, code 505:  HTTP code 505 is explicitly '*HTTP* version not 
supported' - should there really be a separate code for 'RTSP version 
not supported'?

s8.1.1, code 551: s/Support/Supported/

Table 5: Alphabetic sort on Server and Session is incorrect.

s8.2, last para: s/recognize them to be response-header/recognize them 
to be a response-header/

s9, para 1:  Should the cross-reference be to s5.3 (message body) rather 
than 5.2?

s9: Is it deliberately left vague as to whether other message types 
might have message bodies?

s10.2, para 6 and following note:  I can't see that the note following 
para 6 can be justified: since the restriction on multiple connections 
from a client to a server is only a SHOULD, an interoperable server MUST 
be capable of handling multiple connections from a client unless the 
server can explicitly send back a TOO MANY CONNECTIONS status.

s10.2, para 10: s/due to the response is caught in the queue behind a 
number of request that/due to the response being caught in the queue 
behind a number of requests that/

s10.3, para 4, "on the flip side":  Slang.  Maybe "Contrariwise" or 
something less archaic.

s10.4, para 4: Expand RTT acronym (its apparently not well-known).

s10.5, para 1: s/ To show liveness between RTSP request issued/ To show 
liveness between RTSP requests being issued/

s10.5, RTCP para: s/it MUST also work as keep alive/it will necessarily 
also function as a keep alive/; s/statistical guarantees to reach the 
server/statistical guarantees of reaching the server/

s10.5, RTCP para:
OLD:
         That client has, for a network with 5
         % packet loss, the probability to fail showing liveness sign in
         that session within the timeout interval of 2.4*E-16.  Sessions
         with shorter timeouts, or much higher packet loss, or small
         RTCP bandwidths SHOULD also use any of the mechanisms below.
NEW:
         That client has, for a network with 5% 
         packet loss, a probability of failing to confirm liveness 
         within the timeout interval for that session  of 2.4*E-16.  
         Sessions with shorter timeouts, or much higher packet loss, 
         or small RTCP bandwidths SHOULD also implement one or more 
         of the mechanisms below.

s10.5, RTCP para: expand SSRC acronym.

s10.5, SET PARAMETER para: s/keep-alive/keep alive/

s10.5, last para: Should clarify that the 'timeout parameter' is a 
qualifier on the Session parameter - 'timeout parameter' appeared to 
indicate that it was a separate protocol parameter and sent me searching.

s10.6: RFC 3986 has capability for dealing with IP versions beyond 6... 
should these be carried over into RTSP?  The IANA registry says they are.

s10.7, para 3: s/and in dependency of its current load situation/and 
bearing in mind its current load situation/; s/to  increase the length 
proportional with the load of the server/to increase the timeout period 
in proportion to the current load on the server/

s10.7, para 3: Anti-synchronization measures such as are RECOMMENDED 
here are usually MANDATORY. (Also applies to wait timer in last para of 
this section).

s10.7, para 4: s/Another issue are load balancing RTSP proxies/A more 
complex case may arise when a load balancing RTSP proxy is in use/

s10.7, last para: Should the doubling of the wait timer have an upper limit?

s11, para 4: s/Feature-Tag/Feature-tag/

s11, para 4: According to s22.1.3, play.basic, play.scale and play.speed
are 'defined' in this draft.  The nearest thing to a definition of
play.basic that I can find is the last sentence of para 4 in this
section.  I am not convinced that I could produce an interoperable
implementation of a server with this feature-tag with the one sentence
'definition'.  References to where play.xxx are defined would be useful
(play.scale in s18.44, play.speed in s18.48).

s11, Supported (and Proxy-Supported) bullets: 
OLD:
         This results in the
         receiver is learning the requester's feature support.
NEW:
         This results in the
         receiver learning the requester's feature support 
         relevant to the specified resource.
[Note: I added 'specified resource' here and then thought about whether
this made any sense.  It probably needs to be clearer what set of
features are included in the Supported list for both requester and
responder.  Are they restricted to those relevant to the specified
resource that might of course be the whole server, proxy - or client?? -
in which case there isn't an issue, but it might be a specific
presentation - what happens then?  Affects s13.1, para 3 also.]

s11, Proxy-Supported bullet: To emphasise the 'intersection of features'
mechanism used for Proxy-Supported (s18.36), it might be good to 
s/a view of what functionality the proxy chain/a view of the common
functionality supported by all members of the proxy chain/

s12, para 2: Might be better with:
s/allow all requests to setup and initiate media delivery/allow all
requests involved in setting up and initiating media delivery/

s12, para 2, last sentence: s/with at least one RTT/by at least one RTT/

Table 7: The 'Server req' and 'Client req' columns are not described.

s13.1, para 1: s/a client request it to a server/a client can send the
request to a server/

s13.1, para 1:
OLD:
   The client, server or proxy MAY also
   implement the converse of their required capability, but still retain
   the prior mentioned about what is a "MUST implement".
NEW:
   In addition to this "MUST implement" functionality, clients, servers 
   and proxies MAY provide support both for sending OPTIONS requests and 
   generating responses to the requests. 

s13.1, para 3: s/Regardless of scope of the request/Regardless of the
scope of the request/

s13.1, para 4: s/ID/identity/

s13.1, last para: s/fictional/fictitious/

s13.2, example S->C: Is Mark Handley cool with using his name? Might be
better to use the traditional 'another' (A.N.Other).

s13.3, para 1:  It would be helpful to copy the list of (3) states from
Appendix B somewhere around here and mention that the protocol drives a
state machine.

s13.4.1, para 2:
> Upon receipt of the PLAY request, the server MUST position the normal
>    play time to the beginning of the range specified in the received
>    Range header 

Should this mention the caveat that (if I understood earlier statements
correctly) the server may not be able to deliver exactly on this MUST
and then sets it the nearest it can manage? This is borne out by the
example later in this section where the server sets the start point back
10ms (and says so), etc.  Seek-Style affects the interpreation of MUST!

s13.4.1, page 72:
OLD:
   i.e.
   being handled the same as the request was received in Ready state.
   In the case the range in Range header has an implicit start time
   (-endtime),
NEW:
   i.e.
   being handled in the same way as if as the request was received in Ready state.
   In the case that the range in Range header has an implicit start time
   ("-endtime"),

s13.4.3, para 2: s/will take action/will take effect/

s13.4.3, page 76: s/entering or leaving from fast forward or fast
rewind./entering or leaving fast forward or fast rewind mode./

s13.4.4/.5/.7/.8: In these sections the Media-Property random access
property is stated as being required to be Random-Access.  Is
Conditional Random Access a possible value for this property? The
confusion in s4.9.1 does not allow me to conclude that this shouldn't be
a value for the property (sorry for the double negative but this looks a
bit confused).

s13.5.1:  Apologies if this question is stupid - I am not a media stream
wxpert.  Suppose we have an aggregated stream with (say) a number of
recorded media items making up the aggregate.  The client sets it on to
play to the end.  What happens if not all the streams end at the same
time?  Do we get PLAY_NOTIFY End-of-Stream notifications for each
individual stream as it ends or just one when the complete aggregate
ends?

s13.5.2, para 2:
> that changes the basis for making
>    estimates on how the media range progress. 
I can't parse the last part of this and I am not sure what it should be.

s13.5.3, first sentence: 'change the rate' of what? media delivery
presumably.

s13.5.3, para 2: s/adjust the used Scale value/adjust the Scale value
used/

s13.5.3, para 2: s/where the change took effect/when the change took
effect/; s/ID/identity/

s13.6, para after 1st example:s/ resume from the pause/resumes from the
pause/

s13.7.1, para 3:
OLD:
   This may result in
   that a session returns to non-aggregated control, due to that it only
   contains a single media after the requests completion.
NEW:
   This may result in
   a session returning to non-aggregated control, because it only
   contains a single media after the request's completion.

s13.8, para after bullets: s/request parameters/requests parameters/; 
s/Due to this reason/For this reason/

s13.9, para 2: s/In the case a parameter/When a parameter/

s13.10, 3rd para after numbered bullets, page 93: s/"time" parameter are
included/"time" parameter is included/

s13.10, page 94, para next but 1 before example:
OLD:
   However, the
   usage of conditional SETUP using MTag identifiers are RECOMMENDED to
   verify the assumption.
NEW:
   However, the
   usage of conditional SETUP using MTag identifiers is RECOMMENDED as
   a means to verify the assumption.

s14, para 2: s/integer/unsigned integer/ (I assume)

s14: What happens if the upper layer PDU is longer than (2^16 - 1)?

s14, figure: Binary header should have a figure number and title.

s14, figure: 'Length number of bytes of binary data' is confusing.
Maybe 'Binary data (length as in Length field)'

s17.3:  Uses 3xx in the title and 3rr in the body. See previous comment
about 3rr.

s17.4.32: s/next hops/next hop's/ (I think).

s17.5.6: See previous comment about overloading the 505 error code.

s18, Table 8 caption: 
OLD:
Note: It is allowed for all error messages 4xx and 5xx to
                                have a body
NEW:
Note: All error messages for statuses 4xx and 5xx are allowed to
                                carry a body.

s18, para after Table 8: s/[HX.Y] to informational refer to Section
X.Y/[HX.Y] to reference Section X.Y/

s18.2, para 2: s/This as/This is because/

s18.2, para 2: Expand DER avronym.

s18.2, para 3: s/replacement algorithm exist./replacement algorithm
exists./

s18.5, para 1: s/formats it support to receive/formats are acceptable
when received/

s18.6 para 1: s/to strictly inform the recipient of valid methods/to
inform the receipient of the complete set of valid methods/

s18.6, para 2: s/Allow/Allow message-header/; s/is different than/is
different from/

s18.8, para 2: s/due to that/because the/; s/what is reasonable/what is
a reasonable/

s18.10, para 3: s/govern only/govern just/; s/Below is the
description/Below are the descriptions/

s18.10: The various descriptions talk about 'media stream'.  Presumably
this should include media streams and RTSP responses.

s18.10, no-cache para: 
OLD:
Note, there is no security function enforcing that the content can't be
cached.
NEW:
Note, there is no security function preventing the caching of content.

s18.10, private para:  Is there any way in RTSP for the cache to know
whether this is a private cache for the user that should cache this
content?
s18.10, last para:  I am not absolutely certain, but I think this para
is specific to the max-age cache type rather than being generic as
implied by the indentation. [If so use the <vspace blankLines=1/> trick
to provide a pseudo-paragraph break]

s18.11, para 5: s/therefore see/therefore sees/

s18.12, para 1: s/of any next hop that need to be approved/for any next
hop that needs to be approved

s18.12: Figure needs a number and a caption.

s18.14: Consider adding the 'identity' value explicitly to the ABNF.

s18.17, para 6: s/relative URI/relative URI(s)/

s18.10, last para: Should have a reference to RFC 1123 for the date format.

s18.28, para 1: s/properties take effect/properties taking effect/

s18.29, para 2: Are (or should there be) constraints on the ordering of
media ranges for a non-continuous media stream?  It would probably make
the client's job easier if they were in incresing order. 

s18.32, para 3: s/or request of any type/or requests of any type/

s18.32, para 4: s/to a session context exist/to a session context
exists/

s18.39, para 2: Strictly 'fragment' should be 'fragment identifier'.

s18.40, para 1: s/that takes time/that take time/; s/such a/such as/

s18.41, para 1: s/the Supported/the Supported message-header/

s18.41: It appears from a literal interpretation (the third sentence is
an unqualified MUST) that the responder has to respond with error code
551 and an (empty?) list of Unsupported features if it actually does
support all the features.  I suspect this is not what is wanted.

s18.43, para 2: s/result in that a client needs/result in a client
needing/; s/Also functionality as informing/Also functionality that
informs/

s18.43, para 3: s/also the Range header MUST be included/the Range
header MUST also be included/

s18.43, para 9: It might be wise to explicitly expand the NTP acronym
even though it is well-known - its a long distance since the doc told us
not to confuse NPT and NTP.

s18.45, para 4: Harummph! Political Correctness strikes again.  Every
protocol should (and probably does) have a CRAP policy. ;-)

s18.50, Session-Timeout para: s/is kept alive/has been kept alive/

s18.50, time para: s/will stop provide/will stop providing/ 

s18.52, 1st 'No dest_addr' para: s/send media to same address for
which/send media to the same address from which/

s18.52, 2nd dest_addr para: Expand DoS acronym. 

s18.52, 'unicast/multicast' para: s/transmission needs/transmission
need/

s18.52, bottom of page 168:
OLD:
         The host address part of the tuple MAY be empty, for example
         ":58044", in cases when only destination port is desired to be
         specified. 
NEW:
         The host address part of the tuple MAY be empty, for example
         ":58044", in cases when it is desired to specify only the
         destination port. 

s18.52, 2nd para of src_addr section on page 169:
      s/media streams data packets/media stream's data packets/ (I think
there is only one implied - could be "data streams'" if many). 

s18.52, 'setup' section:  There seems to be some inconsistency in the
spcification of the 'active/passive/actpass' values.  a) Is there some
reason for specifying them in square brackets? b) should they say
["active:"] or ["active":] - both formats are used?  The ABNF has the
plain words with no brackets or quotes.

18.52, 'connection' section, 1st line:
s/Clients use the setup parameter/Clients use the connection parameter/
(I assume).

s19.2, para 1: s/both on URI level and port level/both on the URI level
and the port level/

s19.3, para 2: s/the client and server also needs to be aware/the client
and server also need to be aware/

s19.3.1, 'Any' para: s/accept whatever certificate presented/accept
whatever certificate is presented/

s19.3.1, 'Proxy' para: s/;/:/

s20: Proxy-Authorization seems to be missing from the ABNF altogether.

s20.2.1, 'smpte-range' production:  The reference should be to Section
4.4 I think - there is no Section 3.4 and s4.4 talks about SMPTE.

The next four comments are inconsistencies that need sorting out:

s20.2.2: Accept-Ranges and RTP-Info are classified as general headers in
Table 1 but appears in response-header here.

s20.2.2: User-Agent is classified as a request header in Table 3 but
appears in general-header here.

s20.2.2: Server is classified as a response header in Table 5 but
appears in general-header here.

s20.2.2: Accept-Credentials is classified as a request header in Table 3
but appears in response-header here.

s20.2.2, response-header production: Alphabetic sort fails at
MTag/Location. :-(

s21, para 2: s/appendix/an appendix/; s/the media security/media
security/

s21.1, Abuse of Server Logs:  [H15.1.1] doesn't really give much advice
beyond what is said here already.  One could copy the one sentence of
'mind out for the lawyers' advice here and save the indirection.

s21.1, transfer of sensitive info: Is there an equivalent of the Referer
header in RTSP?  Not sure there is but it would be good to explain one
way or the other (either there isn't one so it's less of a problem or
this is the equivalent...)

s21.1, Attacks based on file names etc: The reference should be to
[H15.2].

s21.1, DNS Spoofing:  Presumably RTSP will interact significantly with
content delivery networks.  Some of these work by DNS 'spoofing' that
was in its infancy when RFC 2616 was published.  Are there any other
issues that come out of the greater prevalence of CDNs since 1999?

s21.1, Session Hijacking:  The last part of this is written so that it
appears to mandate authentication in all cases.  As far as I understand
it is up to the client to decide if it needs authentication etc and some
content will be offered on unsecured URIs.  I think this needs to be
clearer that authentication will mitigate the problem but whether it is
done is up to the client if the server doesn't care.

s21.1, Persistently suspicious behaviour:  There seems to be a mismatch
between the title (persistently..) and the first sentence (a single
instance).  Do we have examples of the sort of security risk which is
supposed to be met with a 403 response the first time?

s21.1, last para: s/will be present by following the specification as
written,/will be instantiated if the specification is implemented as
written,/; s/prevent session hijacking/minimize the risk of session
hijacking/; s/strongly improved/greatly improved/

s21.1, last sentence:
>    Some of the above threats are such that
>    the implementation of the RTSP functionality itself needs to consider
>    which policy and strategy it uses to mitigate them.
It strikes me that this is not very helpful to a prospective
implementer.  The point of this section is at least in part to provide
that policy and strategy.  I am not quite sure how to rewrite this (or
if indeed other people think it does need rewriting). 

s21.2, para 1: s/like RTP/such as RTP,/; s/that exist/exist/

s21.2, Media Confidentiality: s/Thus also the signaling protocol
must/Thus the signaling protocol must also/

s21.2, Media Integity amd Auth: s/will have interest to substitute/will
be interested in substituting/

s21.2, Scope of Multicast: s/it is needed to consider the scope that
delivery has./the scope of the delivery must be considered./

s21.2.1, para 1: s/ascertaining the attackers/ascertaining the
attacker's/

s21.2.1, para 1: 
> Security mechanisms
>    that are acceptable in an increased generality are:
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Does this mean 'in order of increasing generality'?

s21.2.1, 2nd bullet: s/that accept to be/that have consented to be/

s21.2.1, last para on p204: Expand ICE acronym. (NAT is well-known).
 
s21.2.1, first para on p205: s/username/a username/; Expand STUN acronym

s21.2.2, RTP/RTCP Extensions: s/and disrupt video/and disruption of
video/

s21.2.2, next to last para:
OLD:
it is clear that strong
   security mechanism to protect RTP is necessary to support. 
NEW:
it is clear that it is necessary that a strong security mechanism is
supported to protect RTP.

s21.2.2, last para: s/beyond the mandatory to implement/beyond those
mandatory to implement/

s22: Ought to have the standard note about replacing RFCXXXX with the
number of the document when approved...

s22, para 2: s/follow the below defined procedure/follow the procedure
defined below/

s22, para 3: s/some of the requirements level/some of the registration
policies/

s22.1.3: References back to the sections which define the play.xx
feature tags should be added.  As previously stated, I am not entirely
sure what the required features are to meet the play.basic requirements.
 
s22.2.1: s/Methods are described in Section Section/RTSP Methods are
described in Section/

s22.3:  The rules about allocating in the sections above x50 should be
explained here (see s8.1.1).  The  numbers below x50 in each section
should be marked as a special category of reserved so they are only
allocated to HTTP analogues.  Is an experimental/private segment in each
category desirable?   

s22.9: Being allowed to register new Range header formats will currently
be restricted to times specified by NPT, SMPTE or UTC because no
registry is defined for Accept-Ranges.  Is this what is intended?




From alexey.melnikov@isode.com  Thu Jun  6 03:05:32 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2346421F9921 for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 03:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RbJ8IYlFQo6w for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 03:05:31 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id B0E9E21F9923 for <gen-art@ietf.org>; Thu,  6 Jun 2013 03:05:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1370513123; d=isode.com; s=selector; i=@isode.com; bh=sKERDKLio+8hXh8+u3X9jal/OmdvlRzNxn+XedjIUh0=; 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=phCOZxNR4zwvxH/HqjhNpzxHqRsUaWtEIldi0S3Et/LKdjontwNz6QeiQgAtS63L2rstSa B5ik77YVE3VtMfKoJwJe9BU6bLjGVOxMeCYCOABeefUNwqlhE/+yl8JJ5ThycPR8A/WEMB sY9BD8x1h1zUZ4tuZRYFfyuPjlkOuF8=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UbBe4gBcbIlC@waldorf.isode.com>; Thu, 6 Jun 2013 11:05:22 +0100
Message-ID: <51B05EE4.1010405@isode.com>
Date: Thu, 06 Jun 2013 11:05:24 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
To: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-forces-interop-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 10:05:32 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-pce-gmpls-aps-req-07
Reviewer: Alexey Melnikov
Review Date: 2013-06-06
IETF LC End Date: 2013-06-07
IESG Telechat date: (if known)

Summary: This draft is ready for publication as an informational RFC.

Major issues: None.

Minor issues: None.

Nits/editorial comments:

I might have missed that, but I think the first mention of ERO
needs expansion of the acronym and a reference.


From dromasca@avaya.com  Thu Jun  6 08:29:23 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A966221F999E for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 08:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iD3oheJSt52w for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 08:29:18 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 130EB21F997A for <gen-art@ietf.org>; Thu,  6 Jun 2013 08:29:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAKypsFHGmAcF/2dsb2JhbABZgmghML9HeBZ0giUBAQMSKDgCBRIBFQcOFEImAQQODRMHh2sBC584nAGPATGDAWEDmGiFGIp/gw+CJw
X-IronPort-AV: E=Sophos;i="4.87,815,1363147200"; d="scan'208";a="15019653"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 06 Jun 2013 11:29:16 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Jun 2013 11:28:01 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Thu, 6 Jun 2013 11:29:15 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-ART review for draft-ietf-avtcore-idms-09
Thread-Index: Ac5iypmOjhIiotB8SaWTHuSE0Blm6Q==
Date: Thu, 6 Jun 2013 15:29:14 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA183D3E@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-avtcore-idms-all@tools.ietf.org" <draft-ietf-avtcore-idms-all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review for draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 15:29:23 -0000

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-avtcore-idms-09
Reviewer: Dan Romascanu
Review Date: 6/6/13
IETF LC End Date: 6/11/13
IESG Telechat date:=20

Summary:

Not Ready

Major issues:

1. This document is tightly connected with the ETSI specification TS 183 06=
3. However this relation is mentioned only in a couple of places and does n=
ot describe the complexity of the relation. Moreover, the relation itself s=
eems problematic.=20

The I-D uses some of the inter-destination media techniques described by ET=
SI TS 183 063. For example Section 7 replicates part of the content of Anne=
x W of the ETSI document. It does it partially however, and with some modif=
ications, as only the content definition and behavior of the transmitters a=
nd receivers for SPST=3D1 were taken from Annex W, while the content and be=
havior for SPST=3D2-4 are marked as 'defined by ETSI TISPAN'. The ETSI docu=
ment details what happens with the fields when SPST=3D2-4. This will result=
 in the RTCP XR block for IDMS to be defined in two places - part in this I=
ETF document (if approved), the rest in the ETSI document (to be modified a=
ccordingly in the future). For some period of time the same fields will be =
defined in two places. This seems broken.=20

2. The note to the RFC Editor in section 14.2 states:=20

   14.2.  RTCP XR IDMS Report Block

   This document assigns the block type value 12 in the IANA "RTCP XR
   Block Type Registry" to the RTCP XR IDMS Report Block.
=09
   [Note to RFC Editor: this block type value is currently assigned to
   [TS183063].  This document replaces [TS183063] as the normative
   specification of the RTCP XR IDMS Report Block.  Upon publication of
   this document as RFC, [TS183063] will be changed to reflect this.

The first statement is not accurate. Value 12 is not a new assignment, 12 w=
as already assigned by ETSI, this document asks to change the assignment of=
 value 12 from the RTCP XR Block Type for reporting IDMS information to the=
 IETF defined RTCP XR IDMS Report Block. This change is however partial as =
described previously, as the content of the fields and behavior for SPST =
=3D 2-4 remain under ETSI control. Moreover, it is not clear who has furthe=
r control for other new values, as SPST =3D 5-15 show as 'reserved for futu=
re use in both documents'. The IANA section does not define or refer an IAN=
A registry and the policy for adding and approving new values for SPST.=20

This solution is not clean. Only one organization should have control upon =
the definition of one single RTCP XR block type. Either the IETF should mak=
e the overleaping parts of the  document Informational and reflect the cont=
ent of the ETSI document, or should take control over the whole block.=20

3. The relation with the ETSI specification TS 183 063 should have been des=
cribed clearly from the beginning of the document.=20

Minor issues:

1. The version of the block definition is set to V=3D2 which is the same as=
 in the ETSI specification. Were versions 0 and 1 already used by ETSI? If =
this is the case a note should be made.=20

2. In Section 7:=20

   Reserved bits (Resrv): 3 bits.  These bits are reserved for future
   definition.  In the absence of such a definition, the bits in this
   field MUST be set to zero and MUST be ignored by the receiver.

s/MUST be set to zero/MUST be set to zero at transmission/

3. In Section 7:=20

   Reserved bits (Resrv): 25 bits.  These bits are reserved for future
   use and SHALL be set to 0.

s/ SHALL be set to 0/ MUST be set to zero at transmission and MUST be ignor=
ed by the receiver/

4. In Section 7:=20

   When
   reporting on an RTP packet which is one of several consecutive RTP
   packets having equal timestamps, an SC SHOULD report on the RTP
   packet it received with the lowest sequence number.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

5. In Section 8:=20

   Because RTP
   timestamps do wrap around, the sender of this packet SHOULD use
   recent values, i.e. choose NTP timestamps that reflect current time
   and not too far in the future or in the past.=20

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

6. In Section 8:=20

   This SHOULD relate to the first
   arriving RTP packet containing this particular RTP timestamp, in case
   multiple RTP packets contain the same RTP timestamp.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

7. In Section 8:=20

   The timestamp is formatted based on the NTP
   timestamp format as specified in [RFC5905].  If this field is empty,
   then it SHALL be set to 0.  This field MAY be left empty if none or
   only one of the receivers reported on presentation timestamps.

Why a MAY here? Especially for the case when none of the receivers reported=
, what content can be set there but 0 ?

8: The reference:=20

[TS183063]
              "IMS-based IPTV stage 3 specification, TS 183 063 v3.4.1",
              June 2010.

V3.4.1 is not the latest release. Is this intentional? I found at least one=
 more recent release dated 2011 and numbered 3.5.2 - I do not know if there=
 is any diff in the relevant content, but pointing to the most updated revi=
ew seems appropriate.

9: Did this document undergo an SDP directorate review? If not I believe th=
at one would be necessary, as a new SDP Attribute is being defined.=20
=20
Nits/editorial comments:

1. typo in the last paragraph of section 5 - s/nessecary/necessary/

2. in section 8 expand PT as Packet Type

3. typo in the first paragraph of section 11 - s/mutli/multi/



Regards,

Dan



From mahoney@nostrum.com  Thu Jun  6 16:06:33 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C7121F998D for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 16:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bcWQlr-YRVCL for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 16:06:32 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 83ADF21F998B for <gen-art@ietf.org>; Thu,  6 Jun 2013 16:06:31 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r56N6Uf6037745 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 6 Jun 2013 18:06:31 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51B115F1.7010901@nostrum.com>
Date: Thu, 06 Jun 2013 18:06:25 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-06-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 23:06:33 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
David Black       2013-06-17   draft-ietf-abfab-eapapplicability-03

Elwyn Davies      2013-06-18   draft-ietf-payload-vp8-08

Francis Dupont    2013-06-19   draft-ietf-rtgwg-cl-requirement-10

Joel Halpern      2013-06-19   draft-ietf-ospf-manet-single-hop-mdr-03

Martin Thomson    2013-06-19   draft-ietf-nvo3-overlay-problem-statement-03

Meral Shirazipour 2013-06-20   draft-ietf-alto-server-discovery-08

Peter McCann      2013-06-20   draft-ietf-rmt-sec-discussion-08



I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From mahoney@nostrum.com  Thu Jun  6 16:08:52 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 947B921E8053 for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 16:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VpzvTM5ajrPU for <gen-art@ietfa.amsl.com>; Thu,  6 Jun 2013 16:08:52 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id CE82A21F9590 for <gen-art@ietf.org>; Thu,  6 Jun 2013 16:08:51 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r56N8pga037992 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 6 Jun 2013 18:08:51 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51B1167E.5080402@nostrum.com>
Date: Thu, 06 Jun 2013 18:08:46 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2013-06-13 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 23:08:52 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft
------------------------------------------------------------------------------------
Alexey Melnikov        TR2013-05-09 draft-ietf-6man-impatient-nud-06 **

Kathleen Moriarty      TR2013-05-01 draft-ietf-ipfix-protocol-rfc5101bis-07

Suresh Krishnan        TR2013-04-15 draft-ietf-sipcore-sip-websocket-08 **
Suresh Krishnan        TR2013-05-06 draft-ietf-geopriv-held-measurements-07 **

Wassim Haddad          TR2013-06-06 draft-ietf-manet-nhdp-sec-threats-04

* Earlier draft reviewed
** Already reviewed


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

For your convenience, the review boilerplate template is included below.

Note that reviews should ideally be posted to the gen-art mailing list
by COB on Tuesday:
http://wiki.tools.ietf.org/area/gen/trac/wiki/

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From prvs=5870ac8b49=magnus.westerlund@ericsson.com  Fri Jun  7 02:35:28 2013
Return-Path: <prvs=5870ac8b49=magnus.westerlund@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC27021F9648; Fri,  7 Jun 2013 02:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8FLhUvFF6Sf; Fri,  7 Jun 2013 02:35:23 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 272E321F9371; Fri,  7 Jun 2013 02:35:21 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-94-51b1a958c107
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id DE.D5.15700.859A1B15; Fri,  7 Jun 2013 11:35:20 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Fri, 7 Jun 2013 11:35:20 +0200
Message-ID: <51B1A95B.2030208@ericsson.com>
Date: Fri, 7 Jun 2013 11:35:23 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1370477514.4596.9052.camel@mightyatom>
In-Reply-To: <1370477514.4596.9052.camel@mightyatom>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNLMWRmVeSWpSXmKPExsUyM+JvrW7Eyo2BBnM+2lhc/HKE3eL4gR3s FldffWaxeLZxPovF1OWPWRxYPb6ebGfxWLLkJ5PHl8uf2QKYo7htkhJLyoIz0/P07RK4Mx7/ ncFccN2kouPldOYGxnOaXYwcHBICJhKNq4BMTiBTTOLCvfVsXYxcHEICpxgl7m26zwjhLGOU OHB2MQtIFa+AtsTNyccZQWwWARWJX8f6wWw2AQuJmz8a2UBsUYFgiSPbN0PVC0qcnPkEzBYR UJPY/PUB2FBmgXWMEidnPwJrFhbwkdgyYTVYkZCAscTjr+9ZQWxOoOvutnaxQpwnKbHlRTs7 iM0soCcx5WoLI4QtL9G8dTYzRK+2RENTB+sERqFZSHbPQtIyC0nLAkbmVYzsuYmZOenlhpsY gWF9cMtv3R2Mp86JHGKU5mBREufV410cKCSQnliSmp2aWpBaFF9UmpNafIiRiYMTRHBJNTBm Njw9vXtNjUSWqHffHf6XIhdnHWQqOXH7tfbLwsgXdjn1jrV8DCI6Oey3tmjcFJDc/Trm/qna ur78ph9FVukpx5KmPdX9LeBY19627evxW3cXyOr3VT+WMRG5YP1/RexpIY41ey3Xf92z4ffL Kfwfr/U/FPzHIuo/RU8mv0p0eV339/f6E62VWIozEg21mIuKEwF2n0SPPgIAAA==
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>, IETF discussion <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 09:35:28 -0000

Hi Elwyn,

Many thanks for the detailed review. We will address the nits you have
raised, but I cut them out of this reply to focus on the more
substantial issues you have brought up.

See inline below.

On 2013-06-06 02:11, Elwyn Davies wrote:
> I am an additional Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Document: draft-ietf-mmusic-rfc2326bis
> Reviewer: Elwyn Davies
> Review Date: 5 June 2013
> IETF LC End Date: 5 JUne 2013
> IESG Telechat date: (if known) -
> 
> Summary:
> Almost ready.  Generally this is an excellent and well written document,
> particularly given its size.  There are a few minor issues to sort out
> mainly at the nit level and some consistency issues to fix up.  The two
> issues that I have brought out below are really at what the IESG would
> call 'DISCUSS-DISCUSS' level.  The issue of URI scheme redefinition may
> well have already been cleared by the URI expert - the draft does not do
> itself any favours here by failing to explain what the syntax changes
> are in s4.2; this raises immediate red flags that only start to fade a
> couple of hundred pages later. The rudimentary nature of the pipeline
> mechanism is carried over from RTSP 1.0.  I'd like to be sure that this
> has been properly discussed in the WG as it looks pretty flaky to an
> outsider.  There are several inconsistencies between various lists of
> headers that need sorting out and there is no definition of
> Proxy-Authorization in the ABNF.
> 
> There are also a fairly large number of editorial nits but these are all
> localized and trivial to fix.  Finally I have't had time to review the
> appendices (maybe there will be a follow up).
> 
> Robert Sparks is the main gen-art reviewer for the document; he asked
> for additional eyes on the document given the size and his RAI
> background.  Having (just) seen his review, I think we have both picked
> up on the URI scheme and pipeline issues.  I am not sure that I concur
> with his view that there is significant normative material in the
> appendices - AFAICS the main protocol definition *is* in the main body
> of the document and the bits especiially in Appendices B and C are not
> the core of the protocol.  However this is based on a very cursory
> glance through something like 75 pages of the document.  However, I do
> concur with Robert's view that it needs a security expert to check the
> security stories.
> 
> Major(ish) issues:
> s4.2: This section (re-)defines the URI schemes "rtsp" and "rtsps". The 
> last sentence of para 1 states that the 'details of the syntax' of the 
> URIs 'have been changed'.  Is this a reasonable thing to do? Has this 
> been cleared with the URI expert reviewer?  I am not entirely clear what 
> the change involves and the draft doesn't explain exactly how the syntax 
> has been altered  and its consequences (if any) in s4.2.  Some details
> are finally given in s22.14.

These syntax changes where discussed in the reviews I got on the URI
list. That resulted in the explicitness in the template, but I forgot
about adding anything into Section 4.2. I see no issue with adding the
following clarification to Section 4.2:

   The details of the syntax of "rtsp" and "rtsps" URIs has been changed
   from RTSP 1.0.  These changes are:

   o  Support for IPV6 literal in host part and future IP literals
      through RFC 3986 defined mechanism.

   o  A new relative format to use in the RTSP protocol elements that is
      not required to start with "/".

   Neither should have any significant impact on interoperability.  If
   one is required to use IPv6 literals to reach an RTSP server, then
   that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
   IPv6 capable protocol.  Thus, RTSP 2.0 support will be needed anyway.
   The second change will only occur in RTSP messages, that are
   explicitly identified as being RTSP 2.0 messages, thus a RTSP 1.0
   only agent will not be required to parse this variant.

I hope this makes it clear that these syntax changes is unlikely to hurt
the interoperability.

> 
> 
> Minor issues:
> s11, para 3: I guess that the WG decided that sticking with the RTSP 1.0
> model of sending requests and worrying about success of prior prior
> pipelined requests was the right answer.  I would have thought that it
> might have been helpful to provide qualifiers on the Pipelined-Requests
> header that allowed subsequent requests to be suppressed unless the
> previous command resulted in one of a given set of status codes with a
> 'reset' option to 'restart' the pipeline.  It strikes me that this would
> avoid some irritating need to work out how to recover from arbitrary
> failures in a command chain in a client.
> 

I assume you mean this Section 12 paragraph:

   If a pipelined request builds on the successful completion of one or
   more prior requests the requester must verify that all requests were
   executed as expected.  A common example will be two SETUP requests
   and a PLAY request.  In case one of the SETUP fails unexpectedly, the
   PLAY request can still be successfully executed.  However, the
   resulting presentation will not be as expected by the requesting
   client, as only a single media instead of two will be played.  In
   this case the client can send a PAUSE request, correct the failing
   SETUP request and then request it to be played.

I think I agree with your assessment, that it would have been nice.
However, we should have thought of that when we introduced this type of
pipelining 7 years ago. Making any changes to this at this stage is
counter productive. The reality is that all the "nice" features and
necessary clarifications has been retrofitted into RTSP 1.0 by the ones
that have been using RTSP 1.0. So changing anything will separate the
RTSP 1.0 and RTSP 2.0 implementations. The good thing is that I can't
remember any substantial complaints about this issue.

I hope this resolves your comments.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From elwynd@folly.org.uk  Fri Jun  7 05:26:10 2013
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF0721F8B35; Fri,  7 Jun 2013 05:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PyqxrcKbqLXM; Fri,  7 Jun 2013 05:26:06 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id B629421F8ADC; Fri,  7 Jun 2013 05:26:05 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1Ukvk2-00081p-C1; Fri, 07 Jun 2013 13:26:02 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <51B1A95B.2030208@ericsson.com>
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Organization: Folly Consulting
Date: Fri, 07 Jun 2013 13:26:00 +0100
Message-Id: <1370607960.4596.9114.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 12:26:10 -0000

On Fri, 2013-06-07 at 11:35 +0200, Magnus Westerlund wrote:
> Hi Elwyn,
>=20
> Many thanks for the detailed review. We will address the nits you have
> raised, but I cut them out of this reply to focus on the more
> substantial issues you have brought up.
.. and thanks for the quick response.

>=20
> See inline below.
OK.  I think the responses clear those issues.

I have done a little bit more on the Appendices and liaised a bit with
Robert Sparks.  'Highlights':

Appendix F: I missed that the text/parameter format appeared in the
examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
definitions of these methods what encodings are acceptable for the
message bodies that may go with these methods and their responses.
Clearly the new text/parameter MIME format is one.  Is it the only one?
I guess you could use a application/json or an XML format but I guess
these would also either have to be called out explicitly in the method
descriptions or put in as feature extensions.  This needs to be
clarified in the method descriptions (s13).  The upshot of all this is
that I think Appendix F needs to be pulled back into Section 20 as
currently it is the only way to encode the message bodies.

Appendix B: I appreciate that the state machine is illustrative and to
an extent 'abstract'.  However, the tables are really written to
describe the state machine in the server: the action column mostly
describes the events that come into the server (apart from the notify
actions) - sending these 'events' are actions in the client.  The 'real'
state machine in the both the server and the client has a somewhat more
complex form: I'd think that there was a STOPPED state in the server
when the media has reached an end point and not been explictly paused
and STARTING/PAUSING states in the client while the client waits for
response to PLAY/PAUSE respectively.  I think a little bit more
explanation about the dual nature of the columns would solve the
problem.

Appendix C: Pending.

Regards,
Elwyn
>=20
> On 2013-06-06 02:11, Elwyn Davies wrote:
> > I am an additional Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >=20
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >=20
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >=20
> > Document: draft-ietf-mmusic-rfc2326bis
> > Reviewer: Elwyn Davies
> > Review Date: 5 June 2013
> > IETF LC End Date: 5 JUne 2013
> > IESG Telechat date: (if known) -
> >=20
> > Summary:
> > Almost ready.  Generally this is an excellent and well written document=
,
> > particularly given its size.  There are a few minor issues to sort out
> > mainly at the nit level and some consistency issues to fix up.  The two
> > issues that I have brought out below are really at what the IESG would
> > call 'DISCUSS-DISCUSS' level.  The issue of URI scheme redefinition may
> > well have already been cleared by the URI expert - the draft does not d=
o
> > itself any favours here by failing to explain what the syntax changes
> > are in s4.2; this raises immediate red flags that only start to fade a
> > couple of hundred pages later. The rudimentary nature of the pipeline
> > mechanism is carried over from RTSP 1.0.  I'd like to be sure that this
> > has been properly discussed in the WG as it looks pretty flaky to an
> > outsider.  There are several inconsistencies between various lists of
> > headers that need sorting out and there is no definition of
> > Proxy-Authorization in the ABNF.
> >=20
> > There are also a fairly large number of editorial nits but these are al=
l
> > localized and trivial to fix.  Finally I have't had time to review the
> > appendices (maybe there will be a follow up).
> >=20
> > Robert Sparks is the main gen-art reviewer for the document; he asked
> > for additional eyes on the document given the size and his RAI
> > background.  Having (just) seen his review, I think we have both picked
> > up on the URI scheme and pipeline issues.  I am not sure that I concur
> > with his view that there is significant normative material in the
> > appendices - AFAICS the main protocol definition *is* in the main body
> > of the document and the bits especiially in Appendices B and C are not
> > the core of the protocol.  However this is based on a very cursory
> > glance through something like 75 pages of the document.  However, I do
> > concur with Robert's view that it needs a security expert to check the
> > security stories.
> >=20
> > Major(ish) issues:
> > s4.2: This section (re-)defines the URI schemes "rtsp" and "rtsps". The=
=20
> > last sentence of para 1 states that the 'details of the syntax' of the=20
> > URIs 'have been changed'.  Is this a reasonable thing to do? Has this=20
> > been cleared with the URI expert reviewer?  I am not entirely clear wha=
t=20
> > the change involves and the draft doesn't explain exactly how the synta=
x=20
> > has been altered  and its consequences (if any) in s4.2.  Some details
> > are finally given in s22.14.
>=20
> These syntax changes where discussed in the reviews I got on the URI
> list. That resulted in the explicitness in the template, but I forgot
> about adding anything into Section 4.2. I see no issue with adding the
> following clarification to Section 4.2:
>=20
>    The details of the syntax of "rtsp" and "rtsps" URIs has been changed
>    from RTSP 1.0.  These changes are:
>=20
>    o  Support for IPV6 literal in host part and future IP literals
>       through RFC 3986 defined mechanism.
>=20
>    o  A new relative format to use in the RTSP protocol elements that is
>       not required to start with "/".
>=20
>    Neither should have any significant impact on interoperability.  If
>    one is required to use IPv6 literals to reach an RTSP server, then
>    that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
>    IPv6 capable protocol.  Thus, RTSP 2.0 support will be needed anyway.
>    The second change will only occur in RTSP messages, that are
>    explicitly identified as being RTSP 2.0 messages, thus a RTSP 1.0
>    only agent will not be required to parse this variant.
>=20
> I hope this makes it clear that these syntax changes is unlikely to hurt
> the interoperability.
>=20
> >=20
> >=20
> > Minor issues:
> > s11, para 3: I guess that the WG decided that sticking with the RTSP 1.=
0
> > model of sending requests and worrying about success of prior prior
> > pipelined requests was the right answer.  I would have thought that it
> > might have been helpful to provide qualifiers on the Pipelined-Requests
> > header that allowed subsequent requests to be suppressed unless the
> > previous command resulted in one of a given set of status codes with a
> > 'reset' option to 'restart' the pipeline.  It strikes me that this woul=
d
> > avoid some irritating need to work out how to recover from arbitrary
> > failures in a command chain in a client.
> >=20
>=20
> I assume you mean this Section 12 paragraph:
>=20
>    If a pipelined request builds on the successful completion of one or
>    more prior requests the requester must verify that all requests were
>    executed as expected.  A common example will be two SETUP requests
>    and a PLAY request.  In case one of the SETUP fails unexpectedly, the
>    PLAY request can still be successfully executed.  However, the
>    resulting presentation will not be as expected by the requesting
>    client, as only a single media instead of two will be played.  In
>    this case the client can send a PAUSE request, correct the failing
>    SETUP request and then request it to be played.
>=20
> I think I agree with your assessment, that it would have been nice.
> However, we should have thought of that when we introduced this type of
> pipelining 7 years ago. Making any changes to this at this stage is
> counter productive. The reality is that all the "nice" features and
> necessary clarifications has been retrofitted into RTSP 1.0 by the ones
> that have been using RTSP 1.0. So changing anything will separate the
> RTSP 1.0 and RTSP 2.0 implementations. The good thing is that I can't
> remember any substantial complaints about this issue.
>=20
> I hope this resolves your comments.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From prvs=6870181dd3=magnus.westerlund@ericsson.com  Fri Jun  7 07:05:58 2013
Return-Path: <prvs=6870181dd3=magnus.westerlund@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55FD921F8756; Fri,  7 Jun 2013 07:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yfQrbF2j5QHu; Fri,  7 Jun 2013 07:05:52 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 202DC21F84F5; Fri,  7 Jun 2013 07:05:50 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-ce-51b1e8b94b16
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id A2.82.18006.9B8E1B15; Fri,  7 Jun 2013 16:05:47 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.279.1; Fri, 7 Jun 2013 16:05:45 +0200
Message-ID: <51B1E8BD.80901@ericsson.com>
Date: Fri, 7 Jun 2013 16:05:49 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com> <1370607960.4596.9114.camel@mightyatom>
In-Reply-To: <1370607960.4596.9114.camel@mightyatom>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUyM+Jvre7uFxsDDX6eYrG4+OUIu8XxAzvY La6++sxi8WzjfBaLqcsfsziwenw92c7isWTJTyaPL5c/swUwR3HbJCWWlAVnpufp2yVwZ7xY cp+toEuuYtPRWSwNjBMkuhg5OSQETCTuzzzKAmGLSVy4t56ti5GLQ0jgFKPE1NfNrBDOMkaJ 7U9OsYJU8QpoSkze8IEZxGYRUJG4+6WfEcRmE7CQuPmjkQ3EFhUIljiyfTMLRL2gxMmZT8Bs EQE1ic1fHzCCDGUWWMco8ay3GWyosECYxLwt3UwgtpBAjcThZ6/AbE6g83Z3/maCOE9SYsuL dnYQm1lAT2LK1RZGCFteonnrbGaIXm2JhqYO1gmMQrOQ7J6FpGUWkpYFjMyrGNlzEzNz0suN NjECA/vglt+qOxjvnBM5xCjNwaIkzqvHuzhQSCA9sSQ1OzW1ILUovqg0J7X4ECMTByeI4JJq YAxRMMrVvRF/XOGI73/rjKO/9zSa3rPYkBx1WW75tSRuMUOvP5o7tyZunZ4wR+qV0OyyFAaz k+8/WtaXuineTgUGmOnO74emb+ELnfphSUX6aodPB+69E8lkvtma/XPCZea0xPjrGw/t7vxb cc1CyE8ySuCq6d6CPW+FY87uPLX17Qbn81umLlNiKc5INNRiLipOBACdPXC5PwIAAA==
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 14:05:58 -0000

Hi Elwyn,

On 2013-06-07 14:26, Elwyn Davies wrote:
> On Fri, 2013-06-07 at 11:35 +0200, Magnus Westerlund wrote:
>> Hi Elwyn,
>>
>> Many thanks for the detailed review. We will address the nits you have
>> raised, but I cut them out of this reply to focus on the more
>> substantial issues you have brought up.
> .. and thanks for the quick response.
> 
>>
>> See inline below.
> OK.  I think the responses clear those issues.
> 
> I have done a little bit more on the Appendices and liaised a bit with
> Robert Sparks.  'Highlights':
> 
> Appendix F: I missed that the text/parameter format appeared in the
> examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
> definitions of these methods what encodings are acceptable for the
> message bodies that may go with these methods and their responses.

Exactly, that is intentional. These methods can use anything that has a
MIME type. Also it has HTTP's mechanisms for determining what formats
one supports.

> Clearly the new text/parameter MIME format is one.  Is it the only one?

It is the only one defined by IETF for this purpose. That is why it is
in the appendix so that RTSP users shall have something to define the
parameters they want in. However, they have to accept the limitations of
a basic text format.

> I guess you could use a application/json or an XML format but I guess
> these would also either have to be called out explicitly in the method
> descriptions or put in as feature extensions.  This needs to be
> clarified in the method descriptions (s13).  The upshot of all this is
> that I think Appendix F needs to be pulled back into Section 20 as
> currently it is the only way to encode the message bodies.

I can agree that the format negotiation for the bodies of
GET/SET_PARAMETER is not clear. I will look at proposing some
improvements of the text related to the handling of method bodies and
their format negotiation.

However, I am not pulling in Appendix F. It is an optional to use format
for parameter value pairs that can be used in these methods, it is not
required. Nor, does the specification define any parameters that are
transferred using this interface. The things that are in the appendix
are not core protocol, they represent either informational things, like
the examples and the state machine. The other appendices are normative
definitions of particular choices for things that can be combined or
used with RTSP, like RTP as media transport.

> 
> Appendix B: I appreciate that the state machine is illustrative and to
> an extent 'abstract'.  However, the tables are really written to
> describe the state machine in the server: the action column mostly
> describes the events that come into the server (apart from the notify
> actions) - sending these 'events' are actions in the client.  The 'real'
> state machine in the both the server and the client has a somewhat more
> complex form: I'd think that there was a STOPPED state in the server
> when the media has reached an end point and not been explictly paused
> and STARTING/PAUSING states in the client while the client waits for
> response to PLAY/PAUSE respectively.  I think a little bit more
> explanation about the dual nature of the columns would solve the
> problem.

There shouldn't be an issue to clarify this nature.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From elwynd@folly.org.uk  Fri Jun  7 08:40:19 2013
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 586AB21F9798; Fri,  7 Jun 2013 08:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=0.698,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBguRDe8Pqk6; Fri,  7 Jun 2013 08:40:14 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id C662021F9732; Fri,  7 Jun 2013 08:40:07 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1Ukylo-0003mK-T1; Fri, 07 Jun 2013 16:40:05 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <51B1E8BD.80901@ericsson.com>
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com> <1370607960.4596.9114.camel@mightyatom> <51B1E8BD.80901@ericsson.com>
Content-Type: text/plain
Organization: Folly Consulting
Date: Fri, 07 Jun 2013 16:40:02 +0100
Message-Id: <1370619602.4596.9175.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, "mmusic \(E-mail\)" <mmusic@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 15:40:19 -0000

On Fri, 2013-06-07 at 16:05 +0200, Magnus Westerlund wrote:

> > Appendix F: I missed that the text/parameter format appeared in the
> > examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
> > definitions of these methods what encodings are acceptable for the
> > message bodies that may go with these methods and their responses.
> 
> Exactly, that is intentional. These methods can use anything that has a
> MIME type. Also it has HTTP's mechanisms for determining what formats
> one supports.
> 
> > Clearly the new text/parameter MIME format is one.  Is it the only one?
> 
> It is the only one defined by IETF for this purpose. That is why it is
> in the appendix so that RTSP users shall have something to define the
> parameters they want in. However, they have to accept the limitations of
> a basic text format.
> 
> > I guess you could use a application/json or an XML format but I guess
> > these would also either have to be called out explicitly in the method
> > descriptions or put in as feature extensions.  This needs to be
> > clarified in the method descriptions (s13).  The upshot of all this is
> > that I think Appendix F needs to be pulled back into Section 20 as
> > currently it is the only way to encode the message bodies.
> 
> I can agree that the format negotiation for the bodies of
> GET/SET_PARAMETER is not clear. I will look at proposing some
> improvements of the text related to the handling of method bodies and
> their format negotiation.
Good. I don't see where the server tells what formats it accepts for
either GET_PARAMETER or SET_PARAMETER.  Also the Accept spec doesn't say
anything about SET_PARAMETER.  AFAICS the client could tell the server
what formats it accepts as a side-effect of DESCRIBE but that's a bit
arcane - and it is not clear how you would separate the formats for
DESCRIBE from those for GET_PARAM and SET_PARAM.
> 
> However, I am not pulling in Appendix F. It is an optional to use format
> for parameter value pairs that can be used in these methods, it is not
> required. Nor, does the specification define any parameters that are
> transferred using this interface. The things that are in the appendix
> are not core protocol, they represent either informational things, like
> the examples and the state machine. The other appendices are normative
> definitions of particular choices for things that can be combined or
> used with RTSP, like RTP as media transport.
> 
OK, it is possible to use GET_PARAM for basic requirements without using
message bodies, so you can get away without defining a lowest common
denominator format. However, the use of message bodies for SET_PARAM is
RECOMMENDED so it seems a little odd not to ensure that server and
client will have at least one format in common. (And its not as if we
are dealing with a hugely complicated bit of spec for
text/parameters! :-) ).  Then, given the example in GET_PARAMETER it
seems sensible to advise implementing text/parameters as the default for
GET_PARAM also.

/Elwyn




From elwynd@dial.pipex.com  Fri Jun  7 16:18:44 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1488321F99B6 for <gen-art@ietfa.amsl.com>; Fri,  7 Jun 2013 16:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_26=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHprujc63Ds1 for <gen-art@ietfa.amsl.com>; Fri,  7 Jun 2013 16:18:43 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCB121F8FEC for <gen-art@ietf.org>; Fri,  7 Jun 2013 16:18:43 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1Ul5vZ-0002tv-Gx; Sat, 08 Jun 2013 00:18:40 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Sat, 08 Jun 2013 00:18:34 +0100
Message-Id: <1370647114.4596.9276.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: "draft-ietf-payload-vp8.all "@tools.ietf.org
Subject: [Gen-art] Gen-art LC review of draft-ietf-payload-vp8-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 23:18:44 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-payload-vp8-08
Reviewer: Elwyn Davies
Review Date: 7 June 2013
IETF LC End Date: 18 June 2013 
IESG Telechat date: (if known) -

Summary: Almost ready.  Needs to specify the format of all the integer
fields - a generic statement that 'all integer fields in the
specifications are encoded as unsigned integers in network octet order'
will solve this.  There is a rather awkquard downref to the VP8 coded
data format RFC 6386 - take advice from your AD on this one.  Check that
the media type registration is OK with the updated BCP (RFC 6838)

Major issues:

Minor issues:

Nits/editorial comments:
General: Consistent use of octets instead of bytes.

s4: I suspect that usage of RTP/AVPF is an upper case RECOMMENDED.  A
brief explanation of *why* the usage of RTP/AVPF is RECOMMENDED would be
helpful. 

s4.1: The formats for the Timestamp and Sequence Number fields are not
specified (presumably unsigned integers in network octet order).

s4.2: The formats for PartID, PictureID, TL0PICIDX, TID, and KEYIDX are
not specified(presumably unsigned integers in network octet order).

s4.2, Y bit: s/an change/a change/; s/rfc 6386/[RFC6386]/ 

s4.3, SizeN:  s/The size of the first partition size/The size of the
first partition/

s4.3: SizeN and VER need formats.

s5.2: First, Number and (possibly) PictureID need formats.

s6.2.2: s/will need a mean/will need a means/

s10:  Are all of the refs normative?  If so change the section title.
The only one which I am dubious about is RFC 4566 (and there is  6386 -
see next comment).

s10:  id nits complains that RFC 3894 is not referenced, RFC 4288 is
obsoleted by 6838 (need to check your media type registration against
the updated BCP) and RFC 6386 is a downref (you had better ask your AD
about this downref - it is fairly fundamental!)


From jmh@joelhalpern.com  Sat Jun  8 10:16:58 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E628621F944F for <gen-art@ietfa.amsl.com>; Sat,  8 Jun 2013 10:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jCiUgpOGoOBr for <gen-art@ietfa.amsl.com>; Sat,  8 Jun 2013 10:16:53 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 19CD621F9446 for <gen-art@ietf.org>; Sat,  8 Jun 2013 10:16:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id EB2FD1C6E6A; Sat,  8 Jun 2013 10:16:43 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-48.clppva.east.verizon.net [70.106.135.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 6E4FE1C0A93; Sat,  8 Jun 2013 10:16:43 -0700 (PDT)
Message-ID: <51B366F7.5040603@joelhalpern.com>
Date: Sat, 08 Jun 2013 13:16:39 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <51B115F1.7010901@nostrum.com>
In-Reply-To: <51B115F1.7010901@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  Review: draft-ietf-ospf-manet-single-hop-mdr-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jun 2013 17:16:58 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-ospf-manet-single-hop-mdr-03.txt

Reviewer: Joel M. Halpern
Review Date: 8-June-2013
IETF LC End Date: 19-June-2013
IESG Telechat date: N/A

Summary: This document is ready for publication as an Experimental RFC.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A

From dromasca@avaya.com  Sun Jun  9 00:53:16 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB8F21F8F33 for <gen-art@ietfa.amsl.com>; Sun,  9 Jun 2013 00:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.224
X-Spam-Level: 
X-Spam-Status: No, score=-103.224 tagged_above=-999 required=5 tests=[AWL=0.375, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtHLrzuVmmMT for <gen-art@ietfa.amsl.com>; Sun,  9 Jun 2013 00:53:10 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4C54921F8895 for <gen-art@ietf.org>; Sun,  9 Jun 2013 00:53:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAAH/ZlGHCzI1/2dsb2JhbABQgmUhNsFIgQcWdIIhAQEDEig4AgUSARUHDhRCJgEEDg0TB4dyAQugPJ0jjmUxgmdhA5gjhQaKaIMLgig
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200"; d="scan'208";a="14829044"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 09 Jun 2013 03:53:09 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 09 Jun 2013 03:48:25 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Sun, 9 Jun 2013 09:53:08 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lw==
Date: Sun, 9 Jun 2013 07:53:07 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2013 07:53:16 -0000

(resending, I mis-spelled .all address at the first try)

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-avtcore-idms-09
Reviewer: Dan Romascanu
Review Date: 6/6/13
IETF LC End Date: 6/11/13
IESG Telechat date:=20

Summary:

Not Ready

Major issues:

1. This document is tightly connected with the ETSI specification TS 183 06=
3. However this relation is mentioned only in a couple of places and does n=
ot describe the complexity of the relation. Moreover, the relation itself s=
eems problematic.=20

The I-D uses some of the inter-destination media techniques described by ET=
SI TS 183 063. For example Section 7 replicates part of the content of Anne=
x W of the ETSI document. It does it partially however, and with some modif=
ications, as only the content definition and behavior of the transmitters a=
nd receivers for SPST=3D1 were taken from Annex W, while the content and be=
havior for SPST=3D2-4 are marked as 'defined by ETSI TISPAN'. The ETSI docu=
ment details what happens with the fields when SPST=3D2-4. This will result=
 in the RTCP XR block for IDMS to be defined in two places - part in this I=
ETF document (if approved), the rest in the ETSI document (to be modified a=
ccordingly in the future). For some period of time the same fields will be =
defined in two places. This seems broken.=20

2. The note to the RFC Editor in section 14.2 states:=20

   14.2.  RTCP XR IDMS Report Block

   This document assigns the block type value 12 in the IANA "RTCP XR
   Block Type Registry" to the RTCP XR IDMS Report Block.
=09
   [Note to RFC Editor: this block type value is currently assigned to
   [TS183063].  This document replaces [TS183063] as the normative
   specification of the RTCP XR IDMS Report Block.  Upon publication of
   this document as RFC, [TS183063] will be changed to reflect this.

The first statement is not accurate. Value 12 is not a new assignment, 12 w=
as already assigned by ETSI, this document asks to change the assignment of=
 value 12 from the RTCP XR Block Type for reporting IDMS information to the=
 IETF defined RTCP XR IDMS Report Block. This change is however partial as =
described previously, as the content of the fields and behavior for SPST =
=3D 2-4 remain under ETSI control. Moreover, it is not clear who has furthe=
r control for other new values, as SPST =3D 5-15 show as 'reserved for futu=
re use in both documents'. The IANA section does not define or refer an IAN=
A registry and the policy for adding and approving new values for SPST.=20

This solution is not clean. Only one organization should have control upon =
the definition of one single RTCP XR block type. Either the IETF should mak=
e the overleaping parts of the  document Informational and reflect the cont=
ent of the ETSI document, or should take control over the whole block.=20

3. The relation with the ETSI specification TS 183 063 should have been des=
cribed clearly from the beginning of the document.=20

Minor issues:

1. The version of the block definition is set to V=3D2 which is the same as=
 in the ETSI specification. Were versions 0 and 1 already used by ETSI? If =
this is the case a note should be made.=20

2. In Section 7:=20

   Reserved bits (Resrv): 3 bits.  These bits are reserved for future
   definition.  In the absence of such a definition, the bits in this
   field MUST be set to zero and MUST be ignored by the receiver.

s/MUST be set to zero/MUST be set to zero at transmission/

3. In Section 7:=20

   Reserved bits (Resrv): 25 bits.  These bits are reserved for future
   use and SHALL be set to 0.

s/ SHALL be set to 0/ MUST be set to zero at transmission and MUST be ignor=
ed by the receiver/

4. In Section 7:=20

   When
   reporting on an RTP packet which is one of several consecutive RTP
   packets having equal timestamps, an SC SHOULD report on the RTP
   packet it received with the lowest sequence number.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

5. In Section 8:=20

   Because RTP
   timestamps do wrap around, the sender of this packet SHOULD use
   recent values, i.e. choose NTP timestamps that reflect current time
   and not too far in the future or in the past.=20

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

6. In Section 8:=20

   This SHOULD relate to the first
   arriving RTP packet containing this particular RTP timestamp, in case
   multiple RTP packets contain the same RTP timestamp.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

7. In Section 8:=20

   The timestamp is formatted based on the NTP
   timestamp format as specified in [RFC5905].  If this field is empty,
   then it SHALL be set to 0.  This field MAY be left empty if none or
   only one of the receivers reported on presentation timestamps.

Why a MAY here? Especially for the case when none of the receivers reported=
, what content can be set there but 0 ?

8: The reference:=20

[TS183063]
              "IMS-based IPTV stage 3 specification, TS 183 063 v3.4.1",
              June 2010.

V3.4.1 is not the latest release. Is this intentional? I found at least one=
 more recent release dated 2011 and numbered 3.5.2 - I do not know if there=
 is any diff in the relevant content, but pointing to the most updated revi=
ew seems appropriate.

9: Did this document undergo an SDP directorate review? If not I believe th=
at one would be necessary, as a new SDP Attribute is being defined.=20
=20
Nits/editorial comments:

1. typo in the last paragraph of section 5 - s/nessecary/necessary/

2. in section 8 expand PT as Packet Type

3. typo in the first paragraph of section 11 - s/mutli/multi/



Regards,

Dan




From david.black@emc.com  Sun Jun  9 10:47:58 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF6A521F8E9D; Sun,  9 Jun 2013 10:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AQYsBVBit40f; Sun,  9 Jun 2013 10:47:53 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id F2BA321F8D10; Sun,  9 Jun 2013 10:47:52 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59HlSAC003579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Jun 2013 13:47:28 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 9 Jun 2013 13:47:13 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59HlDKS031140; Sun, 9 Jun 2013 13:47:13 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Sun, 9 Jun 2013 13:47:12 -0400
From: "Black, David" <david.black@emc.com>
To: "d3e3e3@gmail.com" <d3e3e3@gmail.com>, "joe.abley@icann.org" <joe.abley@icann.org>, General Area Review Team <gen-art@ietf.org>
Date: Sun, 9 Jun 2013 13:47:12 -0400
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-03
Thread-Index: Ac5iOdqxPgeHIMhASdCnl829MYVBxwC/mpbg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "joelja@bogus.com" <joelja@bogus.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2013 17:47:58 -0000

The -03 version of this draft resolves all of the concerns raised by
the Gen-ART review of the -02 version.

Unfortunately, a serious typo/thinko snuck into the -03 version (been
there, done that, myself).  Section 3.2 currently says:

   00-42 is a protocol number under the IANA OUI (that is,
   00-00-0E-00-42) to be used for documentation purposes.

The parenthetical expansion of the protocol number is incorrect.
The correct expansion uses -5E- instead of -0E-:

   00-42 is a protocol number under the IANA OUI (that is,
   00-00-5E-00-42) to be used for documentation purposes.

I strongly suggest submitting a -04 version of this draft to make
the necessary single character correction (e.g., as opposed to using
a RFC Editor Note for that purpose).

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Wednesday, June 05, 2013 6:13 PM
> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> Cc: Black, David; joelja@bogus.com; ietf@ietf.org
> Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-eastlake-rfc5342bis-02
> Reviewer: David L. Black
> Review Date: June 5, 2013
> IETF LC End Date: June 4, 2013
>=20
> Summary:
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft updates the IANA registered Ethernet parameters for IETF use,
> including recording values assigned for documentation.  It also makes som=
e
> minor changes to IANA procedures.
>=20
> IANA should review this entire draft, not just its IANA Considerations
> section;
> Pearl Liang appears to have done that comprehensive review for IANA.
>=20
> Major issues: None
>=20
> Minor issues: One, the IANA review also found this issue.
>=20
> Section 3.2 states:
>=20
> 	IANA will assign "00-00-0E-00-42" as the protocol number under the
> 	IANA OUI to be used for documentation purposes.
>=20
> IANA has not made this assignment, but this assignment request is not
> recorded in the IANA Considerations section where IANA actions are
> requested and recorded by IANA after they have been performed.  This
> assignment needs to be added to the IANA Considerations section;
> see item 5 in the IANA review.
>=20
> Nits/editorial comments:
>=20
> Section 1: This document uses an "IESG Ratification" process for some
> assignments.  This is not the same process as the "IESG Approval" process
> defined in RFC 5226.  As those names could be confused by a casual reader
> who is not strongly familiar with IANA processes, I suggest adding a
> statement that the "IESG Ratification" process is defined in this documen=
t
> and is not the same as the "IESG Approval" process in RFC 5226.  This cou=
ld
> be added after the sentence that cites RFC 5226.
>=20
> Section 1.4: It would be helpful to point out that there is no OUI assign=
ed
> for documentation purposes, but there are identifiers based on the IANA O=
UI
> that have been assigned for documentation purposes.
>=20
> In general, the use of the acronym IAB for Individual Address Block is
> unfortunate, but unavoidable, and this is clearly pointed out in the
> definition of the IAB acronym in section 1.2.  Nothing can or should be
> done about this.
>=20
> idnits 2.12.17 did not find any nits.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From d3e3e3@gmail.com  Sun Jun  9 11:06:53 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 891D021F8D10; Sun,  9 Jun 2013 11:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.275
X-Spam-Level: 
X-Spam-Status: No, score=-102.275 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cM0VhXJ5YODZ; Sun,  9 Jun 2013 11:06:52 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 655D521F8C40; Sun,  9 Jun 2013 11:06:52 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so909279oah.10 for <multiple recipients>; Sun, 09 Jun 2013 11:06:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xDvdhVwkMqFe+OuTSmaxE2l3nt0fcE/Io6HndvH9QcI=; b=P2YEQHDn21KeuPOI0MhISLF7sDw6a6DCdNobVLi+XDXQXAGpYH4JtF3IVe78Hweqgx 4wRymCZxdXe6JBNKeLCfqQjes34Bhk2AqN8qDk/xrEGtINwTU8rBfgBBs5d/WhknhVPI cOASMYzJA1rE6hmWeiorINRgdgknXLMVGDEu9NUolWDZ8Sv1S8YzeLC3fSZE4zA164jq q/YTrhkNQYjxjcWvPOXZR+JqXKWKaux7qd67M1aU1hilKuLitCF8I6VJpDNW0MnZq5Ye 3VK9Rm+PkdzlHLZdCpXZEwuHctDXiN7Enr3ttuO725/hXwZsFyHYqHQg2FoeU7hiEAKS 8/JA==
X-Received: by 10.60.84.143 with SMTP id z15mr5370775oey.30.1370801210507; Sun, 09 Jun 2013 11:06:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.12.65 with HTTP; Sun, 9 Jun 2013 11:06:30 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 9 Jun 2013 14:06:30 -0400
Message-ID: <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "joelja@bogus.com" <joelja@bogus.com>, General Area Review Team <gen-art@ietf.org>, "joe.abley@icann.org" <joe.abley@icann.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2013 18:06:53 -0000

Hi David,

On Sun, Jun 9, 2013 at 1:47 PM, Black, David <david.black@emc.com> wrote:
> The -03 version of this draft resolves all of the concerns raised by
> the Gen-ART review of the -02 version.

Thanks.

> Unfortunately, a serious typo/thinko snuck into the -03 version (been
> there, done that, myself).  Section 3.2 currently says:
>
>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-0E-00-42) to be used for documentation purposes.
>
> The parenthetical expansion of the protocol number is incorrect.
> The correct expansion uses -5E- instead of -0E-:

My apologies, you are correct. However, I believe that, in context,
the typo is pretty obvious.

>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-5E-00-42) to be used for documentation purposes.
>
> I strongly suggest submitting a -04 version of this draft to make
> the necessary single character correction (e.g., as opposed to using
> a RFC Editor Note for that purpose).

I defer entirely to JoelJaeggli, the sponsoring AD.

I'd be happy to submit a -04 or it seems to me it could easily be
fixed with an RFC Editor Note or at AUTH48 time. (Actually, it seems
likely to me that during IESG consideration, some other change will be
decided on and this can be fixed at the same time.)

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> --David
>
>> -----Original Message-----
>> From: Black, David
>> Sent: Wednesday, June 05, 2013 6:13 PM
>> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
>> Cc: Black, David; joelja@bogus.com; ietf@ietf.org
>> Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
>>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-eastlake-rfc5342bis-02
>> Reviewer: David L. Black
>> Review Date: June 5, 2013
>> IETF LC End Date: June 4, 2013
>>
>> Summary:
>> This draft is on the right track but has open issues, described in the review.
>>
>> This draft updates the IANA registered Ethernet parameters for IETF use,
>> including recording values assigned for documentation.  It also makes some
>> minor changes to IANA procedures.
>>
>> IANA should review this entire draft, not just its IANA Considerations
>> section;
>> Pearl Liang appears to have done that comprehensive review for IANA.
>>
>> Major issues: None
>>
>> Minor issues: One, the IANA review also found this issue.
>>
>> Section 3.2 states:
>>
>>       IANA will assign "00-00-0E-00-42" as the protocol number under the
>>       IANA OUI to be used for documentation purposes.
>>
>> IANA has not made this assignment, but this assignment request is not
>> recorded in the IANA Considerations section where IANA actions are
>> requested and recorded by IANA after they have been performed.  This
>> assignment needs to be added to the IANA Considerations section;
>> see item 5 in the IANA review.
>>
>> Nits/editorial comments:
>>
>> Section 1: This document uses an "IESG Ratification" process for some
>> assignments.  This is not the same process as the "IESG Approval" process
>> defined in RFC 5226.  As those names could be confused by a casual reader
>> who is not strongly familiar with IANA processes, I suggest adding a
>> statement that the "IESG Ratification" process is defined in this document
>> and is not the same as the "IESG Approval" process in RFC 5226.  This could
>> be added after the sentence that cites RFC 5226.
>>
>> Section 1.4: It would be helpful to point out that there is no OUI assigned
>> for documentation purposes, but there are identifiers based on the IANA OUI
>> that have been assigned for documentation purposes.
>>
>> In general, the use of the acronym IAB for Individual Address Block is
>> unfortunate, but unavoidable, and this is clearly pointed out in the
>> definition of the IAB acronym in section 1.2.  Nothing can or should be
>> done about this.
>>
>> idnits 2.12.17 did not find any nits.
>>
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>

From david.black@emc.com  Sun Jun  9 12:10:25 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E01B21F8FF8; Sun,  9 Jun 2013 12:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0S7HY1NjaRD; Sun,  9 Jun 2013 12:10:21 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 203B621F8FA4; Sun,  9 Jun 2013 12:10:20 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59J9uMc022128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Jun 2013 15:09:56 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 9 Jun 2013 15:09:50 -0400
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r59J9nP2020631; Sun, 9 Jun 2013 15:09:49 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Sun, 9 Jun 2013 15:09:49 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 9 Jun 2013 15:09:48 -0400
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-03
Thread-Index: Ac5lPCQkdinnaPkPQMKO9qA5DiYy8gACFpAw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712980CA213@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com> <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com>
In-Reply-To: <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "joelja@bogus.com" <joelja@bogus.com>, General Area Review Team <gen-art@ietf.org>, "joe.abley@icann.org" <joe.abley@icann.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2013 19:10:25 -0000

> > I strongly suggest submitting a -04 version of this draft to make
> > the necessary single character correction (e.g., as opposed to using
> > a RFC Editor Note for that purpose).
>
> I defer entirely to Joel Jaeggli, the sponsoring AD.

I'm happy to leave that decision up to Joel.

I'm concerned about readers who aren't as
cognizant of and comfortable/familiar with the relationships among
OUIs and the identifiers based on them as people like you and me.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Sunday, June 09, 2013 2:07 PM
> To: Black, David
> Cc: joe.abley@icann.org; General Area Review Team; joelja@bogus.com;
> ietf@ietf.org
> Subject: Re: Gen-ART review of draft-eastlake-rfc5342bis-03
>=20
> Hi David,
>=20
> On Sun, Jun 9, 2013 at 1:47 PM, Black, David <david.black@emc.com> wrote:
> > The -03 version of this draft resolves all of the concerns raised by
> > the Gen-ART review of the -02 version.
>=20
> Thanks.
>=20
> > Unfortunately, a serious typo/thinko snuck into the -03 version (been
> > there, done that, myself).  Section 3.2 currently says:
> >
> >    00-42 is a protocol number under the IANA OUI (that is,
> >    00-00-0E-00-42) to be used for documentation purposes.
> >
> > The parenthetical expansion of the protocol number is incorrect.
> > The correct expansion uses -5E- instead of -0E-:
>=20
> My apologies, you are correct. However, I believe that, in context,
> the typo is pretty obvious.
>=20
> >    00-42 is a protocol number under the IANA OUI (that is,
> >    00-00-5E-00-42) to be used for documentation purposes.
> >
> > I strongly suggest submitting a -04 version of this draft to make
> > the necessary single character correction (e.g., as opposed to using
> > a RFC Editor Note for that purpose).
>=20
> I defer entirely to JoelJaeggli, the sponsoring AD.
>=20
> I'd be happy to submit a -04 or it seems to me it could easily be
> fixed with an RFC Editor Note or at AUTH48 time. (Actually, it seems
> likely to me that during IESG consideration, some other change will be
> decided on and this can be fixed at the same time.)
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: Black, David
> >> Sent: Wednesday, June 05, 2013 6:13 PM
> >> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> >> Cc: Black, David; joelja@bogus.com; ietf@ietf.org
> >> Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
> >>
> >> I am the assigned Gen-ART reviewer for this draft. For background on
> >> Gen-ART, please see the FAQ at
> >>
> >> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>
> >> Please resolve these comments along with any other Last Call comments
> >> you may receive.
> >>
> >> Document: draft-eastlake-rfc5342bis-02
> >> Reviewer: David L. Black
> >> Review Date: June 5, 2013
> >> IETF LC End Date: June 4, 2013
> >>
> >> Summary:
> >> This draft is on the right track but has open issues, described in the
> review.
> >>
> >> This draft updates the IANA registered Ethernet parameters for IETF us=
e,
> >> including recording values assigned for documentation.  It also makes =
some
> >> minor changes to IANA procedures.
> >>
> >> IANA should review this entire draft, not just its IANA Considerations
> >> section;
> >> Pearl Liang appears to have done that comprehensive review for IANA.
> >>
> >> Major issues: None
> >>
> >> Minor issues: One, the IANA review also found this issue.
> >>
> >> Section 3.2 states:
> >>
> >>       IANA will assign "00-00-0E-00-42" as the protocol number under t=
he
> >>       IANA OUI to be used for documentation purposes.
> >>
> >> IANA has not made this assignment, but this assignment request is not
> >> recorded in the IANA Considerations section where IANA actions are
> >> requested and recorded by IANA after they have been performed.  This
> >> assignment needs to be added to the IANA Considerations section;
> >> see item 5 in the IANA review.
> >>
> >> Nits/editorial comments:
> >>
> >> Section 1: This document uses an "IESG Ratification" process for some
> >> assignments.  This is not the same process as the "IESG Approval" proc=
ess
> >> defined in RFC 5226.  As those names could be confused by a casual rea=
der
> >> who is not strongly familiar with IANA processes, I suggest adding a
> >> statement that the "IESG Ratification" process is defined in this docu=
ment
> >> and is not the same as the "IESG Approval" process in RFC 5226.  This =
could
> >> be added after the sentence that cites RFC 5226.
> >>
> >> Section 1.4: It would be helpful to point out that there is no OUI ass=
igned
> >> for documentation purposes, but there are identifiers based on the IAN=
A OUI
> >> that have been assigned for documentation purposes.
> >>
> >> In general, the use of the acronym IAB for Individual Address Block is
> >> unfortunate, but unavoidable, and this is clearly pointed out in the
> >> definition of the IAB acronym in section 1.2.  Nothing can or should b=
e
> >> done about this.
> >>
> >> idnits 2.12.17 did not find any nits.
> >>
> >> Thanks,
> >> --David
> >> ----------------------------------------------------
> >> David L. Black, Distinguished Engineer
> >> EMC Corporation, 176 South St., Hopkinton, MA  01748
> >> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> >> david.black@emc.com        Mobile: +1 (978) 394-7754
> >> ----------------------------------------------------
> >


From peter@akayla.com  Sun Jun  9 22:37:35 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E80221F896D; Sun,  9 Jun 2013 22:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQAnvgn0TM01; Sun,  9 Jun 2013 22:37:30 -0700 (PDT)
Received: from p3plsmtpa07-05.prod.phx3.secureserver.net (p3plsmtpa07-05.prod.phx3.secureserver.net [173.201.192.234]) by ietfa.amsl.com (Postfix) with ESMTP id 783B321F8607; Sun,  9 Jun 2013 22:37:30 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-05.prod.phx3.secureserver.net with  id mVdT1l00F1huGat01VdUhD; Sun, 09 Jun 2013 22:37:29 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>
Date: Sun, 9 Jun 2013 22:37:27 -0700
Message-ID: <03c601ce659c$98abe9f0$ca03bdd0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5lmC2m6gwvYZg7TOq4hiziFSg7Gw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-jabley-dnsext-eui48-eui64-rrtypes-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 05:37:35 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-jabley-dnsext-eui48-eui64-rrtypes-04
Reviewer: Peter Yee
Review Date: June-09-2013
IETF LC End Date: June-17-2013
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication as an Informational
RFC, but has nits that should be fixed before publication. [Ready with nits]

This draft defines DNS Resources Record Types for encoding IEEE 802 EUI-48
and EUI-64 addresses.

General: I am aware of the debate on the IETF mailing list as to whether
this draft could potentially harm user privacy.  I'm of the opinion that
this draft makes a useful specification of new DNS Resource Record Types.
Misuse of this specification and many others could harm privacy, but that
shouldn't necessarily dissuade us from publishing this draft.  The security
considerations cover the issues adequately.

Major issues:

Minor issues:

Nits:

Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and delete an
extraneous space before "Ethernet".

Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to "These"
and change "specification defines" to "specifications define".

Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".

Page 8, 1st paragraph, 1st sentence: change "behaviour" to "behavior".
Let's settle on the American variant of English for this draft. ;-)

Page 10, 3rd paragraph: as others have pointed out, having "the querier
already know some other permanent identifier" is security by obscurity and
is not advised.

		-Peter Yee




From prvs=1873a61d1e=magnus.westerlund@ericsson.com  Mon Jun 10 00:51:59 2013
Return-Path: <prvs=1873a61d1e=magnus.westerlund@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A2DD21F854D; Mon, 10 Jun 2013 00:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pcjtc2IIixWP; Mon, 10 Jun 2013 00:51:52 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id F3BC721F8519; Mon, 10 Jun 2013 00:51:51 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-9c-51b58595c4b0
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 8A.1F.15700.59585B15; Mon, 10 Jun 2013 09:51:49 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Jun 2013 09:51:49 +0200
Message-ID: <51B585A7.7060109@ericsson.com>
Date: Mon, 10 Jun 2013 09:52:07 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1370477514.4596.9052.camel@mightyatom> <51B1A95B.2030208@ericsson.com> <1370607960.4596.9114.camel@mightyatom> <51B1E8BD.80901@ericsson.com> <1370619602.4596.9175.camel@mightyatom>
In-Reply-To: <1370619602.4596.9175.camel@mightyatom>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUyM+Jvre7U1q2BBstarCwufjnCbnH8wA52 i6uvPrNYPNs4n8Vi6vLHLA6sHl9PtrN4LFnyk8njy+XPbAHMUdw2SYklZcGZ6Xn6dgncGbN3 9jEWXJCrmPbfu4HxiUQXIyeHhICJxJ1Jn9khbDGJC/fWs3UxcnEICZxilFh+ZgsrhLOcUWL2 61csIFW8AtoSZ+csB7NZBFQlvu/5xApiswlYSNz80cgGYosKBEsc2b4Zql5Q4uTMJ2C2iICa xOavDxhBhjILrGOU+LGsCaxBWCBMYt6WbiaIbYcZJSZt2Ad2EyfQfe/7Glkg7pOU2PKiHSzO LKAnMeVqCyOELS/RvHU2M4gtBHRdQ1MH6wRGoVlIls9C0jILScsCRuZVjOy5iZk56eWGmxiB gX1wy2/dHYynzokcYpTmYFES59XjXRwoJJCeWJKanZpakFoUX1Sak1p8iJGJgxNEcEk1MIqq VfHFeD+1rMxKDxN78chSxLnK+Pq289Hik4MWPGyK0NvMWSva9eun0smTgsWZkRsKxPL8UvPm n/BgdL2QsTH/h8jtlpsBO7VjWsW1BcxPXIjlMchftWa9Ws8vlsZXM9WfvvO6uvL7SeZQNgbb QyIeYdci7KbnPYpcNbHsskBBul/lG/X5SizFGYmGWsxFxYkA7ohWYD8CAAA=
Cc: General Area Review Team <gen-art@ietf.org>, IETF discussion <ietf@ietf.org>, "mmusic \(E-mail\)" <mmusic@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 07:51:59 -0000

On 2013-06-07 17:40, Elwyn Davies wrote:
> On Fri, 2013-06-07 at 16:05 +0200, Magnus Westerlund wrote:
> 
>>> Appendix F: I missed that the text/parameter format appeared in the
>>> examples for GET_PARAMETER and SET_PARAMETER. It isn't stated in the
>>> definitions of these methods what encodings are acceptable for the
>>> message bodies that may go with these methods and their responses.
>>
>> Exactly, that is intentional. These methods can use anything that has a
>> MIME type. Also it has HTTP's mechanisms for determining what formats
>> one supports.
>>
>>> Clearly the new text/parameter MIME format is one.  Is it the only one?
>>
>> It is the only one defined by IETF for this purpose. That is why it is
>> in the appendix so that RTSP users shall have something to define the
>> parameters they want in. However, they have to accept the limitations of
>> a basic text format.
>>
>>> I guess you could use a application/json or an XML format but I guess
>>> these would also either have to be called out explicitly in the method
>>> descriptions or put in as feature extensions.  This needs to be
>>> clarified in the method descriptions (s13).  The upshot of all this is
>>> that I think Appendix F needs to be pulled back into Section 20 as
>>> currently it is the only way to encode the message bodies.
>>
>> I can agree that the format negotiation for the bodies of
>> GET/SET_PARAMETER is not clear. I will look at proposing some
>> improvements of the text related to the handling of method bodies and
>> their format negotiation.
> Good. I don't see where the server tells what formats it accepts for
> either GET_PARAMETER or SET_PARAMETER.  Also the Accept spec doesn't say
> anything about SET_PARAMETER.  AFAICS the client could tell the server
> what formats it accepts as a side-effect of DESCRIBE but that's a bit
> arcane - and it is not clear how you would separate the formats for
> DESCRIBE from those for GET_PARAM and SET_PARAM.

Yes, I think this negotiation should happen on per methods basis.
>>
>> However, I am not pulling in Appendix F. It is an optional to use format
>> for parameter value pairs that can be used in these methods, it is not
>> required. Nor, does the specification define any parameters that are
>> transferred using this interface. The things that are in the appendix
>> are not core protocol, they represent either informational things, like
>> the examples and the state machine. The other appendices are normative
>> definitions of particular choices for things that can be combined or
>> used with RTSP, like RTP as media transport.
>>
> OK, it is possible to use GET_PARAM for basic requirements without using
> message bodies, so you can get away without defining a lowest common
> denominator format. However, the use of message bodies for SET_PARAM is
> RECOMMENDED so it seems a little odd not to ensure that server and
> client will have at least one format in common. (And its not as if we
> are dealing with a hugely complicated bit of spec for
> text/parameters! :-) ).  Then, given the example in GET_PARAMETER it
> seems sensible to advise implementing text/parameters as the default for
> GET_PARAM also.

Sure, I personally don't have any issue with making it at least SHOULD
implement text/parameters. But from my horizon a forward pointer with
the normative requirements is sufficient to accomplish that.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From prvs=28730c7565=magnus.westerlund@ericsson.com  Mon Jun 10 01:44:00 2013
Return-Path: <prvs=28730c7565=magnus.westerlund@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6052821F867B for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 01:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjKAgj2zAE62 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 01:43:54 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2425A21F861F for <gen-art@ietf.org>; Mon, 10 Jun 2013 01:43:53 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-a3-51b591c8c84a
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 5D.AB.18006.8C195B15; Mon, 10 Jun 2013 10:43:52 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Jun 2013 10:43:52 +0200
Message-ID: <51B591DB.3010700@ericsson.com>
Date: Mon, 10 Jun 2013 10:44:11 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUyM+Jvre6JiVsDDRZNN7a4dfMXm8XXnz9Y La6++sxi8W3zdUaLv+3MDqweB1fOYffYOesuu8eSJT+ZPA6uu8Ds8eXyZ7YA1ihum6TEkrLg zPQ8fbsE7oyOc/vYCo6FVKz7PoO5gXG5UxcjJ4eEgInEhjX/2CBsMYkL99YD2VwcQgKnGCWW 3V0J5SxnlNj+pJEZpIpXQFvizItnLCA2i4CqxMulZxlBbDYBC4mbPxrBJokKBEsc2b6ZBaJe UOLkzCdgtoiAtcSVy13MIEOZBf4yStz6PhesWVjAUuLe7zlQ2yYySizZ8wYswSngI7H98j4m iPskJba8aGcHsZkF9CSmXG1hhLDlJZq3zga7TgjouoamDtYJjEKzkCyfhaRlFpKWBYzMqxjZ cxMzc9LLjTYxAoP94JbfqjsY75wTOcQozcGiJM6rx7s4UEggPbEkNTs1tSC1KL6oNCe1+BAj EwcniOCSamAM5hFevODVZoZfUdN85bQOeVqHLn7KpLp77pWm1hOyjDGOggLTLFpbUgQ4E9ak 1M5xPXSw4pNBc2/ZJ3NG6dIfJ399ca/7zh1hIqJ0ip2r0i5VZlvIi9Olyyavnhh45J6gv7Nf l54Mx5y7rE5LEtOYIhKZWXYdKo4JL74VNL+1qqqx3IY9RomlOCPRUIu5qDgRAGS3gS5JAgAA
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 08:44:00 -0000

Hi,

Can you please put the WG in the loop regarding these comments. Ray, can
you forward your reply as that contains all the information to the WG. I
think it is important we take the discussion of some of the issues,
especially regarding change control and the IANA policy in a public forum.

Cheers

Magnus

On 2013-06-10 10:33, Brandenburg, R. (Ray) van wrote:
> Hi Dan,
> 
> Many thanks for your very thorough review. 
> 
> Before responding to your comments in detail, let me give you some background on how we handle the relationship with the ETSI document: Exactly how we should deal with the existing ETSI spec has been discussed at length in AVTCORE, both on- and offlist. As you can see in the earlier versions of the draft, the document used to extend the ETSI document, referencing it where necessary and including sections that describe this relationship. In the end, the WG consensus was that the IETF draft should be the normative spec for the XR block and AVTCORE should have full change control over it. We therefore removed most references to the ETSI spec, and instead started a Work Item in ETSI to change TS 183 063 to point to the IETF draft and remove all normative statements (apart from extending the IETF-defined block with three new SPST values). 
> 
> The current idea is therefore that since the ETSI spec will be referencing the IETF spec, instead of the other way around, that there is no need to describe this relationship in the IETF draft. The IETF spec is the normative 'base' spec, and ETSI is just describing a way to use it within an IPTV system, including three additional SPST values specific to that scenario. 
> 
> Personally, I agree with the WG consensus that this is the 'cleanest' way to handle it, resulting in backwards compatibility with older versions of the ETSI document as well as have full change control in IETF. 
> 
> Please see inline for your comments. 
> 
> Best regards,
> 
> Ray
> 
> 
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: zondag 9 juni 2013 9:53
> To: General Area Review Team
> Cc: draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: Gen-ART review of draft-ietf-avtcore-idms-09
> 
> (resending, I mis-spelled .all address at the first try)
> 
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at
> 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments you may receive.
> 
> Document: draft-ietf-avtcore-idms-09
> Reviewer: Dan Romascanu
> Review Date: 6/6/13
> IETF LC End Date: 6/11/13
> IESG Telechat date: 
> 
> Summary:
> 
> Not Ready
> 
> Major issues:
> 
> 1. This document is tightly connected with the ETSI specification TS 183 063. However this relation is mentioned only in a couple of places and does not describe the complexity of the relation. Moreover, the relation itself seems problematic. 
> 
> The I-D uses some of the inter-destination media techniques described by ETSI TS 183 063. For example Section 7 replicates part of the content of Annex W of the ETSI document. It does it partially however, and with some modifications, as only the content definition and behavior of the transmitters and receivers for SPST=1 were taken from Annex W, while the content and behavior for SPST=2-4 are marked as 'defined by ETSI TISPAN'. The ETSI document details what happens with the fields when SPST=2-4. This will result in the RTCP XR block for IDMS to be defined in two places - part in this IETF document (if approved), the rest in the ETSI document (to be modified accordingly in the future). For some period of time the same fields will be defined in two places. This seems broken. 
> 
> [Ray: See my comments above. The ETSI document will be changed to point to the IETF spec. Does this solve your issue? In addition, we could create an IANA registry for SPST values, although I personally believe this to not be necessary]
> 
> 2. The note to the RFC Editor in section 14.2 states: 
> 
>    14.2.  RTCP XR IDMS Report Block
> 
>    This document assigns the block type value 12 in the IANA "RTCP XR
>    Block Type Registry" to the RTCP XR IDMS Report Block.
> 	
>    [Note to RFC Editor: this block type value is currently assigned to
>    [TS183063].  This document replaces [TS183063] as the normative
>    specification of the RTCP XR IDMS Report Block.  Upon publication of
>    this document as RFC, [TS183063] will be changed to reflect this.
> 
> The first statement is not accurate. Value 12 is not a new assignment, 12 was already assigned by ETSI, this document asks to change the assignment of value 12 from the RTCP XR Block Type for reporting IDMS information to the IETF defined RTCP XR IDMS Report Block. 
> 
> [Ray: Hmm, I'm not sure. I checked with IANA and they don't see a problem in the current wording. I think this is fundamentally a question of describing the 'soll' situation versus describing the process of getting from 'ist' to 'soll'. Once the ETSI doc has been updated, your proposed sentence  would no longer be necessary, right?]
> 
> This change is however partial as described previously, as the content of the fields and behavior for SPST = 2-4 remain under ETSI control. Moreover, it is not clear who has further control for other new values, as SPST = 5-15 show as 'reserved for future use in both documents'. The IANA section does not define or refer an IANA registry and the policy for adding and approving new values for SPST. 
> 
> This solution is not clean. Only one organization should have control upon the definition of one single RTCP XR block type. Either the IETF should make the overleaping parts of the  document Informational and reflect the content of the ETSI document, or should take control over the whole block. 
> 
> [Ray: See my earlier comments: IETF will have full control, ETSI will just be extending it.] 
> 
> 3. The relation with the ETSI specification TS 183 063 should have been described clearly from the beginning of the document. 
> 
> [Ray: See my earlier comment. Since the IETF draft will be that normative spec that ETSI will be referencing, I believe this relationship should be described in ETSI, not in IETF].
> 
> Minor issues:
> 
> 1. The version of the block definition is set to V=2 which is the same as in the ETSI specification. Were versions 0 and 1 already used by ETSI? If this is the case a note should be made. 
> 
> [Ray: This part of the header is defined by RFC3611, and is specified to be set to 2 to refer to the version of RTP]
> 
> 2. In Section 7: 
> 
>    Reserved bits (Resrv): 3 bits.  These bits are reserved for future
>    definition.  In the absence of such a definition, the bits in this
>    field MUST be set to zero and MUST be ignored by the receiver.
> 
> s/MUST be set to zero/MUST be set to zero at transmission/
> 
> [Ray: Thanks, I will update the draft]
> 
> 3. In Section 7: 
> 
>    Reserved bits (Resrv): 25 bits.  These bits are reserved for future
>    use and SHALL be set to 0.
> 
> s/ SHALL be set to 0/ MUST be set to zero at transmission and MUST be ignored by the receiver/
> 
> [Ray: Thanks, I will update the draft]
> 
> 4. In Section 7: 
> 
>    When
>    reporting on an RTP packet which is one of several consecutive RTP
>    packets having equal timestamps, an SC SHOULD report on the RTP
>    packet it received with the lowest sequence number.
> 
> Why a SHOULD here and not a MUST? If there are any cases of exception they need to be detailed.
> 
> [Ray: Implementations might be optimized for specific scenarios by reporting on specific packets as indicated by e.g. an out-of-band signal]
> 
> 5. In Section 8: 
> 
>    Because RTP
>    timestamps do wrap around, the sender of this packet SHOULD use
>    recent values, i.e. choose NTP timestamps that reflect current time
>    and not too far in the future or in the past. 
> 
> Why a SHOULD here and not a MUST? If there are any cases of exception they need to be detailed.
> 
> [Ray: I will check with my co-authors]
> 
> 6. In Section 8: 
> 
>    This SHOULD relate to the first
>    arriving RTP packet containing this particular RTP timestamp, in case
>    multiple RTP packets contain the same RTP timestamp.
> 
> Why a SHOULD here and not a MUST? If there are any cases of exception they need to be detailed.
> 
> [Ray: I will check with my co-authors]
> 
> 7. In Section 8: 
> 
>    The timestamp is formatted based on the NTP
>    timestamp format as specified in [RFC5905].  If this field is empty,
>    then it SHALL be set to 0.  This field MAY be left empty if none or
>    only one of the receivers reported on presentation timestamps.
> 
> Why a MAY here? Especially for the case when none of the receivers reported, what content can be set there but 0 ?
> 
> [Ray: I believe it should be up to the implementation to decide how it wants to handle the case of there being only one receiver who reported on presentation timestamps]. 
> 
> 8: The reference: 
> 
> [TS183063]
>               "IMS-based IPTV stage 3 specification, TS 183 063 v3.4.1",
>               June 2010.
> 
> V3.4.1 is not the latest release. Is this intentional? I found at least one more recent release dated 2011 and numbered 3.5.2 - I do not know if there is any diff in the relevant content, but pointing to the most updated review seems appropriate.
> 
> [Ray: Thanks for noticing, I will update the reference to the latest ETSI release]. 
> 
> 9: Did this document undergo an SDP directorate review? If not I believe that one would be necessary, as a new SDP Attribute is being defined. 
>  
> [Ray: Yes, an SDP directorate review has been carried out]. 
> 
> Nits/editorial comments:
> 
> 1. typo in the last paragraph of section 5 - s/nessecary/necessary/
> 
> 2. in section 8 expand PT as Packet Type
> 
> 3. typo in the first paragraph of section 11 - s/mutli/multi/
> 
> [Ray: Thanks, I will update the draft]
> 
> Regards,
> 
> Dan
> 
> [Ray: Again, many thanks for the thorough review!]
> 
> 
> 
> This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/emaildisclaimer
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From prvs=78731f4a8f=christer.holmberg@ericsson.com  Mon Jun 10 02:17:44 2013
Return-Path: <prvs=78731f4a8f=christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA85521F85E6 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 02:17:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.048
X-Spam-Level: 
X-Spam-Status: No, score=-6.048 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WBLLDxJPWjFh for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 02:17:36 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8F25521F8B90 for <gen-art@ietf.org>; Mon, 10 Jun 2013 02:16:46 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-c7-51b5997df466
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 4F.B1.18006.D7995B15; Mon, 10 Jun 2013 11:16:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 11:16:45 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-ietf-avtcore-6222bis-03
Thread-Index: Ac5luxdWTPgVtsT2RrKnG3rZqnZqqg==
Date: Mon, 10 Jun 2013 09:16:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C386F68@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C386F68ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUyM+JvrW7tzK2BBi93KVkcnb2SyeLqq88s DkweS5b8ZPL4cvkzWwBTFLdNUmJJWXBmep6+XQJ3Rv+2x2wFx9wrvn7+zdTAuNe2i5GTQ0LA ROL333VsELaYxIV764FsLg4hgcOMEt8PHWWFcJYwSiy738zexcjBwSZgIdH9TxukQURAU2Lu irdMIDazQKrEhfvnwWxhAXOJ9WcnMUPU2EgcOLiDEcLWkzh56BMriM0ioCrx8et2sDivgK/E 1b2bwHoZgY74fmoN1ExxiVtP5jNBHCcgsWTPeWYIW1Ti5eN/rCDnSAgoSizvl4Moz5dYdeoo 1EhBiZMzn7BMYBSehWTSLCRls5CUQcR1JBbs/sQGYWtLLFv4mhnGPnPgMROy+AJG9lWM7LmJ mTnp5UabGIExcnDLb9UdjHfOiRxilOZgURLn1eNdHCgkkJ5YkpqdmlqQWhRfVJqTWnyIkYmD E0RwSTUwrvL7NPWYabplb1bDzU3dm1W3pF6K2bT4dtOuCxa3vv61izEy2M09nWe2jhQPt5RA jNjNv91PROSz9S8uXH74nPWMxFy95R5tt2ymHA+I3rVU5p1UX4F/8NXgzY1ZR+YsurbOY8u9 S988zximC0Zw/VBeM5lv3q9pnprXMupsi5ZM35atPTnUWomlOCPRUIu5qDgRAPbeZDJkAgAA
Cc: "draft-ietf-avtcore-6222bis.all@tools.ietf.org" <draft-ietf-avtcore-6222bis.all@tools.ietf.org>
Subject: [Gen-art] Genart review of draft-ietf-avtcore-6222bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 09:17:45 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C386F68ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>



Document:                         draft-ietf-avtcore-6222bis-03



Reviewer:                           Christer Holmberg



Review Date:                     10 June 2013



IETF LC End Date:             11 June 2013



IETF Telechat Date:         N/A



Summary:  There is a minor issue, described below, that I think should be c=
larified before the document is published.



Major Issues: None



Minor Issues:



Section 4.1 says:



   "The RTCP CNAME can be either persistent across different RTP sessions

   for an RTP endpoint or unique per session, meaning that an RTP

   endpoint chooses a different RTCP CNAME for each RTP session."



...and:



   "An RTP endpoint that is emitting multiple related RTP streams that

   require synchronization at the other endpoint(s) MUST use the same

   RTCP CNAME for all streams that are to be synchronized.  This

   requires a short-term persistent RTCP CNAME that is common across

   several RTP streams, and potentially across several related RTP

   sessions.  A common example of such use occurs when lip-syncing audio

   and video streams in a multimedia session, where a single participant

   has to use the same RTCP CNAME for its audio RTP session and for its

   video RTP session.  Another example might be to synchronize the

   layers of a layered audio codec, where the same RTCP CNAME has to be

   used for each layer."



...etc.



The text talks about the CNAME being unique within an RTP session, or to sp=
an over multiple RTP sessions, but it seems to omit that, *within* an RTP s=
ession, you can also use *different* CNAME values, if e.g. there is no sync=
hronization requirement between the RTP streams.





Editorial nits: None



Best regards,



Christer


--_000_7594FB04B1934943A5C02806D1A2204B1C386F68ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	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;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-avtcore-6222bis-03<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Reviewer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Review Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 10 June 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11 June 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF Telechat Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; N/A<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:&nbsp; There is a minor issue, described =
below, that I think should be clarified before the document is published.<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor Issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Section 4.1 says:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; &#8220;The RTCP CNAME can be either =
persistent across different RTP sessions<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; for an RTP endpoint or unique per se=
ssion, meaning that an RTP<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; endpoint chooses a different RTCP CN=
AME for each RTP session.&#8221;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&#8230;and:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; &#8220;An RTP endpoint that is emitt=
ing multiple related RTP streams that<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; require synchronization at the other=
 endpoint(s) MUST use the same<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; RTCP CNAME for all streams that are =
to be synchronized.&nbsp; This<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; requires a short-term persistent RTC=
P CNAME that is common across<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; several RTP streams, and potentially=
 across several related RTP<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; sessions.&nbsp; A common example of =
such use occurs when lip-syncing audio<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; and video streams in a multimedia se=
ssion, where a single participant<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; has to use the same RTCP CNAME for i=
ts audio RTP session and for its<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; video RTP session.&nbsp; Another exa=
mple might be to synchronize the<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; layers of a layered audio codec, whe=
re the same RTCP CNAME has to be<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; used for each layer.&#8221;<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&#8230;etc.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The text talks about the CNAME being unique withi=
n an RTP session, or to span over multiple RTP sessions, but it seems to om=
it that, *<b>within</b>* an RTP session, you can also use *<b>different</b>=
* CNAME values, if e.g. there is no
 synchronization requirement between the RTP streams.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Editorial nits: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Best regards,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Christer<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C386F68ESESSMB209erics_--

From ron.even.tlv@gmail.com  Mon Jun 10 02:25:55 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A94F121F842A for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 02:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mZyXVlREF6Vd for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 02:25:52 -0700 (PDT)
Received: from mail-ea0-x22d.google.com (mail-ea0-x22d.google.com [IPv6:2a00:1450:4013:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id D6A6521F8C40 for <gen-art@ietf.org>; Mon, 10 Jun 2013 02:25:13 -0700 (PDT)
Received: by mail-ea0-f173.google.com with SMTP id g15so5076478eak.32 for <gen-art@ietf.org>; Mon, 10 Jun 2013 02:25:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=wx05d6XfxewoneFMv5VKuQjjIo46bHdgsYbF1LdGFTQ=; b=tH4TTsFb1Ln7IYsjqw5wzz4GWW307zimgZ4ZjbCoqfrdJn5ieJ29+XtvB5vc4yL7f9 JnXpKOvXdf84BPqdzsBv72/a4CYyjV/pEI98jRUQqZA+aupT5Nn8vJuu8+y1RDT67SXE YFXmPIK+5j9wLIYLFFH0V7pGawenhOJOascJLQS/bCfpxYeXVi84uio9NOe/K2mEB1ka +sGJgQVEyhhQugrZmRsyqo3IVDjUq5TTZ/kSdVbGhEVPvgxAhhAcrKstO/4eUaO5SzUj Pyo2xUujJkktw4znhdezELKY9hTl4F3tAUODqPdtcjloXdOOhOmh4pHPSUfNj0lFFQdw a1hQ==
X-Received: by 10.14.212.66 with SMTP id x42mr10202581eeo.81.1370856312561; Mon, 10 Jun 2013 02:25:12 -0700 (PDT)
Received: from RoniE ([109.64.225.31]) by mx.google.com with ESMTPSA id u11sm21724823eev.12.2013.06.10.02.25.09 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 10 Jun 2013 02:25:11 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>, "'Brandenburg, R. \(Ray\) van'" <ray.vanbrandenburg@tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <51B591DB.3010700@ericsson.com>
In-Reply-To: <51B591DB.3010700@ericsson.com>
Date: Mon, 10 Jun 2013 12:23:49 +0300
Message-ID: <057401ce65bc$39d28cc0$ad77a640$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI1I74918qhRUFB8eBFSTppcpI+AgIH8GiFAdBn13GYQmjm4A==
Content-Language: en-us
Cc: 'General Area Review Team' <gen-art@ietf.org>, draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 09:25:55 -0000

Hi,
I think that what Ray is saying is that the relation between ETSI =
document
and this document in the IANA section were discussed at length at the
AVTcore WG.  Keith insisted that the ETSI document will reflect that the
IETF have change control and should reference the text in the IETF =
document.
As far as I know this happened, we went to a lot of co-ordination to put =
the
update in ETSI.
What I think is missing is the reference to the latest etsi document =
that
reflect this change. I assume that it is a chicken and egg problem so if
ETSI 183 063 is waiting for this document it will be good to have the
reference as informational one since the IETF document is the normative =
one
or have the reference with no specific version since the latest will =
always
be the one to use.=20
Roni

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: 10 June, 2013 11:44 AM
> To: Brandenburg, R. (Ray) van
> Cc: Romascanu, Dan (Dan); General Area Review Team; =
draft-ietf-avtcore-
> idms.all@tools.ietf.org; Roni Even (ron.even.tlv@gmail.com)
> Subject: Re: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
> Hi,
>=20
> Can you please put the WG in the loop regarding these comments. Ray, =
can
> you forward your reply as that contains all the information to the WG. =
I
think
> it is important we take the discussion of some of the issues, =
especially
> regarding change control and the IANA policy in a public forum.
>=20
> Cheers
>=20
> Magnus
>=20
> On 2013-06-10 10:33, Brandenburg, R. (Ray) van wrote:
> > Hi Dan,
> >
> > Many thanks for your very thorough review.
> >
> > Before responding to your comments in detail, let me give you some
> background on how we handle the relationship with the ETSI document:
> Exactly how we should deal with the existing ETSI spec has been =
discussed
at
> length in AVTCORE, both on- and offlist. As you can see in the earlier
versions
> of the draft, the document used to extend the ETSI document, =
referencing
it
> where necessary and including sections that describe this =
relationship. In
the
> end, the WG consensus was that the IETF draft should be the normative =
spec
> for the XR block and AVTCORE should have full change control over it. =
We
> therefore removed most references to the ETSI spec, and instead =
started a
> Work Item in ETSI to change TS 183 063 to point to the IETF draft and
remove
> all normative statements (apart from extending the IETF-defined block =
with
> three new SPST values).
> >
> > The current idea is therefore that since the ETSI spec will be
referencing
> the IETF spec, instead of the other way around, that there is no need =
to
> describe this relationship in the IETF draft. The IETF spec is the
normative
> 'base' spec, and ETSI is just describing a way to use it within an =
IPTV
system,
> including three additional SPST values specific to that scenario.
> >
> > Personally, I agree with the WG consensus that this is the =
'cleanest'
way to
> handle it, resulting in backwards compatibility with older versions of =
the
ETSI
> document as well as have full change control in IETF.
> >
> > Please see inline for your comments.
> >
> > Best regards,
> >
> > Ray
> >
> >
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: zondag 9 juni 2013 9:53
> > To: General Area Review Team
> > Cc: draft-ietf-avtcore-idms.all@tools.ietf.org
> > Subject: Gen-ART review of draft-ietf-avtcore-idms-09
> >
> > (resending, I mis-spelled .all address at the first try)
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call =
comments
> you may receive.
> >
> > Document: draft-ietf-avtcore-idms-09
> > Reviewer: Dan Romascanu
> > Review Date: 6/6/13
> > IETF LC End Date: 6/11/13
> > IESG Telechat date:
> >
> > Summary:
> >
> > Not Ready
> >
> > Major issues:
> >
> > 1. This document is tightly connected with the ETSI specification TS =
183
063.
> However this relation is mentioned only in a couple of places and does =
not
> describe the complexity of the relation. Moreover, the relation itself
seems
> problematic.
> >
> > The I-D uses some of the inter-destination media techniques =
described by
> ETSI TS 183 063. For example Section 7 replicates part of the content =
of
> Annex W of the ETSI document. It does it partially however, and with =
some
> modifications, as only the content definition and behavior of the
transmitters
> and receivers for SPST=3D1 were taken from Annex W, while the content =
and
> behavior for SPST=3D2-4 are marked as 'defined by ETSI TISPAN'. The =
ETSI
> document details what happens with the fields when SPST=3D2-4. This =
will
> result in the RTCP XR block for IDMS to be defined in two places - =
part in
this
> IETF document (if approved), the rest in the ETSI document (to be =
modified
> accordingly in the future). For some period of time the same fields =
will
be
> defined in two places. This seems broken.
> >
> > [Ray: See my comments above. The ETSI document will be changed to
> > point to the IETF spec. Does this solve your issue? In addition, we
> > could create an IANA registry for SPST values, although I personally
> > believe this to not be necessary]
> >
> > 2. The note to the RFC Editor in section 14.2 states:
> >
> >    14.2.  RTCP XR IDMS Report Block
> >
> >    This document assigns the block type value 12 in the IANA "RTCP =
XR
> >    Block Type Registry" to the RTCP XR IDMS Report Block.
> >
> >    [Note to RFC Editor: this block type value is currently assigned =
to
> >    [TS183063].  This document replaces [TS183063] as the normative
> >    specification of the RTCP XR IDMS Report Block.  Upon publication =
of
> >    this document as RFC, [TS183063] will be changed to reflect this.
> >
> > The first statement is not accurate. Value 12 is not a new =
assignment,
12
> was already assigned by ETSI, this document asks to change the =
assignment
> of value 12 from the RTCP XR Block Type for reporting IDMS information =
to
> the IETF defined RTCP XR IDMS Report Block.
> >
> > [Ray: Hmm, I'm not sure. I checked with IANA and they don't see a
> > problem in the current wording. I think this is fundamentally a
> > question of describing the 'soll' situation versus describing the
> > process of getting from 'ist' to 'soll'. Once the ETSI doc has been
> > updated, your proposed sentence  would no longer be necessary, =
right?]
> >
> > This change is however partial as described previously, as the =
content
of
> the fields and behavior for SPST =3D 2-4 remain under ETSI control.
Moreover, it
> is not clear who has further control for other new values, as SPST =3D =
5-15
show
> as 'reserved for future use in both documents'. The IANA section does =
not
> define or refer an IANA registry and the policy for adding and =
approving
new
> values for SPST.
> >
> > This solution is not clean. Only one organization should have =
control
upon
> the definition of one single RTCP XR block type. Either the IETF =
should
make
> the overleaping parts of the  document Informational and reflect the
content
> of the ETSI document, or should take control over the whole block.
> >
> > [Ray: See my earlier comments: IETF will have full control, ETSI =
will
> > just be extending it.]
> >
> > 3. The relation with the ETSI specification TS 183 063 should have =
been
> described clearly from the beginning of the document.
> >
> > [Ray: See my earlier comment. Since the IETF draft will be that
normative
> spec that ETSI will be referencing, I believe this relationship should =
be
> described in ETSI, not in IETF].
> >
> > Minor issues:
> >
> > 1. The version of the block definition is set to V=3D2 which is the =
same
as in
> the ETSI specification. Were versions 0 and 1 already used by ETSI? If
this is
> the case a note should be made.
> >
> > [Ray: This part of the header is defined by RFC3611, and is =
specified
> > to be set to 2 to refer to the version of RTP]
> >
> > 2. In Section 7:
> >
> >    Reserved bits (Resrv): 3 bits.  These bits are reserved for =
future
> >    definition.  In the absence of such a definition, the bits in =
this
> >    field MUST be set to zero and MUST be ignored by the receiver.
> >
> > s/MUST be set to zero/MUST be set to zero at transmission/
> >
> > [Ray: Thanks, I will update the draft]
> >
> > 3. In Section 7:
> >
> >    Reserved bits (Resrv): 25 bits.  These bits are reserved for =
future
> >    use and SHALL be set to 0.
> >
> > s/ SHALL be set to 0/ MUST be set to zero at transmission and MUST =
be
> > ignored by the receiver/
> >
> > [Ray: Thanks, I will update the draft]
> >
> > 4. In Section 7:
> >
> >    When
> >    reporting on an RTP packet which is one of several consecutive =
RTP
> >    packets having equal timestamps, an SC SHOULD report on the RTP
> >    packet it received with the lowest sequence number.
> >
> > Why a SHOULD here and not a MUST? If there are any cases of =
exception
> they need to be detailed.
> >
> > [Ray: Implementations might be optimized for specific scenarios by
> > reporting on specific packets as indicated by e.g. an out-of-band
> > signal]
> >
> > 5. In Section 8:
> >
> >    Because RTP
> >    timestamps do wrap around, the sender of this packet SHOULD use
> >    recent values, i.e. choose NTP timestamps that reflect current =
time
> >    and not too far in the future or in the past.
> >
> > Why a SHOULD here and not a MUST? If there are any cases of =
exception
> they need to be detailed.
> >
> > [Ray: I will check with my co-authors]
> >
> > 6. In Section 8:
> >
> >    This SHOULD relate to the first
> >    arriving RTP packet containing this particular RTP timestamp, in =
case
> >    multiple RTP packets contain the same RTP timestamp.
> >
> > Why a SHOULD here and not a MUST? If there are any cases of =
exception
> they need to be detailed.
> >
> > [Ray: I will check with my co-authors]
> >
> > 7. In Section 8:
> >
> >    The timestamp is formatted based on the NTP
> >    timestamp format as specified in [RFC5905].  If this field is =
empty,
> >    then it SHALL be set to 0.  This field MAY be left empty if none =
or
> >    only one of the receivers reported on presentation timestamps.
> >
> > Why a MAY here? Especially for the case when none of the receivers
> reported, what content can be set there but 0 ?
> >
> > [Ray: I believe it should be up to the implementation to decide how =
it
> wants to handle the case of there being only one receiver who reported =
on
> presentation timestamps].
> >
> > 8: The reference:
> >
> > [TS183063]
> >               "IMS-based IPTV stage 3 specification, TS 183 063 =
v3.4.1",
> >               June 2010.
> >
> > V3.4.1 is not the latest release. Is this intentional? I found at =
least
one more
> recent release dated 2011 and numbered 3.5.2 - I do not know if there =
is
any
> diff in the relevant content, but pointing to the most updated review
seems
> appropriate.
> >
> > [Ray: Thanks for noticing, I will update the reference to the latest
ETSI
> release].
> >
> > 9: Did this document undergo an SDP directorate review? If not I =
believe
> that one would be necessary, as a new SDP Attribute is being defined.
> >
> > [Ray: Yes, an SDP directorate review has been carried out].
> >
> > Nits/editorial comments:
> >
> > 1. typo in the last paragraph of section 5 - s/nessecary/necessary/
> >
> > 2. in section 8 expand PT as Packet Type
> >
> > 3. typo in the first paragraph of section 11 - s/mutli/multi/
> >
> > [Ray: Thanks, I will update the draft]
> >
> > Regards,
> >
> > Dan
> >
> > [Ray: Again, many thanks for the thorough review!]
> >
> >
> >
> > This e-mail and its contents are subject to the DISCLAIMER at
> > http://www.tno.nl/emaildisclaimer
> >
>=20
>=20
> --
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------


From dromasca@avaya.com  Mon Jun 10 03:22:14 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F88921F8B98 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 03:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.799
X-Spam-Level: 
X-Spam-Status: No, score=-102.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Ofu2CbP7kMR for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 03:22:09 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECAA21F8825 for <gen-art@ietf.org>; Mon, 10 Jun 2013 03:22:08 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAPOntVHGmAcF/2dsb2JhbABagmghMEm+P34WdIIjAQEBAQIBEigtCwIFBQcEAgEIDQQDAQEBCxQJByERFAkIAQEEAQkEBQgTB4dZAwkGAQudCpJTDYg7F4xbgSuBATEHBoJ5YQOVWAGDEIUZhVyFJIMPgXE2
X-IronPort-AV: E=Sophos;i="4.87,836,1363147200"; d="scan'208";a="15406080"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 10 Jun 2013 06:22:05 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Jun 2013 06:20:37 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 06:22:04 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>, "General Area Review Team" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5A=
Date: Mon, 10 Jun 2013 10:22:03 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 10:22:14 -0000

Hi Ray,

Thank you for the detailed answer.=20

See in-line.=20

Regards,

Dan




> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 11:33 AM
> To: Romascanu, Dan (Dan); General Area Review Team
> Cc: draft-ietf-avtcore-idms.all@tools.ietf.org; Roni Even
> (ron.even.tlv@gmail.com)
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
> Hi Dan,
>=20
> Many thanks for your very thorough review.
>=20
> Before responding to your comments in detail, let me give you some
> background on how we handle the relationship with the ETSI document:
> Exactly how we should deal with the existing ETSI spec has been
> discussed at length in AVTCORE, both on- and offlist. As you can see in
> the earlier versions of the draft, the document used to extend the ETSI
> document, referencing it where necessary and including sections that
> describe this relationship. In the end, the WG consensus was that the
> IETF draft should be the normative spec for the XR block and AVTCORE
> should have full change control over it. We therefore removed most
> references to the ETSI spec, and instead started a Work Item in ETSI to
> change TS 183 063 to point to the IETF draft and remove all normative
> statements (apart from extending the IETF-defined block with three new
> SPST values).
>=20
[[DR]] Thank you for the clarification information. This is very useful. Ca=
n you tell what is the status of the work item in ETSI?=20

> The current idea is therefore that since the ETSI spec will be
> referencing the IETF spec, instead of the other way around, that there
> is no need to describe this relationship in the IETF draft. The IETF
> spec is the normative 'base' spec, and ETSI is just describing a way to
> use it within an IPTV system, including three additional SPST values
> specific to that scenario.
[[DR]] I disagree that there is no need to describe this relationship on th=
e IETF draft. As control for the XR block was previously in ETSI and will n=
ow be transferred to the IETF we should assume that there are implementers =
and deployments who know about the older ETSI specification. You need a sec=
tions that describes the relationship with the ETSI document, and describes=
 the changes relative to that version - same as would have been written if =
there was an RFC that was updated or made obsolete by this document.=20

Moreover, the current document is not consistent, as it still keeps a norma=
tive reference to the older (not even the latest version) ETSI document. Th=
is will be not needed any longer, an informational reference would be suffi=
cient. =20

>=20
> Personally, I agree with the WG consensus that this is the 'cleanest'
> way to handle it, resulting in backwards compatibility with older
> versions of the ETSI document as well as have full change control in
> IETF.
>=20
> Please see inline for your comments.
>=20
> Best regards,
>=20
> Ray
>=20
>=20
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: zondag 9 juni 2013 9:53
> To: General Area Review Team
> Cc: draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
> (resending, I mis-spelled .all address at the first try)
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-avtcore-idms-09
> Reviewer: Dan Romascanu
> Review Date: 6/6/13
> IETF LC End Date: 6/11/13
> IESG Telechat date:
>=20
> Summary:
>=20
> Not Ready
>=20
> Major issues:
>=20
> 1. This document is tightly connected with the ETSI specification TS 183
> 063. However this relation is mentioned only in a couple of places and
> does not describe the complexity of the relation. Moreover, the relation
> itself seems problematic.
>=20
> The I-D uses some of the inter-destination media techniques described by
> ETSI TS 183 063. For example Section 7 replicates part of the content of
> Annex W of the ETSI document. It does it partially however, and with
> some modifications, as only the content definition and behavior of the
> transmitters and receivers for SPST=3D1 were taken from Annex W, while th=
e
> content and behavior for SPST=3D2-4 are marked as 'defined by ETSI
> TISPAN'. The ETSI document details what happens with the fields when
> SPST=3D2-4. This will result in the RTCP XR block for IDMS to be defined
> in two places - part in this IETF document (if approved), the rest in
> the ETSI document (to be modified accordingly in the future). For some
> period of time the same fields will be defined in two places. This seems
> broken.
>=20
> [Ray: See my comments above. The ETSI document will be changed to point
> to the IETF spec. Does this solve your issue? In addition, we could
> create an IANA registry for SPST values, although I personally believe
> this to not be necessary]
>=20
[[DR]] Eventually it will solve the issue, but the situation is murky in th=
e interim. I believe that creating a registry would be good, because it pro=
vides a way to describe the interim situation, and also because we do not k=
now yet for sure who may use the values 5-15 in the future.=20

> 2. The note to the RFC Editor in section 14.2 states:
>=20
>    14.2.  RTCP XR IDMS Report Block
>=20
>    This document assigns the block type value 12 in the IANA "RTCP XR
>    Block Type Registry" to the RTCP XR IDMS Report Block.
>=20
>    [Note to RFC Editor: this block type value is currently assigned to
>    [TS183063].  This document replaces [TS183063] as the normative
>    specification of the RTCP XR IDMS Report Block.  Upon publication of
>    this document as RFC, [TS183063] will be changed to reflect this.
>=20
> The first statement is not accurate. Value 12 is not a new assignment,
> 12 was already assigned by ETSI, this document asks to change the
> assignment of value 12 from the RTCP XR Block Type for reporting IDMS
> information to the IETF defined RTCP XR IDMS Report Block.
>=20
> [Ray: Hmm, I'm not sure. I checked with IANA and they don't see a
> problem in the current wording. I think this is fundamentally a question
> of describing the 'soll' situation versus describing the process of
> getting from 'ist' to 'soll'. Once the ETSI doc has been updated, your
> proposed sentence  would no longer be necessary, right?]
>=20
[[DR]] The phrase 'This document assigns ... ' is typically used for new as=
signments, and may be misleading, especially in the interim. Describing exp=
licitly the transfer of control is better IMO.=20

> This change is however partial as described previously, as the content
> of the fields and behavior for SPST =3D 2-4 remain under ETSI control.
> Moreover, it is not clear who has further control for other new values,
> as SPST =3D 5-15 show as 'reserved for future use in both documents'. The
> IANA section does not define or refer an IANA registry and the policy
> for adding and approving new values for SPST.
>=20
> This solution is not clean. Only one organization should have control
> upon the definition of one single RTCP XR block type. Either the IETF
> should make the overleaping parts of the  document Informational and
> reflect the content of the ETSI document, or should take control over
> the whole block.
>=20
> [Ray: See my earlier comments: IETF will have full control, ETSI will
> just be extending it.]
>=20
[[DR]] a registry is better, it also avoids the need to make changes to thi=
s document if new extensions are being defined by ETSI or other organizatio=
ns.=20

> 3. The relation with the ETSI specification TS 183 063 should have been
> described clearly from the beginning of the document.
>=20
> [Ray: See my earlier comment. Since the IETF draft will be that
> normative spec that ETSI will be referencing, I believe this
> relationship should be described in ETSI, not in IETF].
>=20
[[DR]] This is where we disagree. If there was no history of control, no pr=
evious ETSI specification you would be right, but this is not the case.=20

> Minor issues:
>=20
> 1. The version of the block definition is set to V=3D2 which is the same
> as in the ETSI specification. Were versions 0 and 1 already used by
> ETSI? If this is the case a note should be made.
>=20
> [Ray: This part of the header is defined by RFC3611, and is specified to
> be set to 2 to refer to the version of RTP]
>=20
[[DR]] OK

> 2. In Section 7:
>=20
>    Reserved bits (Resrv): 3 bits.  These bits are reserved for future
>    definition.  In the absence of such a definition, the bits in this
>    field MUST be set to zero and MUST be ignored by the receiver.
>=20
> s/MUST be set to zero/MUST be set to zero at transmission/
>=20
> [Ray: Thanks, I will update the draft]
>=20
> 3. In Section 7:
>=20
>    Reserved bits (Resrv): 25 bits.  These bits are reserved for future
>    use and SHALL be set to 0.
>=20
> s/ SHALL be set to 0/ MUST be set to zero at transmission and MUST be
> ignored by the receiver/
>=20
> [Ray: Thanks, I will update the draft]
>=20
> 4. In Section 7:
>=20
>    When
>    reporting on an RTP packet which is one of several consecutive RTP
>    packets having equal timestamps, an SC SHOULD report on the RTP
>    packet it received with the lowest sequence number.
>=20
> Why a SHOULD here and not a MUST? If there are any cases of exception
> they need to be detailed.
>=20
> [Ray: Implementations might be optimized for specific scenarios by
> reporting on specific packets as indicated by e.g. an out-of-band
> signal]
>=20
[[DR]] It would be good to clarify this in the text.=20

> 5. In Section 8:
>=20
>    Because RTP
>    timestamps do wrap around, the sender of this packet SHOULD use
>    recent values, i.e. choose NTP timestamps that reflect current time
>    and not too far in the future or in the past.
>=20
> Why a SHOULD here and not a MUST? If there are any cases of exception
> they need to be detailed.
>=20
> [Ray: I will check with my co-authors]
>=20
> 6. In Section 8:
>=20
>    This SHOULD relate to the first
>    arriving RTP packet containing this particular RTP timestamp, in case
>    multiple RTP packets contain the same RTP timestamp.
>=20
> Why a SHOULD here and not a MUST? If there are any cases of exception
> they need to be detailed.
>=20
> [Ray: I will check with my co-authors]
>=20
> 7. In Section 8:
>=20
>    The timestamp is formatted based on the NTP
>    timestamp format as specified in [RFC5905].  If this field is empty,
>    then it SHALL be set to 0.  This field MAY be left empty if none or
>    only one of the receivers reported on presentation timestamps.
>=20
> Why a MAY here? Especially for the case when none of the receivers
> reported, what content can be set there but 0 ?
>=20
> [Ray: I believe it should be up to the implementation to decide how it
> wants to handle the case of there being only one receiver who reported
> on presentation timestamps].
>=20
[[DR]] OK, so the cases when none of the receivers reported and one receive=
r only reported should be dealt with differently. This needs to be clarifie=
d.=20

> 8: The reference:
>=20
> [TS183063]
>               "IMS-based IPTV stage 3 specification, TS 183 063 v3.4.1",
>               June 2010.
>=20
> V3.4.1 is not the latest release. Is this intentional? I found at least
> one more recent release dated 2011 and numbered 3.5.2 - I do not know if
> there is any diff in the relevant content, but pointing to the most
> updated review seems appropriate.
>=20
> [Ray: Thanks for noticing, I will update the reference to the latest
> ETSI release].
>=20
> 9: Did this document undergo an SDP directorate review? If not I believe
> that one would be necessary, as a new SDP Attribute is being defined.
>=20
> [Ray: Yes, an SDP directorate review has been carried out].
>=20
> Nits/editorial comments:
>=20
> 1. typo in the last paragraph of section 5 - s/nessecary/necessary/
>=20
> 2. in section 8 expand PT as Packet Type
>=20
> 3. typo in the first paragraph of section 11 - s/mutli/multi/
>=20
> [Ray: Thanks, I will update the draft]
>=20
> Regards,
>=20
> Dan
>=20
> [Ray: Again, many thanks for the thorough review!]
>=20
>=20
>=20
> This e-mail and its contents are subject to the DISCLAIMER at
> http://www.tno.nl/emaildisclaimer


From ray.vanbrandenburg@tno.nl  Mon Jun 10 01:33:41 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE99F21F854D for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 01:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k6pvnQ0zoBSj for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 01:33:34 -0700 (PDT)
Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 0285B21F84F2 for <gen-art@ietf.org>; Mon, 10 Jun 2013 01:33:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,835,1363129200";  d="scan'208";a="1603171"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1b.tno.nl with ESMTP; 10 Jun 2013 10:33:27 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.85]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 10:33:27 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGA
Date: Mon, 10 Jun 2013 08:33:26 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.191]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 10 Jun 2013 04:28:14 -0700
Cc: "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 08:33:41 -0000

Hi Dan,

Many thanks for your very thorough review. =


Before responding to your comments in detail, let me give you some backgrou=
nd on how we handle the relationship with the ETSI document: Exactly how we=
 should deal with the existing ETSI spec has been discussed at length in AV=
TCORE, both on- and offlist. As you can see in the earlier versions of the =
draft, the document used to extend the ETSI document, referencing it where =
necessary and including sections that describe this relationship. In the en=
d, the WG consensus was that the IETF draft should be the normative spec fo=
r the XR block and AVTCORE should have full change control over it. We ther=
efore removed most references to the ETSI spec, and instead started a Work =
Item in ETSI to change TS 183 063 to point to the IETF draft and remove all=
 normative statements (apart from extending the IETF-defined block with thr=
ee new SPST values). =


The current idea is therefore that since the ETSI spec will be referencing =
the IETF spec, instead of the other way around, that there is no need to de=
scribe this relationship in the IETF draft. The IETF spec is the normative =
'base' spec, and ETSI is just describing a way to use it within an IPTV sys=
tem, including three additional SPST values specific to that scenario. =


Personally, I agree with the WG consensus that this is the 'cleanest' way t=
o handle it, resulting in backwards compatibility with older versions of th=
e ETSI document as well as have full change control in IETF. =


Please see inline for your comments. =


Best regards,

Ray


-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] =

Sent: zondag 9 juni 2013 9:53
To: General Area Review Team
Cc: draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: Gen-ART review of draft-ietf-avtcore-idms-09

(resending, I mis-spelled .all address at the first try)

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-avtcore-idms-09
Reviewer: Dan Romascanu
Review Date: 6/6/13
IETF LC End Date: 6/11/13
IESG Telechat date: =


Summary:

Not Ready

Major issues:

1. This document is tightly connected with the ETSI specification TS 183 06=
3. However this relation is mentioned only in a couple of places and does n=
ot describe the complexity of the relation. Moreover, the relation itself s=
eems problematic. =


The I-D uses some of the inter-destination media techniques described by ET=
SI TS 183 063. For example Section 7 replicates part of the content of Anne=
x W of the ETSI document. It does it partially however, and with some modif=
ications, as only the content definition and behavior of the transmitters a=
nd receivers for SPST=3D1 were taken from Annex W, while the content and be=
havior for SPST=3D2-4 are marked as 'defined by ETSI TISPAN'. The ETSI docu=
ment details what happens with the fields when SPST=3D2-4. This will result=
 in the RTCP XR block for IDMS to be defined in two places - part in this I=
ETF document (if approved), the rest in the ETSI document (to be modified a=
ccordingly in the future). For some period of time the same fields will be =
defined in two places. This seems broken. =


[Ray: See my comments above. The ETSI document will be changed to point to =
the IETF spec. Does this solve your issue? In addition, we could create an =
IANA registry for SPST values, although I personally believe this to not be=
 necessary]

2. The note to the RFC Editor in section 14.2 states: =


   14.2.  RTCP XR IDMS Report Block

   This document assigns the block type value 12 in the IANA "RTCP XR
   Block Type Registry" to the RTCP XR IDMS Report Block.
	=

   [Note to RFC Editor: this block type value is currently assigned to
   [TS183063].  This document replaces [TS183063] as the normative
   specification of the RTCP XR IDMS Report Block.  Upon publication of
   this document as RFC, [TS183063] will be changed to reflect this.

The first statement is not accurate. Value 12 is not a new assignment, 12 w=
as already assigned by ETSI, this document asks to change the assignment of=
 value 12 from the RTCP XR Block Type for reporting IDMS information to the=
 IETF defined RTCP XR IDMS Report Block. =


[Ray: Hmm, I'm not sure. I checked with IANA and they don't see a problem i=
n the current wording. I think this is fundamentally a question of describi=
ng the 'soll' situation versus describing the process of getting from 'ist'=
 to 'soll'. Once the ETSI doc has been updated, your proposed sentence  wou=
ld no longer be necessary, right?]

This change is however partial as described previously, as the content of t=
he fields and behavior for SPST =3D 2-4 remain under ETSI control. Moreover=
, it is not clear who has further control for other new values, as SPST =3D=
 5-15 show as 'reserved for future use in both documents'. The IANA section=
 does not define or refer an IANA registry and the policy for adding and ap=
proving new values for SPST. =


This solution is not clean. Only one organization should have control upon =
the definition of one single RTCP XR block type. Either the IETF should mak=
e the overleaping parts of the  document Informational and reflect the cont=
ent of the ETSI document, or should take control over the whole block. =


[Ray: See my earlier comments: IETF will have full control, ETSI will just =
be extending it.] =


3. The relation with the ETSI specification TS 183 063 should have been des=
cribed clearly from the beginning of the document. =


[Ray: See my earlier comment. Since the IETF draft will be that normative s=
pec that ETSI will be referencing, I believe this relationship should be de=
scribed in ETSI, not in IETF].

Minor issues:

1. The version of the block definition is set to V=3D2 which is the same as=
 in the ETSI specification. Were versions 0 and 1 already used by ETSI? If =
this is the case a note should be made. =


[Ray: This part of the header is defined by RFC3611, and is specified to be=
 set to 2 to refer to the version of RTP]

2. In Section 7: =


   Reserved bits (Resrv): 3 bits.  These bits are reserved for future
   definition.  In the absence of such a definition, the bits in this
   field MUST be set to zero and MUST be ignored by the receiver.

s/MUST be set to zero/MUST be set to zero at transmission/

[Ray: Thanks, I will update the draft]

3. In Section 7: =


   Reserved bits (Resrv): 25 bits.  These bits are reserved for future
   use and SHALL be set to 0.

s/ SHALL be set to 0/ MUST be set to zero at transmission and MUST be ignor=
ed by the receiver/

[Ray: Thanks, I will update the draft]

4. In Section 7: =


   When
   reporting on an RTP packet which is one of several consecutive RTP
   packets having equal timestamps, an SC SHOULD report on the RTP
   packet it received with the lowest sequence number.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

[Ray: Implementations might be optimized for specific scenarios by reportin=
g on specific packets as indicated by e.g. an out-of-band signal]

5. In Section 8: =


   Because RTP
   timestamps do wrap around, the sender of this packet SHOULD use
   recent values, i.e. choose NTP timestamps that reflect current time
   and not too far in the future or in the past. =


Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

[Ray: I will check with my co-authors]

6. In Section 8: =


   This SHOULD relate to the first
   arriving RTP packet containing this particular RTP timestamp, in case
   multiple RTP packets contain the same RTP timestamp.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.

[Ray: I will check with my co-authors]

7. In Section 8: =


   The timestamp is formatted based on the NTP
   timestamp format as specified in [RFC5905].  If this field is empty,
   then it SHALL be set to 0.  This field MAY be left empty if none or
   only one of the receivers reported on presentation timestamps.

Why a MAY here? Especially for the case when none of the receivers reported=
, what content can be set there but 0 ?

[Ray: I believe it should be up to the implementation to decide how it want=
s to handle the case of there being only one receiver who reported on prese=
ntation timestamps]. =


8: The reference: =


[TS183063]
              "IMS-based IPTV stage 3 specification, TS 183 063 v3.4.1",
              June 2010.

V3.4.1 is not the latest release. Is this intentional? I found at least one=
 more recent release dated 2011 and numbered 3.5.2 - I do not know if there=
 is any diff in the relevant content, but pointing to the most updated revi=
ew seems appropriate.

[Ray: Thanks for noticing, I will update the reference to the latest ETSI r=
elease]. =


9: Did this document undergo an SDP directorate review? If not I believe th=
at one would be necessary, as a new SDP Attribute is being defined. =

 =

[Ray: Yes, an SDP directorate review has been carried out]. =


Nits/editorial comments:

1. typo in the last paragraph of section 5 - s/nessecary/necessary/

2. in section 8 expand PT as Packet Type

3. typo in the first paragraph of section 11 - s/mutli/multi/

[Ray: Thanks, I will update the draft]

Regards,

Dan

[Ray: Again, many thanks for the thorough review!]



This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From ray.vanbrandenburg@tno.nl  Mon Jun 10 05:46:36 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2055C21F84B1; Mon, 10 Jun 2013 05:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wCbHefeuyeDW; Mon, 10 Jun 2013 05:46:29 -0700 (PDT)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 223A821F843F; Mon, 10 Jun 2013 05:38:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,836,1363129200";  d="scan'208";a="9657969"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1a.tno.nl with ESMTP; 10 Jun 2013 14:27:32 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.85]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 14:27:32 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBw
Date: Mon, 10 Jun 2013 12:27:31 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 12:46:36 -0000

Hi Dan,

(I've cc'ed the AVTCORE list on Magnus' request)

Please see my comments inline (I've shortened the message exchange somewhat=
 to only include the points of discussion). =


Best regards,

Ray

> Before responding to your comments in detail, let me give you some =

> background on how we handle the relationship with the ETSI document:
> Exactly how we should deal with the existing ETSI spec has been =

> discussed at length in AVTCORE, both on- and offlist. As you can see =

> in the earlier versions of the draft, the document used to extend the =

> ETSI document, referencing it where necessary and including sections =

> that describe this relationship. In the end, the WG consensus was that =

> the IETF draft should be the normative spec for the XR block and =

> AVTCORE should have full change control over it. We therefore removed =

> most references to the ETSI spec, and instead started a Work Item in =

> ETSI to change TS 183 063 to point to the IETF draft and remove all =

> normative statements (apart from extending the IETF-defined block with =

> three new SPST values).
> =

[[DR]] Thank you for the clarification information. This is very useful. Ca=
n you tell what is the status of the work item in ETSI? =


[Ray] The current status is that the Work Item has been opened and the cont=
ributions have been written and discussed. ETSI has postponed formally acce=
pting the contributions until the IETF document is given an RFC number so t=
hat they can reference it. =


> The current idea is therefore that since the ETSI spec will be =

> referencing the IETF spec, instead of the other way around, that there =

> is no need to describe this relationship in the IETF draft. The IETF =

> spec is the normative 'base' spec, and ETSI is just describing a way =

> to use it within an IPTV system, including three additional SPST =

> values specific to that scenario.
[[DR]] I disagree that there is no need to describe this relationship on th=
e IETF draft. As control for the XR block was previously in ETSI and will n=
ow be transferred to the IETF we should assume that there are implementers =
and deployments who know about the older ETSI specification. You need a sec=
tions that describes the relationship with the ETSI document, and describes=
 the changes relative to that version - same as would have been written if =
there was an RFC that was updated or made obsolete by this document. =


Moreover, the current document is not consistent, as it still keeps a norma=
tive reference to the older (not even the latest version) ETSI document. Th=
is will be not needed any longer, an informational reference would be suffi=
cient.  =


[Ray] I agree completely. This seems to be a relic and I will update the re=
ference to make it informational. =


> 1. This document is tightly connected with the ETSI specification TS
> 183 063. However this relation is mentioned only in a couple of places =

> and does not describe the complexity of the relation. Moreover, the =

> relation itself seems problematic.
> =

> The I-D uses some of the inter-destination media techniques described =

> by ETSI TS 183 063. For example Section 7 replicates part of the =

> content of Annex W of the ETSI document. It does it partially however, =

> and with some modifications, as only the content definition and =

> behavior of the transmitters and receivers for SPST=3D1 were taken from =

> Annex W, while the content and behavior for SPST=3D2-4 are marked as =

> 'defined by ETSI TISPAN'. The ETSI document details what happens with =

> the fields when SPST=3D2-4. This will result in the RTCP XR block for =

> IDMS to be defined in two places - part in this IETF document (if =

> approved), the rest in the ETSI document (to be modified accordingly =

> in the future). For some period of time the same fields will be =

> defined in two places. This seems broken.
> =

> [Ray: See my comments above. The ETSI document will be changed to =

> point to the IETF spec. Does this solve your issue? In addition, we =

> could create an IANA registry for SPST values, although I personally =

> believe this to not be necessary]
> =

[[DR]] Eventually it will solve the issue, but the situation is murky in th=
e interim. I believe that creating a registry would be good, because it pro=
vides a way to describe the interim situation, and also because we do not k=
now yet for sure who may use the values 5-15 in the future. =


[Ray] As Roni mentioned, it is a chicken-egg problem. If there is consensus=
 in the WG to create a registry, I am happy to include one in the draft. =


> 2. The note to the RFC Editor in section 14.2 states:
> =

>    14.2.  RTCP XR IDMS Report Block
> =

>    This document assigns the block type value 12 in the IANA "RTCP XR
>    Block Type Registry" to the RTCP XR IDMS Report Block.
> =

>    [Note to RFC Editor: this block type value is currently assigned to
>    [TS183063].  This document replaces [TS183063] as the normative
>    specification of the RTCP XR IDMS Report Block.  Upon publication of
>    this document as RFC, [TS183063] will be changed to reflect this.
> =

> The first statement is not accurate. Value 12 is not a new assignment,
> 12 was already assigned by ETSI, this document asks to change the =

> assignment of value 12 from the RTCP XR Block Type for reporting IDMS =

> information to the IETF defined RTCP XR IDMS Report Block.
> =

> [Ray: Hmm, I'm not sure. I checked with IANA and they don't see a =

> problem in the current wording. I think this is fundamentally a =

> question of describing the 'soll' situation versus describing the =

> process of getting from 'ist' to 'soll'. Once the ETSI doc has been =

> updated, your proposed sentence  would no longer be necessary, right?]
> =

[[DR]] The phrase 'This document assigns ... ' is typically used for new as=
signments, and may be misleading, especially in the interim. Describing exp=
licitly the transfer of control is better IMO. =


[Ray] Fair enough. How about: 'This document asks to update the assignment =
of value 12 from the RTCP XR Block Type for reporting IDMS =

information to the RTCP XR IDMS Report Block defined in this document' ?

> This change is however partial as described previously, as the content =

> of the fields and behavior for SPST =3D 2-4 remain under ETSI control.
> Moreover, it is not clear who has further control for other new =

> values, as SPST =3D 5-15 show as 'reserved for future use in both =

> documents'. The IANA section does not define or refer an IANA registry =

> and the policy for adding and approving new values for SPST.
> =

> This solution is not clean. Only one organization should have control =

> upon the definition of one single RTCP XR block type. Either the IETF =

> should make the overleaping parts of the  document Informational and =

> reflect the content of the ETSI document, or should take control over =

> the whole block.
> =

> [Ray: See my earlier comments: IETF will have full control, ETSI will =

> just be extending it.]
> =

[[DR]] a registry is better, it also avoids the need to make changes to thi=
s document if new extensions are being defined by ETSI or other organizatio=
ns. =


[Ray] See my earlier comment: if the WG consensus is that we need a registr=
y, I can include one. =


> 3. The relation with the ETSI specification TS 183 063 should have =

> been described clearly from the beginning of the document.
> =

> [Ray: See my earlier comment. Since the IETF draft will be that =

> normative spec that ETSI will be referencing, I believe this =

> relationship should be described in ETSI, not in IETF].
> =

[[DR]] This is where we disagree. If there was no history of control, no pr=
evious ETSI specification you would be right, but this is not the case. =


[Ray] Can we agree to a short informational section that describes the hist=
ory of IDMS in ETSI and IETF?


> 4. In Section 7:
> =

>    When
>    reporting on an RTP packet which is one of several consecutive RTP
>    packets having equal timestamps, an SC SHOULD report on the RTP
>    packet it received with the lowest sequence number.
> =

> Why a SHOULD here and not a MUST? If there are any cases of exception =

> they need to be detailed.
> =

> [Ray: Implementations might be optimized for specific scenarios by =

> reporting on specific packets as indicated by e.g. an out-of-band =

> signal]
> =

[[DR]] It would be good to clarify this in the text. =


[Ray] OK


> 7. In Section 8:
> =

>    The timestamp is formatted based on the NTP
>    timestamp format as specified in [RFC5905].  If this field is empty,
>    then it SHALL be set to 0.  This field MAY be left empty if none or
>    only one of the receivers reported on presentation timestamps.
> =

> Why a MAY here? Especially for the case when none of the receivers =

> reported, what content can be set there but 0 ?
> =

> [Ray: I believe it should be up to the implementation to decide how it =

> wants to handle the case of there being only one receiver who reported =

> on presentation timestamps].
> =

[[DR]] OK, so the cases when none of the receivers reported and one receive=
r only reported should be dealt with differently. This needs to be clarifie=
d. =


[Ray] What exactly is the problem with the MAY here? IMO it doesn't create =
any interop issues: whatever is the reason for setting the value to 0, to t=
he client the end result is the same: ignore it. =


Best regards,

Ray
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From dromasca@avaya.com  Mon Jun 10 06:11:10 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A7621F8AC2; Mon, 10 Jun 2013 06:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASVcaeA1UB3Y; Mon, 10 Jun 2013 06:11:04 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id ADB8C21F866E; Mon, 10 Jun 2013 06:11:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAIPPtVGHCzI1/2dsb2JhbABagmghMEm+QYEDFnSCIwEBAQECARIoOAcFBwQCAQgNBAQBAQsUCQchERQJCAEBBAoEBQgTB4dZAwkGAQudMZJzDYg7F4xbgSuBATEHBoJ5YQOVWAGIKYVchSSDD4FxNg
X-IronPort-AV: E=Sophos;i="4.87,837,1363147200"; d="scan'208";a="12506580"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jun 2013 09:11:00 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Jun 2013 09:05:54 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 09:10:38 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThA=
Date: Mon, 10 Jun 2013 13:10:38 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 13:11:11 -0000

Hi Ray,

Thanks again for considering my comments.=20

See in-line.=20

Regards,

Dan




> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 3:28 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
> Hi Dan,
>=20
> (I've cc'ed the AVTCORE list on Magnus' request)
>=20
> Please see my comments inline (I've shortened the message exchange
> somewhat to only include the points of discussion).
>=20
> Best regards,
>=20
> Ray
>=20
> > Before responding to your comments in detail, let me give you some
> > background on how we handle the relationship with the ETSI document:
> > Exactly how we should deal with the existing ETSI spec has been
> > discussed at length in AVTCORE, both on- and offlist. As you can see
> > in the earlier versions of the draft, the document used to extend the
> > ETSI document, referencing it where necessary and including sections
> > that describe this relationship. In the end, the WG consensus was that
> > the IETF draft should be the normative spec for the XR block and
> > AVTCORE should have full change control over it. We therefore removed
> > most references to the ETSI spec, and instead started a Work Item in
> > ETSI to change TS 183 063 to point to the IETF draft and remove all
> > normative statements (apart from extending the IETF-defined block with
> > three new SPST values).
> >
> [[DR]] Thank you for the clarification information. This is very useful.
> Can you tell what is the status of the work item in ETSI?
>=20
> [Ray] The current status is that the Work Item has been opened and the
> contributions have been written and discussed. ETSI has postponed
> formally accepting the contributions until the IETF document is given an
> RFC number so that they can reference it.
>=20
> > The current idea is therefore that since the ETSI spec will be
> > referencing the IETF spec, instead of the other way around, that there
> > is no need to describe this relationship in the IETF draft. The IETF
> > spec is the normative 'base' spec, and ETSI is just describing a way
> > to use it within an IPTV system, including three additional SPST
> > values specific to that scenario.
> [[DR]] I disagree that there is no need to describe this relationship on
> the IETF draft. As control for the XR block was previously in ETSI and
> will now be transferred to the IETF we should assume that there are
> implementers and deployments who know about the older ETSI
> specification. You need a sections that describes the relationship with
> the ETSI document, and describes the changes relative to that version -
> same as would have been written if there was an RFC that was updated or
> made obsolete by this document.
>=20
> Moreover, the current document is not consistent, as it still keeps a
> normative reference to the older (not even the latest version) ETSI
> document. This will be not needed any longer, an informational reference
> would be sufficient.
>=20
> [Ray] I agree completely. This seems to be a relic and I will update the
> reference to make it informational.
>=20
> > 1. This document is tightly connected with the ETSI specification TS
> > 183 063. However this relation is mentioned only in a couple of places
> > and does not describe the complexity of the relation. Moreover, the
> > relation itself seems problematic.
> >
> > The I-D uses some of the inter-destination media techniques described
> > by ETSI TS 183 063. For example Section 7 replicates part of the
> > content of Annex W of the ETSI document. It does it partially however,
> > and with some modifications, as only the content definition and
> > behavior of the transmitters and receivers for SPST=3D1 were taken from
> > Annex W, while the content and behavior for SPST=3D2-4 are marked as
> > 'defined by ETSI TISPAN'. The ETSI document details what happens with
> > the fields when SPST=3D2-4. This will result in the RTCP XR block for
> > IDMS to be defined in two places - part in this IETF document (if
> > approved), the rest in the ETSI document (to be modified accordingly
> > in the future). For some period of time the same fields will be
> > defined in two places. This seems broken.
> >
> > [Ray: See my comments above. The ETSI document will be changed to
> > point to the IETF spec. Does this solve your issue? In addition, we
> > could create an IANA registry for SPST values, although I personally
> > believe this to not be necessary]
> >
> [[DR]] Eventually it will solve the issue, but the situation is murky in
> the interim. I believe that creating a registry would be good, because
> it provides a way to describe the interim situation, and also because we
> do not know yet for sure who may use the values 5-15 in the future.
>=20
> [Ray] As Roni mentioned, it is a chicken-egg problem. If there is
> consensus in the WG to create a registry, I am happy to include one in
> the draft.
>=20
> > 2. The note to the RFC Editor in section 14.2 states:
> >
> >    14.2.  RTCP XR IDMS Report Block
> >
> >    This document assigns the block type value 12 in the IANA "RTCP XR
> >    Block Type Registry" to the RTCP XR IDMS Report Block.
> >
> >    [Note to RFC Editor: this block type value is currently assigned to
> >    [TS183063].  This document replaces [TS183063] as the normative
> >    specification of the RTCP XR IDMS Report Block.  Upon publication
> of
> >    this document as RFC, [TS183063] will be changed to reflect this.
> >
> > The first statement is not accurate. Value 12 is not a new assignment,
> > 12 was already assigned by ETSI, this document asks to change the
> > assignment of value 12 from the RTCP XR Block Type for reporting IDMS
> > information to the IETF defined RTCP XR IDMS Report Block.
> >
> > [Ray: Hmm, I'm not sure. I checked with IANA and they don't see a
> > problem in the current wording. I think this is fundamentally a
> > question of describing the 'soll' situation versus describing the
> > process of getting from 'ist' to 'soll'. Once the ETSI doc has been
> > updated, your proposed sentence  would no longer be necessary, right?]
> >
> [[DR]] The phrase 'This document assigns ... ' is typically used for new
> assignments, and may be misleading, especially in the interim.
> Describing explicitly the transfer of control is better IMO.
>=20
> [Ray] Fair enough. How about: 'This document asks to update the
> assignment of value 12 from the RTCP XR Block Type for reporting IDMS
> information to the RTCP XR IDMS Report Block defined in this document' ?
>=20
[[DR]] close, with slight edits, I would make it:=20

'This document updates the assignment of value 12 from the RTCP XR=20
Block Type for reporting IDMS information as per [TS183063] to the=20
RTCP XR IDMS Report Block defined in this document'=20


> > This change is however partial as described previously, as the content
> > of the fields and behavior for SPST =3D 2-4 remain under ETSI control.
> > Moreover, it is not clear who has further control for other new
> > values, as SPST =3D 5-15 show as 'reserved for future use in both
> > documents'. The IANA section does not define or refer an IANA registry
> > and the policy for adding and approving new values for SPST.
> >
> > This solution is not clean. Only one organization should have control
> > upon the definition of one single RTCP XR block type. Either the IETF
> > should make the overleaping parts of the  document Informational and
> > reflect the content of the ETSI document, or should take control over
> > the whole block.
> >
> > [Ray: See my earlier comments: IETF will have full control, ETSI will
> > just be extending it.]
> >
> [[DR]] a registry is better, it also avoids the need to make changes to
> this document if new extensions are being defined by ETSI or other
> organizations.
>=20
> [Ray] See my earlier comment: if the WG consensus is that we need a
> registry, I can include one.
>=20
> > 3. The relation with the ETSI specification TS 183 063 should have
> > been described clearly from the beginning of the document.
> >
> > [Ray: See my earlier comment. Since the IETF draft will be that
> > normative spec that ETSI will be referencing, I believe this
> > relationship should be described in ETSI, not in IETF].
> >
> [[DR]] This is where we disagree. If there was no history of control, no
> previous ETSI specification you would be right, but this is not the
> case.
>=20
> [Ray] Can we agree to a short informational section that describes the
> history of IDMS in ETSI and IETF?
>=20
>=20
[[DR]] that's all I am asking

> > 4. In Section 7:
> >
> >    When
> >    reporting on an RTP packet which is one of several consecutive RTP
> >    packets having equal timestamps, an SC SHOULD report on the RTP
> >    packet it received with the lowest sequence number.
> >
> > Why a SHOULD here and not a MUST? If there are any cases of exception
> > they need to be detailed.
> >
> > [Ray: Implementations might be optimized for specific scenarios by
> > reporting on specific packets as indicated by e.g. an out-of-band
> > signal]
> >
> [[DR]] It would be good to clarify this in the text.
>=20
> [Ray] OK
>=20
>=20
> > 7. In Section 8:
> >
> >    The timestamp is formatted based on the NTP
> >    timestamp format as specified in [RFC5905].  If this field is
> empty,
> >    then it SHALL be set to 0.  This field MAY be left empty if none or
> >    only one of the receivers reported on presentation timestamps.
> >
> > Why a MAY here? Especially for the case when none of the receivers
> > reported, what content can be set there but 0 ?
> >
> > [Ray: I believe it should be up to the implementation to decide how it
> > wants to handle the case of there being only one receiver who reported
> > on presentation timestamps].
> >
> [[DR]] OK, so the cases when none of the receivers reported and one
> receiver only reported should be dealt with differently. This needs to
> be clarified.
>=20
> [Ray] What exactly is the problem with the MAY here? IMO it doesn't
> create any interop issues: whatever is the reason for setting the value
> to 0, to the client the end result is the same: ignore it.
>=20

[[DR]] In the case when none of the receivers reported we want to avoid lea=
ving some garbage in this field which could be interpreted differently - do=
n't we?=20

> Best regards,
>=20
> Ray
> This e-mail and its contents are subject to the DISCLAIMER at
> http://www.tno.nl/emaildisclaimer


From ray.vanbrandenburg@tno.nl  Mon Jun 10 07:27:14 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC0A21F9485; Mon, 10 Jun 2013 07:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wrzb8I1fjksv; Mon, 10 Jun 2013 07:27:08 -0700 (PDT)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id D6FB921F9473; Mon, 10 Jun 2013 07:27:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,837,1363129200";  d="scan'208";a="9667752"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.222]) by mailhost1a.tno.nl with ESMTP; 10 Jun 2013 16:27:06 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.85]) by EXC-CASHUB03.tsn.tno.nl ([134.221.225.222]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 16:27:06 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4A==
Date: Mon, 10 Jun 2013 14:27:05 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 14:27:14 -0000

Hi Dan,

Please see inline. We seem to be converging:)

Ray



-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]=20
Sent: maandag 10 juni 2013 15:11
To: Brandenburg, R. (Ray) van
Cc: avt@ietf.org; General Area Review Team; Roni Even (ron.even.tlv@gmail.c=
om); draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09

Hi Ray,

Thanks again for considering my comments.=20

See in-line.=20

Regards,

Dan




> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 3:28 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even=20
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
> Hi Dan,
>=20
> (I've cc'ed the AVTCORE list on Magnus' request)
>=20
> Please see my comments inline (I've shortened the message exchange=20
> somewhat to only include the points of discussion).
>=20
> Best regards,
>=20
> Ray
>=20
> > Before responding to your comments in detail, let me give you some=20
> > background on how we handle the relationship with the ETSI document:
> > Exactly how we should deal with the existing ETSI spec has been=20
> > discussed at length in AVTCORE, both on- and offlist. As you can see=20
> > in the earlier versions of the draft, the document used to extend=20
> > the ETSI document, referencing it where necessary and including=20
> > sections that describe this relationship. In the end, the WG=20
> > consensus was that the IETF draft should be the normative spec for=20
> > the XR block and AVTCORE should have full change control over it. We=20
> > therefore removed most references to the ETSI spec, and instead=20
> > started a Work Item in ETSI to change TS 183 063 to point to the=20
> > IETF draft and remove all normative statements (apart from extending=20
> > the IETF-defined block with three new SPST values).
> >
> [[DR]] Thank you for the clarification information. This is very useful.
> Can you tell what is the status of the work item in ETSI?
>=20
> [Ray] The current status is that the Work Item has been opened and the=20
> contributions have been written and discussed. ETSI has postponed=20
> formally accepting the contributions until the IETF document is given=20
> an RFC number so that they can reference it.
>=20
> > The current idea is therefore that since the ETSI spec will be=20
> > referencing the IETF spec, instead of the other way around, that=20
> > there is no need to describe this relationship in the IETF draft.=20
> > The IETF spec is the normative 'base' spec, and ETSI is just=20
> > describing a way to use it within an IPTV system, including three=20
> > additional SPST values specific to that scenario.
> [[DR]] I disagree that there is no need to describe this relationship=20
> on the IETF draft. As control for the XR block was previously in ETSI=20
> and will now be transferred to the IETF we should assume that there=20
> are implementers and deployments who know about the older ETSI=20
> specification. You need a sections that describes the relationship=20
> with the ETSI document, and describes the changes relative to that=20
> version - same as would have been written if there was an RFC that was=20
> updated or made obsolete by this document.
>=20
> Moreover, the current document is not consistent, as it still keeps a=20
> normative reference to the older (not even the latest version) ETSI=20
> document. This will be not needed any longer, an informational=20
> reference would be sufficient.
>=20
> [Ray] I agree completely. This seems to be a relic and I will update=20
> the reference to make it informational.
>=20
> > 1. This document is tightly connected with the ETSI specification TS
> > 183 063. However this relation is mentioned only in a couple of=20
> > places and does not describe the complexity of the relation.=20
> > Moreover, the relation itself seems problematic.
> >
> > The I-D uses some of the inter-destination media techniques=20
> > described by ETSI TS 183 063. For example Section 7 replicates part=20
> > of the content of Annex W of the ETSI document. It does it partially=20
> > however, and with some modifications, as only the content definition=20
> > and behavior of the transmitters and receivers for SPST=3D1 were taken=
=20
> > from Annex W, while the content and behavior for SPST=3D2-4 are marked=
=20
> > as 'defined by ETSI TISPAN'. The ETSI document details what happens=20
> > with the fields when SPST=3D2-4. This will result in the RTCP XR block=
=20
> > for IDMS to be defined in two places - part in this IETF document=20
> > (if approved), the rest in the ETSI document (to be modified=20
> > accordingly in the future). For some period of time the same fields=20
> > will be defined in two places. This seems broken.
> >
> > [Ray: See my comments above. The ETSI document will be changed to=20
> > point to the IETF spec. Does this solve your issue? In addition, we=20
> > could create an IANA registry for SPST values, although I personally=20
> > believe this to not be necessary]
> >
> [[DR]] Eventually it will solve the issue, but the situation is murky=20
> in the interim. I believe that creating a registry would be good,=20
> because it provides a way to describe the interim situation, and also=20
> because we do not know yet for sure who may use the values 5-15 in the fu=
ture.
>=20
> [Ray] As Roni mentioned, it is a chicken-egg problem. If there is=20
> consensus in the WG to create a registry, I am happy to include one in=20
> the draft.
>=20
> > 2. The note to the RFC Editor in section 14.2 states:
> >
> >    14.2.  RTCP XR IDMS Report Block
> >
> >    This document assigns the block type value 12 in the IANA "RTCP XR
> >    Block Type Registry" to the RTCP XR IDMS Report Block.
> >
> >    [Note to RFC Editor: this block type value is currently assigned to
> >    [TS183063].  This document replaces [TS183063] as the normative
> >    specification of the RTCP XR IDMS Report Block.  Upon publication
> of
> >    this document as RFC, [TS183063] will be changed to reflect this.
> >
> > The first statement is not accurate. Value 12 is not a new=20
> > assignment,
> > 12 was already assigned by ETSI, this document asks to change the=20
> > assignment of value 12 from the RTCP XR Block Type for reporting=20
> > IDMS information to the IETF defined RTCP XR IDMS Report Block.
> >
> > [Ray: Hmm, I'm not sure. I checked with IANA and they don't see a=20
> > problem in the current wording. I think this is fundamentally a=20
> > question of describing the 'soll' situation versus describing the=20
> > process of getting from 'ist' to 'soll'. Once the ETSI doc has been=20
> > updated, your proposed sentence  would no longer be necessary,=20
> > right?]
> >
> [[DR]] The phrase 'This document assigns ... ' is typically used for=20
> new assignments, and may be misleading, especially in the interim.
> Describing explicitly the transfer of control is better IMO.
>=20
> [Ray] Fair enough. How about: 'This document asks to update the=20
> assignment of value 12 from the RTCP XR Block Type for reporting IDMS=20
> information to the RTCP XR IDMS Report Block defined in this document' ?
>=20
[[DR]] close, with slight edits, I would make it:=20

'This document updates the assignment of value 12 from the RTCP XR Block Ty=
pe for reporting IDMS information as per [TS183063] to the RTCP XR IDMS Rep=
ort Block defined in this document'=20

[Ray] Ok.


> > This change is however partial as described previously, as the=20
> > content of the fields and behavior for SPST =3D 2-4 remain under ETSI c=
ontrol.
> > Moreover, it is not clear who has further control for other new=20
> > values, as SPST =3D 5-15 show as 'reserved for future use in both=20
> > documents'. The IANA section does not define or refer an IANA=20
> > registry and the policy for adding and approving new values for SPST.
> >
> > This solution is not clean. Only one organization should have=20
> > control upon the definition of one single RTCP XR block type. Either=20
> > the IETF should make the overleaping parts of the  document=20
> > Informational and reflect the content of the ETSI document, or=20
> > should take control over the whole block.
> >
> > [Ray: See my earlier comments: IETF will have full control, ETSI=20
> > will just be extending it.]
> >
> [[DR]] a registry is better, it also avoids the need to make changes=20
> to this document if new extensions are being defined by ETSI or other=20
> organizations.
>=20
> [Ray] See my earlier comment: if the WG consensus is that we need a=20
> registry, I can include one.
>=20
> > 3. The relation with the ETSI specification TS 183 063 should have=20
> > been described clearly from the beginning of the document.
> >
> > [Ray: See my earlier comment. Since the IETF draft will be that=20
> > normative spec that ETSI will be referencing, I believe this=20
> > relationship should be described in ETSI, not in IETF].
> >
> [[DR]] This is where we disagree. If there was no history of control,=20
> no previous ETSI specification you would be right, but this is not the=20
> case.
>=20
> [Ray] Can we agree to a short informational section that describes the=20
> history of IDMS in ETSI and IETF?
>=20
>=20
[[DR]] that's all I am asking

[Ray] Ok, I think that is acceptable.=20

> > 4. In Section 7:
> >
> >    When
> >    reporting on an RTP packet which is one of several consecutive RTP
> >    packets having equal timestamps, an SC SHOULD report on the RTP
> >    packet it received with the lowest sequence number.
> >
> > Why a SHOULD here and not a MUST? If there are any cases of=20
> > exception they need to be detailed.
> >
> > [Ray: Implementations might be optimized for specific scenarios by=20
> > reporting on specific packets as indicated by e.g. an out-of-band=20
> > signal]
> >
> [[DR]] It would be good to clarify this in the text.
>=20
> [Ray] OK
>=20
>=20
> > 7. In Section 8:
> >
> >    The timestamp is formatted based on the NTP
> >    timestamp format as specified in [RFC5905].  If this field is
> empty,
> >    then it SHALL be set to 0.  This field MAY be left empty if none or
> >    only one of the receivers reported on presentation timestamps.
> >
> > Why a MAY here? Especially for the case when none of the receivers=20
> > reported, what content can be set there but 0 ?
> >
> > [Ray: I believe it should be up to the implementation to decide how=20
> > it wants to handle the case of there being only one receiver who=20
> > reported on presentation timestamps].
> >
> [[DR]] OK, so the cases when none of the receivers reported and one=20
> receiver only reported should be dealt with differently. This needs to=20
> be clarified.
>=20
> [Ray] What exactly is the problem with the MAY here? IMO it doesn't=20
> create any interop issues: whatever is the reason for setting the=20
> value to 0, to the client the end result is the same: ignore it.
>=20

[[DR]] In the case when none of the receivers reported we want to avoid lea=
ving some garbage in this field which could be interpreted differently - do=
n't we?=20

[Ray] I think I see where we disagree. The paragraph says: "If this field i=
s empty, then it SHALL be set to 0. This field MAY be left empty if none or=
 only one of the receivers reported on presentation timestamps". The way I =
read this is as: In the case the field is declared empty (=3D contains NULL=
 information), it SHALL be set to 0. There can be different reasons for dec=
laring the field empty/NULL, one of those reasons is if none or only one re=
ceiver reported on presentation timestamps. To me, the paragraph doesn't sa=
y that this is the only possible reason, but it does specify very clearly t=
hat if you decide the field should be empty, you SHALL set it to zero.=20


> Best regards,
>=20
> Ray
> This e-mail and its contents are subject to the DISCLAIMER at=20
> http://www.tno.nl/emaildisclaimer


From kevin.gross@avanw.com  Mon Jun 10 07:26:13 2013
Return-Path: <kevin.gross@avanw.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9C121F93E5 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 07:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.186
X-Spam-Level: 
X-Spam-Status: No, score=0.186 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bfl4xrUaXF5N for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 07:26:09 -0700 (PDT)
Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:32]) by ietfa.amsl.com (Postfix) with ESMTP id 94C0E21F9412 for <gen-art@ietf.org>; Mon, 10 Jun 2013 07:26:07 -0700 (PDT)
Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by qmta03.emeryville.ca.mail.comcast.net with comcast id mcl81l00317UAYkA3eS68a; Mon, 10 Jun 2013 14:26:06 +0000
Received: from mail-ie0-x22f.google.com ([IPv6:2607:f8b0:4001:c03::22f]) by omta13.emeryville.ca.mail.comcast.net with comcast id meS41l00x5FJP4R8ZeS5Cc; Mon, 10 Jun 2013 14:26:06 +0000
Received: by mail-ie0-f175.google.com with SMTP id a13so3505636iee.20 for <multiple recipients>; Mon, 10 Jun 2013 07:26:04 -0700 (PDT)
X-Google-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=JxSUwGNAiNQ+YkSrt0Qdt6RNZ1iHRyTYpqS/VnTwvsk=; b=ZjdxUDkSKhOAuU4HegUwFttzMflHo9wBF38LEkma/YyjoSU/Q2Afd1HU1GZ9g+jhDf D4OBSCtTVKs++k/XNMfzj1AbLSdttnKC2goneIp6pEW5Jsh+kWATrkRopo+T8FLHNv5h GRXLhycYFQniMHtzzyyGl0bw9gpSgcuCS7JAmzuLk1A12ET8i+UdR864VBj3bXBpJjSY Zq0eifmE5YLKa32OgZhEhVWOM6gIAk4sFlglPtZHOTXKiQZ0i7pBy4Z20k2OEsQbaNt8 V7lQAnzcTsKbCd1/Lg3XzAocSwKfBSXhvEAQspDRkAQMyxlH//9ebDKnUH/p/1KoGE2x kGKA==
MIME-Version: 1.0
X-Received: by 10.43.9.4 with SMTP id ou4mr3868419icb.53.1370874364796; Mon, 10 Jun 2013 07:26:04 -0700 (PDT)
Received: by 10.50.149.199 with HTTP; Mon, 10 Jun 2013 07:26:04 -0700 (PDT)
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl>
Date: Mon, 10 Jun 2013 08:26:04 -0600
Message-ID: <CALw1_Q13icqNLGDuvCOMB-O6Q_LtnjXSvZqG_Tyftuf6BjYCEg@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Content-Type: multipart/alternative; boundary=bcaec50dc32c8bcb4004decd8f9c
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370874366; bh=JxSUwGNAiNQ+YkSrt0Qdt6RNZ1iHRyTYpqS/VnTwvsk=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=bh9Buspt1eo+aJI34GoNh9J+Xdle2BZrTBhdVipPq+DKvEhZ6XNH+YzPpAMTTqV5i f/E455Ldv6yjjzkLZMsB0CXyFDB5I7rbY//F/jsA5hFHniGFu9wR+dY2QcuBevd6Hq N4GOFkMj+85lEmY5e/8egQcfgooTWPHQNKzPNMG27sBzf0q6Y34oSf9wh9vsA/jMsn nOy8cixx5iX+j54Af7caEX8/tvWYaOqNIVsrOwaKCxGuTbvBIaN+XmeX17AyTE7dfg 3Sm9lXvuR41maGJYZfcSi0B735pCm5IHyfwwm79ubewTcgfRUfYRAGYkGwBVd5maxb fRjU2B0RUVy6A==
X-Mailman-Approved-At: Mon, 10 Jun 2013 07:30:29 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 14:26:13 -0000

--bcaec50dc32c8bcb4004decd8f9c
Content-Type: text/plain; charset=ISO-8859-1

Dan, thanks for looking at this.

As a co-author, I'll weigh in on a couple of things that Ray did not
address.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Mon, Jun 10, 2013 at 2:33 AM, Brandenburg, R. (Ray) van <
ray.vanbrandenburg@tno.nl> wrote:

>
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: zondag 9 juni 2013 9:53
> To: General Area Review Team
> Cc: draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: Gen-ART review of draft-ietf-avtcore-idms-09
>
> (resending, I mis-spelled .all address at the first try)
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
> Document: draft-ietf-avtcore-idms-09
> Reviewer: Dan Romascanu
> Review Date: 6/6/13
> IETF LC End Date: 6/11/13
> IESG Telechat date:
>
> Summary:
>
> Not Ready
>
> Major issues:
>
> 5. In Section 8:
>
>    Because RTP
>    timestamps do wrap around, the sender of this packet SHOULD use
>    recent values, i.e. choose NTP timestamps that reflect current time
>    and not too far in the future or in the past.
>
> Why a SHOULD here and not a MUST? If there are any cases of exception they
> need to be detailed.
>
> [Ray: I will check with my co-authors]
>

[Kevin] Devices that receive these reports need to deal with rollover
conditions both for the RTP timestamp (which can rollover a couple times a
day) and the NTP timestamp (which will have its first rollover in 2036). I
believe these requirements are already stated in RFC3550 and RFC5905
respectively. The suggestion to use recent timestamps in reporting reduces
statistical chance that a receiving device will need to do extra
computation required to handle an RTP rollover. There's no way to eliminate
this possibility altogether and the requirement is stated in a qualitative
way and so could not be enforced as a MUST.

>
> 6. In Section 8:
>
>    This SHOULD relate to the first
>    arriving RTP packet containing this particular RTP timestamp, in case
>    multiple RTP packets contain the same RTP timestamp.
>
> Why a SHOULD here and not a MUST? If there are any cases of exception they
> need to be detailed.
>
> [Ray: I will check with my co-authors]
>

[Kevin] This is an issue that the authors discussed at length and for which
we do not believe there is an optimal solution and so we were reluctant to
require our recommendation. Ideally we want an NTP timestamp indicating
when all data required to render the specified RTP timestamp has arrived.
For this we'd really like to know when the last packet for an RTP timestamp
arrived. In the presence packet loss and reordering, it is not possible to
reliably record the last packet. It is possible to record the first packet
and so this is our recommendation. The accuracy of arrival times is not so
critical in IDMS as arrival time allows a less precise synchronization than
presentation times.

--bcaec50dc32c8bcb4004decd8f9c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dan, thanks for looking at this.<div><br></div><div>As a c=
o-author, I&#39;ll weigh in on a couple of things that Ray did not address.=
<div class=3D"gmail_extra"><br clear=3D"all"><div>Kevin Gross<br><div>+1-30=
3-447-0517</div>
<div>Media Network Consultant<br><div>AVA Networks -=A0<a href=3D"http://ww=
w.avanw.com/" target=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.=
X192.org" target=3D"_blank">www.X192.org</a></div></div></div>
<br><br><div class=3D"gmail_quote">On Mon, Jun 10, 2013 at 2:33 AM, Branden=
burg, R. (Ray) van <span dir=3D"ltr">&lt;<a href=3D"mailto:ray.vanbrandenbu=
rg@tno.nl" target=3D"_blank">ray.vanbrandenburg@tno.nl</a>&gt;</span> wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br><div class=3D"im">
-----Original Message-----<br>
From: Romascanu, Dan (Dan) [mailto:<a href=3D"mailto:dromasca@avaya.com">dr=
omasca@avaya.com</a>]<br>
Sent: zondag 9 juni 2013 9:53<br>
To: General Area Review Team<br>
Cc: <a href=3D"mailto:draft-ietf-avtcore-idms.all@tools.ietf.org">draft-iet=
f-avtcore-idms.all@tools.ietf.org</a><br>
Subject: Gen-ART review of draft-ietf-avtcore-idms-09<br>
<br>
(resending, I mis-spelled .all address at the first try)<br>
<br>
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at<br>
<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" tar=
get=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&=
gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br>
<br>
Document: draft-ietf-avtcore-idms-09<br>
Reviewer: Dan Romascanu<br>
Review Date: 6/6/13<br>
IETF LC End Date: 6/11/13<br>
IESG Telechat date:<br>
<br>
Summary:<br>
<br>
Not Ready<br>
<br>
Major issues:<br>
<br></div><div class=3D"im">
5. In Section 8:<br>
<br>
=A0 =A0Because RTP<br>
=A0 =A0timestamps do wrap around, the sender of this packet SHOULD use<br>
=A0 =A0recent values, i.e. choose NTP timestamps that reflect current time<=
br>
=A0 =A0and not too far in the future or in the past.<br>
<br>
Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.<br>
<br>
</div>[Ray: I will check with my co-authors]<br></blockquote><div><br></div=
><div style>[Kevin] Devices that receive these reports need to deal with ro=
llover conditions both for the RTP timestamp (which can rollover a couple t=
imes a day) and the NTP timestamp (which will have its first rollover in 20=
36). I believe these requirements are already stated in RFC3550 and RFC5905=
 respectively. The suggestion to use recent timestamps in reporting reduces=
 statistical chance that a receiving device will need to do extra computati=
on required to handle an RTP rollover. There&#39;s no way to eliminate this=
 possibility altogether and the requirement is stated in a qualitative way =
and so could not be enforced as a MUST.</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
6. In Section 8:<br>
<br>
=A0 =A0This SHOULD relate to the first<br>
=A0 =A0arriving RTP packet containing this particular RTP timestamp, in cas=
e<br>
=A0 =A0multiple RTP packets contain the same RTP timestamp.<br>
<br>
Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.<br>
<br>
</div>[Ray: I will check with my co-authors]<br></blockquote><div><br></div=
><div style>[Kevin] This is an issue that the authors discussed at length a=
nd for which we do not believe there is an optimal solution and so we were =
reluctant to require our recommendation. Ideally we want an NTP timestamp i=
ndicating when all data required to render the specified RTP timestamp has =
arrived. For this we&#39;d really like to know when the last packet for an =
RTP timestamp arrived. In the presence packet loss and reordering, it is no=
t possible to reliably record the last packet. It is possible to record the=
 first packet and so this is our recommendation. The accuracy of arrival ti=
mes is not so critical in IDMS as arrival time allows a less precise synchr=
onization than presentation times.</div>
</div></div></div></div>

--bcaec50dc32c8bcb4004decd8f9c--

From dromasca@avaya.com  Mon Jun 10 07:34:44 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51CFF21F8F6E; Mon, 10 Jun 2013 07:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.313
X-Spam-Level: 
X-Spam-Status: No, score=-103.313 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEXw1RgbOzKh; Mon, 10 Jun 2013 07:34:37 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 8A78321F8F61; Mon, 10 Jun 2013 07:34:35 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAIritVHGmAcF/2dsb2JhbABagmgheb5CgQQWdIIjAQEBAQIBEig/DAQCAQgNBAQBAQsUCQchERQJCAIEDgUIGodZAwkGAZ1TkwQNiDsXjFuCLDEHBoJ5YQOVWAGIKYVchSSDD4In
X-IronPort-AV: E=Sophos;i="4.87,837,1363147200"; d="scan'208";a="12521285"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jun 2013 10:34:33 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Jun 2013 10:33:04 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 10:34:31 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/A
Date: Mon, 10 Jun 2013 14:34:31 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 14:34:44 -0000

Yes, we seem to get closer and closer, focus on one last issue (and much ag=
reement deleted)

Thanks and Regards,

Dan



> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 5:27 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
> Hi Dan,
>=20
> Please see inline. We seem to be converging:)
>=20
> Ray

> > > 7. In Section 8:
> > >
> > >    The timestamp is formatted based on the NTP
> > >    timestamp format as specified in [RFC5905].  If this field is
> > empty,
> > >    then it SHALL be set to 0.  This field MAY be left empty if none
> or
> > >    only one of the receivers reported on presentation timestamps.
> > >
> > > Why a MAY here? Especially for the case when none of the receivers
> > > reported, what content can be set there but 0 ?
> > >
> > > [Ray: I believe it should be up to the implementation to decide how
> > > it wants to handle the case of there being only one receiver who
> > > reported on presentation timestamps].
> > >
> > [[DR]] OK, so the cases when none of the receivers reported and one
> > receiver only reported should be dealt with differently. This needs to
> > be clarified.
> >
> > [Ray] What exactly is the problem with the MAY here? IMO it doesn't
> > create any interop issues: whatever is the reason for setting the
> > value to 0, to the client the end result is the same: ignore it.
> >
>=20
> [[DR]] In the case when none of the receivers reported we want to avoid
> leaving some garbage in this field which could be interpreted
> differently - don't we?
>=20
> [Ray] I think I see where we disagree. The paragraph says: "If this
> field is empty, then it SHALL be set to 0. This field MAY be left empty
> if none or only one of the receivers reported on presentation
> timestamps". The way I read this is as: In the case the field is
> declared empty (=3D contains NULL information), it SHALL be set to 0.
> There can be different reasons for declaring the field empty/NULL, one
> of those reasons is if none or only one receiver reported on
> presentation timestamps. To me, the paragraph doesn't say that this is
> the only possible reason, but it does specify very clearly that if you
> decide the field should be empty, you SHALL set it to zero.
>=20
>=20

[[DR]] But then, why do not you take out 'if none or' - because for the opt=
ion of 'none' there is no alternative but the 'null' information, and the M=
AY does not make sense.=20

Dan


From dromasca@avaya.com  Mon Jun 10 07:40:33 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C3E21F938E; Mon, 10 Jun 2013 07:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.348
X-Spam-Level: 
X-Spam-Status: No, score=-103.348 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N1TuFurvVW-D; Mon, 10 Jun 2013 07:40:27 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3239421F9399; Mon, 10 Jun 2013 07:40:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AioFAJ7ktVGHCzI1/2dsb2JhbABXA4JFIyEwSbV4iEqBBBZ0giMBAQEBAxIbHDAMBAIBCAcGBAMBAQELHQcyFAkIAgQOBQgTB4drAQudR5tMF48HIAENAwYBBgMIgm5hA5hphRmLAIMPgic
X-IronPort-AV: E=Sophos;i="4.87,837,1363147200"; d="scan'208,217";a="12522144"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jun 2013 10:40:24 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Jun 2013 10:35:37 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 10:40:22 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Kevin Gross <kevin.gross@avanw.com>, "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Thread-Topic: [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: AQHOZeZ7ymQ4hhifMECwBepzBAET3ZkvBFkQ
Date: Mon, 10 Jun 2013 14:40:22 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA199E5B@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <CALw1_Q13icqNLGDuvCOMB-O6Q_LtnjXSvZqG_Tyftuf6BjYCEg@mail.gmail.com>
In-Reply-To: <CALw1_Q13icqNLGDuvCOMB-O6Q_LtnjXSvZqG_Tyftuf6BjYCEg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA199E5BAZFFEXMB04globala_"
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 14:40:33 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA199E5BAZFFEXMB04globala_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Kevin,

Thank you for looking at my comments and for explaining in detail the edito=
rial decisions that you made. Both explanations make sense, and leaving the=
 current text in place is acceptable.

Regards,

Dan



From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Kevin=
 Gross
Sent: Monday, June 10, 2013 5:26 PM
To: Brandenburg, R. (Ray) van
Cc: Romascanu, Dan (Dan); General Area Review Team; avt@ietf.org; draft-iet=
f-avtcore-idms.all@tools.ietf.org
Subject: Re: [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09

Dan, thanks for looking at this.

As a co-author, I'll weigh in on a couple of things that Ray did not addres=
s.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com<http://www.avanw.com/>, www.X192.org<http://ww=
w.X192.org>

On Mon, Jun 10, 2013 at 2:33 AM, Brandenburg, R. (Ray) van <ray.vanbrandenb=
urg@tno.nl<mailto:ray.vanbrandenburg@tno.nl>> wrote:

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com<mailto:dromasca@avaya=
.com>]
Sent: zondag 9 juni 2013 9:53
To: General Area Review Team
Cc: draft-ietf-avtcore-idms.all@tools.ietf.org<mailto:draft-ietf-avtcore-id=
ms.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-avtcore-idms-09

(resending, I mis-spelled .all address at the first try)

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-avtcore-idms-09
Reviewer: Dan Romascanu
Review Date: 6/6/13
IETF LC End Date: 6/11/13
IESG Telechat date:

Summary:

Not Ready

Major issues:
5. In Section 8:

   Because RTP
   timestamps do wrap around, the sender of this packet SHOULD use
   recent values, i.e. choose NTP timestamps that reflect current time
   and not too far in the future or in the past.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.
[Ray: I will check with my co-authors]

[Kevin] Devices that receive these reports need to deal with rollover condi=
tions both for the RTP timestamp (which can rollover a couple times a day) =
and the NTP timestamp (which will have its first rollover in 2036). I belie=
ve these requirements are already stated in RFC3550 and RFC5905 respectivel=
y. The suggestion to use recent timestamps in reporting reduces statistical=
 chance that a receiving device will need to do extra computation required =
to handle an RTP rollover. There's no way to eliminate this possibility alt=
ogether and the requirement is stated in a qualitative way and so could not=
 be enforced as a MUST.

6. In Section 8:

   This SHOULD relate to the first
   arriving RTP packet containing this particular RTP timestamp, in case
   multiple RTP packets contain the same RTP timestamp.

Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.
[Ray: I will check with my co-authors]

[Kevin] This is an issue that the authors discussed at length and for which=
 we do not believe there is an optimal solution and so we were reluctant to=
 require our recommendation. Ideally we want an NTP timestamp indicating wh=
en all data required to render the specified RTP timestamp has arrived. For=
 this we'd really like to know when the last packet for an RTP timestamp ar=
rived. In the presence packet loss and reordering, it is not possible to re=
liably record the last packet. It is possible to record the first packet an=
d so this is our recommendation. The accuracy of arrival times is not so cr=
itical in IDMS as arrival time allows a less precise synchronization than p=
resentation times.

--_000_9904FB1B0159DA42B0B887B7FA8119CA199E5BAZFFEXMB04globala_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Kevin,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thank you for looking at =
my comments and for explaining in detail the editorial decisions that you m=
ade. Both explanations make sense, and leaving the current
 text in place is acceptable. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> avt-boun=
ces@ietf.org [mailto:avt-bounces@ietf.org]
<b>On Behalf Of </b>Kevin Gross<br>
<b>Sent:</b> Monday, June 10, 2013 5:26 PM<br>
<b>To:</b> Brandenburg, R. (Ray) van<br>
<b>Cc:</b> Romascanu, Dan (Dan); General Area Review Team; avt@ietf.org; dr=
aft-ietf-avtcore-idms.all@tools.ietf.org<br>
<b>Subject:</b> Re: [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09<=
o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Dan, thanks for looking at this.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">As a co-author, I'll weigh in on a couple of things =
that Ray did not address.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Kevin Gross<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&#43;1-303-447-0517<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Media Network Consultant<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">AVA Networks -&nbsp;<a href=3D"http://www.avanw.com/=
" target=3D"_blank">www.AVAnw.com</a>,&nbsp;<a href=3D"http://www.X192.org"=
 target=3D"_blank">www.X192.org</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 2:33 AM, Brandenburg, R. (Ra=
y) van &lt;<a href=3D"mailto:ray.vanbrandenburg@tno.nl" target=3D"_blank">r=
ay.vanbrandenburg@tno.nl</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">-----Original Message=
-----<br>
From: Romascanu, Dan (Dan) [mailto:<a href=3D"mailto:dromasca@avaya.com">dr=
omasca@avaya.com</a>]<br>
Sent: zondag 9 juni 2013 9:53<br>
To: General Area Review Team<br>
Cc: <a href=3D"mailto:draft-ietf-avtcore-idms.all@tools.ietf.org">draft-iet=
f-avtcore-idms.all@tools.ietf.org</a><br>
Subject: Gen-ART review of draft-ietf-avtcore-idms-09<br>
<br>
(resending, I mis-spelled .all address at the first try)<br>
<br>
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at<br>
<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" tar=
get=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&=
gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br>
<br>
Document: draft-ietf-avtcore-idms-09<br>
Reviewer: Dan Romascanu<br>
Review Date: 6/6/13<br>
IETF LC End Date: 6/11/13<br>
IESG Telechat date:<br>
<br>
Summary:<br>
<br>
Not Ready<br>
<br>
Major issues:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">5. In Section 8:<br>
<br>
&nbsp; &nbsp;Because RTP<br>
&nbsp; &nbsp;timestamps do wrap around, the sender of this packet SHOULD us=
e<br>
&nbsp; &nbsp;recent values, i.e. choose NTP timestamps that reflect current=
 time<br>
&nbsp; &nbsp;and not too far in the future or in the past.<br>
<br>
Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">[Ray: I will check with my co-authors]<o:p></o:p></p=
>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[Kevin] Devices that receive these reports need to d=
eal with rollover conditions both for the RTP timestamp (which can rollover=
 a couple times a day) and the NTP timestamp (which will have its first rol=
lover in 2036). I believe these requirements
 are already stated in RFC3550 and RFC5905 respectively. The suggestion to =
use recent timestamps in reporting reduces statistical chance that a receiv=
ing device will need to do extra computation required to handle an RTP roll=
over. There's no way to eliminate
 this possibility altogether and the requirement is stated in a qualitative=
 way and so could not be enforced as a MUST.<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
6. In Section 8:<br>
<br>
&nbsp; &nbsp;This SHOULD relate to the first<br>
&nbsp; &nbsp;arriving RTP packet containing this particular RTP timestamp, =
in case<br>
&nbsp; &nbsp;multiple RTP packets contain the same RTP timestamp.<br>
<br>
Why a SHOULD here and not a MUST? If there are any cases of exception they =
need to be detailed.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">[Ray: I will check with my co-authors]<o:p></o:p></p=
>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[Kevin] This is an issue that the authors discussed =
at length and for which we do not believe there is an optimal solution and =
so we were reluctant to require our recommendation. Ideally we want an NTP =
timestamp indicating when all data
 required to render the specified RTP timestamp has arrived. For this we'd =
really like to know when the last packet for an RTP timestamp arrived. In t=
he presence packet loss and reordering, it is not possible to reliably reco=
rd the last packet. It is possible
 to record the first packet and so this is our recommendation. The accuracy=
 of arrival times is not so critical in IDMS as arrival time allows a less =
precise synchronization than presentation times.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA199E5BAZFFEXMB04globala_--

From ray.vanbrandenburg@tno.nl  Mon Jun 10 07:52:02 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCC0721F9408; Mon, 10 Jun 2013 07:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z5DVMoDCyV7b; Mon, 10 Jun 2013 07:51:57 -0700 (PDT)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 82B0B21F8EF7; Mon, 10 Jun 2013 07:51:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,837,1363129200";  d="scan'208";a="9669333"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1a.tno.nl with ESMTP; 10 Jun 2013 16:51:50 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.85]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 16:51:49 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/AAACXwtA=
Date: Mon, 10 Jun 2013 14:51:49 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 14:52:03 -0000

Hi Dan,

See below...

Best regards,

Ray

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] =

Sent: maandag 10 juni 2013 16:35
To: Brandenburg, R. (Ray) van
Cc: avt@ietf.org; General Area Review Team; Roni Even (ron.even.tlv@gmail.c=
om); draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09


Yes, we seem to get closer and closer, focus on one last issue (and much ag=
reement deleted)

Thanks and Regards,

Dan



> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 5:27 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> =

> Hi Dan,
> =

> Please see inline. We seem to be converging:)
> =

> Ray

> > > 7. In Section 8:
> > >
> > >    The timestamp is formatted based on the NTP
> > >    timestamp format as specified in [RFC5905].  If this field is
> > empty,
> > >    then it SHALL be set to 0.  This field MAY be left empty if =

> > > none
> or
> > >    only one of the receivers reported on presentation timestamps.
> > >
> > > Why a MAY here? Especially for the case when none of the receivers =

> > > reported, what content can be set there but 0 ?
> > >
> > > [Ray: I believe it should be up to the implementation to decide =

> > > how it wants to handle the case of there being only one receiver =

> > > who reported on presentation timestamps].
> > >
> > [[DR]] OK, so the cases when none of the receivers reported and one =

> > receiver only reported should be dealt with differently. This needs =

> > to be clarified.
> >
> > [Ray] What exactly is the problem with the MAY here? IMO it doesn't =

> > create any interop issues: whatever is the reason for setting the =

> > value to 0, to the client the end result is the same: ignore it.
> >
> =

> [[DR]] In the case when none of the receivers reported we want to =

> avoid leaving some garbage in this field which could be interpreted =

> differently - don't we?
> =

> [Ray] I think I see where we disagree. The paragraph says: "If this =

> field is empty, then it SHALL be set to 0. This field MAY be left =

> empty if none or only one of the receivers reported on presentation =

> timestamps". The way I read this is as: In the case the field is =

> declared empty (=3D contains NULL information), it SHALL be set to 0.
> There can be different reasons for declaring the field empty/NULL, one =

> of those reasons is if none or only one receiver reported on =

> presentation timestamps. To me, the paragraph doesn't say that this is =

> the only possible reason, but it does specify very clearly that if you =

> decide the field should be empty, you SHALL set it to zero.
> =

> =


[[DR]] But then, why do not you take out 'if none or' - because for the opt=
ion of 'none' there is no alternative but the 'null' information, and the M=
AY does not make sense. =


[Ray] The fact that no receiver reported on the packet presentation timesta=
mp does not necessarily mean that the MSAS does not want to indicate a prop=
osed packet presentation timestamp. The absence of such reports just means =
that the proposed playout moment might not be realistic, or be supported by=
 any receiver. =


Dan
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From dromasca@avaya.com  Mon Jun 10 07:57:23 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7AEC21F95D7; Mon, 10 Jun 2013 07:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.377
X-Spam-Level: 
X-Spam-Status: No, score=-103.377 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 47YXCJLzOHJi; Mon, 10 Jun 2013 07:57:11 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 734D421F938E; Mon, 10 Jun 2013 07:57:01 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAJTotVGHCzI1/2dsb2JhbABagmgheb5CgQQWdIIjAQEBAQMSKD8MBAIBCA0EBAEBCxQJByERFAkIAgQOBQgah1kDDwGdUpMJDYg7F4xbgiwxBwaCeWEDlVgBiCmFXIUkgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,837,1363147200"; d="scan'208";a="12524860"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jun 2013 10:56:59 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Jun 2013 10:52:12 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 16:56:57 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/AAACXwtAAACxhQA==
Date: Mon, 10 Jun 2013 14:56:56 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 14:57:23 -0000
X-List-Received-Date: Mon, 10 Jun 2013 14:57:23 -0000

> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 5:52 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
> Hi Dan,
>=20
> See below...
>=20
> Best regards,
>=20
> Ray
>=20
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: maandag 10 juni 2013 16:35
> To: Brandenburg, R. (Ray) van
> Cc: avt@ietf.org; General Area Review Team; Roni Even
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
>=20
> Yes, we seem to get closer and closer, focus on one last issue (and much
> agreement deleted)
>=20
> Thanks and Regards,
>=20
> Dan
>=20
>=20
>=20
> > -----Original Message-----
> > From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> > Sent: Monday, June 10, 2013 5:27 PM
> > To: Romascanu, Dan (Dan)
> > Cc: avt@ietf.org; General Area Review Team; Roni Even
> > (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> > Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >
> > Hi Dan,
> >
> > Please see inline. We seem to be converging:)
> >
> > Ray
>=20
> > > > 7. In Section 8:
> > > >
> > > >    The timestamp is formatted based on the NTP
> > > >    timestamp format as specified in [RFC5905].  If this field is
> > > empty,
> > > >    then it SHALL be set to 0.  This field MAY be left empty if
> > > > none
> > or
> > > >    only one of the receivers reported on presentation timestamps.
> > > >
> > > > Why a MAY here? Especially for the case when none of the receivers
> > > > reported, what content can be set there but 0 ?
> > > >
> > > > [Ray: I believe it should be up to the implementation to decide
> > > > how it wants to handle the case of there being only one receiver
> > > > who reported on presentation timestamps].
> > > >
> > > [[DR]] OK, so the cases when none of the receivers reported and one
> > > receiver only reported should be dealt with differently. This needs
> > > to be clarified.
> > >
> > > [Ray] What exactly is the problem with the MAY here? IMO it doesn't
> > > create any interop issues: whatever is the reason for setting the
> > > value to 0, to the client the end result is the same: ignore it.
> > >
> >
> > [[DR]] In the case when none of the receivers reported we want to
> > avoid leaving some garbage in this field which could be interpreted
> > differently - don't we?
> >
> > [Ray] I think I see where we disagree. The paragraph says: "If this
> > field is empty, then it SHALL be set to 0. This field MAY be left
> > empty if none or only one of the receivers reported on presentation
> > timestamps". The way I read this is as: In the case the field is
> > declared empty (=3D contains NULL information), it SHALL be set to 0.
> > There can be different reasons for declaring the field empty/NULL, one
> > of those reasons is if none or only one receiver reported on
> > presentation timestamps. To me, the paragraph doesn't say that this is
> > the only possible reason, but it does specify very clearly that if you
> > decide the field should be empty, you SHALL set it to zero.
> >
> >
>=20
> [[DR]] But then, why do not you take out 'if none or' - because for the
> option of 'none' there is no alternative but the 'null' information, and
> the MAY does not make sense.
>=20
> [Ray] The fact that no receiver reported on the packet presentation
> timestamp does not necessarily mean that the MSAS does not want to
> indicate a proposed packet presentation timestamp. The absence of such
> reports just means that the proposed playout moment might not be
> realistic, or be supported by any receiver.
>=20

[[DR]] yes, but is the field set to anything but 0 in such cases?=20

Dan

From ray.vanbrandenburg@tno.nl  Mon Jun 10 08:06:15 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75BB21F96F5; Mon, 10 Jun 2013 08:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozH18FxEojmB; Mon, 10 Jun 2013 08:06:09 -0700 (PDT)
Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 7602321F9732; Mon, 10 Jun 2013 08:06:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,837,1363129200";  d="scan'208";a="1611512"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1b.tno.nl with ESMTP; 10 Jun 2013 17:05:59 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.85]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 17:05:59 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/AAACXwtAAACxhQAAAZQ1g
Date: Mon, 10 Jun 2013 15:05:58 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581F34D520@EXC-MBX03.tsn.tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.153]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 15:06:15 -0000

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] =

Sent: maandag 10 juni 2013 16:57
To: Brandenburg, R. (Ray) van
Cc: avt@ietf.org; General Area Review Team; Roni Even (ron.even.tlv@gmail.c=
om); draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09





> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 5:52 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> =

> Hi Dan,
> =

> See below...
> =

> Best regards,
> =

> Ray
> =

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: maandag 10 juni 2013 16:35
> To: Brandenburg, R. (Ray) van
> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> =

> =

> Yes, we seem to get closer and closer, focus on one last issue (and =

> much agreement deleted)
> =

> Thanks and Regards,
> =

> Dan
> =

> =

> =

> > -----Original Message-----
> > From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> > Sent: Monday, June 10, 2013 5:27 PM
> > To: Romascanu, Dan (Dan)
> > Cc: avt@ietf.org; General Area Review Team; Roni Even =

> > (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> > Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >
> > Hi Dan,
> >
> > Please see inline. We seem to be converging:)
> >
> > Ray
> =

> > > > 7. In Section 8:
> > > >
> > > >    The timestamp is formatted based on the NTP
> > > >    timestamp format as specified in [RFC5905].  If this field is
> > > empty,
> > > >    then it SHALL be set to 0.  This field MAY be left empty if =

> > > > none
> > or
> > > >    only one of the receivers reported on presentation timestamps.
> > > >
> > > > Why a MAY here? Especially for the case when none of the =

> > > > receivers reported, what content can be set there but 0 ?
> > > >
> > > > [Ray: I believe it should be up to the implementation to decide =

> > > > how it wants to handle the case of there being only one receiver =

> > > > who reported on presentation timestamps].
> > > >
> > > [[DR]] OK, so the cases when none of the receivers reported and =

> > > one receiver only reported should be dealt with differently. This =

> > > needs to be clarified.
> > >
> > > [Ray] What exactly is the problem with the MAY here? IMO it =

> > > doesn't create any interop issues: whatever is the reason for =

> > > setting the value to 0, to the client the end result is the same: ign=
ore it.
> > >
> >
> > [[DR]] In the case when none of the receivers reported we want to =

> > avoid leaving some garbage in this field which could be interpreted =

> > differently - don't we?
> >
> > [Ray] I think I see where we disagree. The paragraph says: "If this =

> > field is empty, then it SHALL be set to 0. This field MAY be left =

> > empty if none or only one of the receivers reported on presentation =

> > timestamps". The way I read this is as: In the case the field is =

> > declared empty (=3D contains NULL information), it SHALL be set to 0.
> > There can be different reasons for declaring the field empty/NULL, =

> > one of those reasons is if none or only one receiver reported on =

> > presentation timestamps. To me, the paragraph doesn't say that this =

> > is the only possible reason, but it does specify very clearly that =

> > if you decide the field should be empty, you SHALL set it to zero.
> >
> >
> =

> [[DR]] But then, why do not you take out 'if none or' - because for =

> the option of 'none' there is no alternative but the 'null' =

> information, and the MAY does not make sense.
> =

> [Ray] The fact that no receiver reported on the packet presentation =

> timestamp does not necessarily mean that the MSAS does not want to =

> indicate a proposed packet presentation timestamp. The absence of such =

> reports just means that the proposed playout moment might not be =

> realistic, or be supported by any receiver.
> =


[[DR]] yes, but is the field set to anything but 0 in such cases? =


[Ray] If the MSAS decides to leave the field empty, it is set to 0 accordin=
g to the SHALL. If the MSAS decides to include a timestamp anyway, it is se=
t to whatever value the MSAS proposes. =


Dan
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From dromasca@avaya.com  Mon Jun 10 08:11:40 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE5121F8EAE; Mon, 10 Jun 2013 08:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level: 
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aQfo6EzEssCk; Mon, 10 Jun 2013 08:11:34 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id B08C121F8FB6; Mon, 10 Jun 2013 08:11:33 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFACfstVHGmAcF/2dsb2JhbABagmgheb5CgQQWdIIjAQEBAQMSKD8MBAIBCA0EBAEBCxQJByERFAkIAgQOBQgah1kDDwGdUJMLDYg7F4xbgiwxBwaCeWEDlVgBiCmFXIUkgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,837,1363147200"; d="scan'208";a="12527806"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jun 2013 11:11:32 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Jun 2013 11:10:03 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 17:11:30 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/AAACXwtAAACxhQAAAZQ1gAAAuajA=
Date: Mon, 10 Jun 2013 15:11:29 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA199F21@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D520@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34D520@EXC-MBX03.tsn.tno.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 15:11:41 -0000

> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 6:06 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
>=20
>=20
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: maandag 10 juni 2013 16:57
> To: Brandenburg, R. (Ray) van
> Cc: avt@ietf.org; General Area Review Team; Roni Even
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> > Sent: Monday, June 10, 2013 5:52 PM
> > To: Romascanu, Dan (Dan)
> > Cc: avt@ietf.org; General Area Review Team; Roni Even
> > (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> > Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >
> > Hi Dan,
> >
> > See below...
> >
> > Best regards,
> >
> > Ray
> >
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: maandag 10 juni 2013 16:35
> > To: Brandenburg, R. (Ray) van
> > Cc: avt@ietf.org; General Area Review Team; Roni Even
> > (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> > Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >
> >
> > Yes, we seem to get closer and closer, focus on one last issue (and
> > much agreement deleted)
> >
> > Thanks and Regards,
> >
> > Dan
> >
> >
> >
> > > -----Original Message-----
> > > From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> > > Sent: Monday, June 10, 2013 5:27 PM
> > > To: Romascanu, Dan (Dan)
> > > Cc: avt@ietf.org; General Area Review Team; Roni Even
> > > (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> > > Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> > >
> > > Hi Dan,
> > >
> > > Please see inline. We seem to be converging:)
> > >
> > > Ray
> >
> > > > > 7. In Section 8:
> > > > >
> > > > >    The timestamp is formatted based on the NTP
> > > > >    timestamp format as specified in [RFC5905].  If this field is
> > > > empty,
> > > > >    then it SHALL be set to 0.  This field MAY be left empty if
> > > > > none
> > > or
> > > > >    only one of the receivers reported on presentation
> timestamps.
> > > > >
> > > > > Why a MAY here? Especially for the case when none of the
> > > > > receivers reported, what content can be set there but 0 ?
> > > > >
> > > > > [Ray: I believe it should be up to the implementation to decide
> > > > > how it wants to handle the case of there being only one receiver
> > > > > who reported on presentation timestamps].
> > > > >
> > > > [[DR]] OK, so the cases when none of the receivers reported and
> > > > one receiver only reported should be dealt with differently. This
> > > > needs to be clarified.
> > > >
> > > > [Ray] What exactly is the problem with the MAY here? IMO it
> > > > doesn't create any interop issues: whatever is the reason for
> > > > setting the value to 0, to the client the end result is the same:
> ignore it.
> > > >
> > >
> > > [[DR]] In the case when none of the receivers reported we want to
> > > avoid leaving some garbage in this field which could be interpreted
> > > differently - don't we?
> > >
> > > [Ray] I think I see where we disagree. The paragraph says: "If this
> > > field is empty, then it SHALL be set to 0. This field MAY be left
> > > empty if none or only one of the receivers reported on presentation
> > > timestamps". The way I read this is as: In the case the field is
> > > declared empty (=3D contains NULL information), it SHALL be set to 0.
> > > There can be different reasons for declaring the field empty/NULL,
> > > one of those reasons is if none or only one receiver reported on
> > > presentation timestamps. To me, the paragraph doesn't say that this
> > > is the only possible reason, but it does specify very clearly that
> > > if you decide the field should be empty, you SHALL set it to zero.
> > >
> > >
> >
> > [[DR]] But then, why do not you take out 'if none or' - because for
> > the option of 'none' there is no alternative but the 'null'
> > information, and the MAY does not make sense.
> >
> > [Ray] The fact that no receiver reported on the packet presentation
> > timestamp does not necessarily mean that the MSAS does not want to
> > indicate a proposed packet presentation timestamp. The absence of such
> > reports just means that the proposed playout moment might not be
> > realistic, or be supported by any receiver.
> >
>=20
> [[DR]] yes, but is the field set to anything but 0 in such cases?
>=20
> [Ray] If the MSAS decides to leave the field empty, it is set to 0
> according to the SHALL. If the MSAS decides to include a timestamp
> anyway, it is set to whatever value the MSAS proposes.
>=20

[[DR]] So two different implementations may behave differently in similar s=
ituations. Is this a problem?=20

Dan


From ray.vanbrandenburg@tno.nl  Mon Jun 10 09:19:07 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35DB821F9649; Mon, 10 Jun 2013 09:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbW-mHh3OHXI; Mon, 10 Jun 2013 09:19:02 -0700 (PDT)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEE621F93D4; Mon, 10 Jun 2013 09:19:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,838,1363129200";  d="scan'208";a="9673876"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1a.tno.nl with ESMTP; 10 Jun 2013 18:18:46 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.85]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 18:18:46 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/AAACXwtAAACxhQAAAZQ1gAAAuajAAAmW0KA==
Date: Mon, 10 Jun 2013 16:18:44 +0000
Message-ID: <3DFD3155-BBD9-4BE0-8912-81B92C93D3CB@tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D520@EXC-MBX03.tsn.tno.nl>, <9904FB1B0159DA42B0B887B7FA8119CA199F21@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA199F21@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 16:19:07 -0000

On 10 jun. 2013, at 17:11, "Romascanu, Dan (Dan)" <dromasca@avaya.com> wrot=
e:

> =

> =

> =

> =

>> -----Original Message-----
>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
>> Sent: Monday, June 10, 2013 6:06 PM
>> To: Romascanu, Dan (Dan)
>> Cc: avt@ietf.org; General Area Review Team; Roni Even
>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>> =

>> =

>> =

>> -----Original Message-----
>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
>> Sent: maandag 10 juni 2013 16:57
>> To: Brandenburg, R. (Ray) van
>> Cc: avt@ietf.org; General Area Review Team; Roni Even
>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>> =

>> =

>> =

>> =

>> =

>>> -----Original Message-----
>>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
>>> Sent: Monday, June 10, 2013 5:52 PM
>>> To: Romascanu, Dan (Dan)
>>> Cc: avt@ietf.org; General Area Review Team; Roni Even
>>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>> =

>>> Hi Dan,
>>> =

>>> See below...
>>> =

>>> Best regards,
>>> =

>>> Ray
>>> =

>>> -----Original Message-----
>>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
>>> Sent: maandag 10 juni 2013 16:35
>>> To: Brandenburg, R. (Ray) van
>>> Cc: avt@ietf.org; General Area Review Team; Roni Even
>>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>> =

>>> =

>>> Yes, we seem to get closer and closer, focus on one last issue (and
>>> much agreement deleted)
>>> =

>>> Thanks and Regards,
>>> =

>>> Dan
>>> =

>>> =

>>> =

>>>> -----Original Message-----
>>>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
>>>> Sent: Monday, June 10, 2013 5:27 PM
>>>> To: Romascanu, Dan (Dan)
>>>> Cc: avt@ietf.org; General Area Review Team; Roni Even
>>>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
>>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>>> =

>>>> Hi Dan,
>>>> =

>>>> Please see inline. We seem to be converging:)
>>>> =

>>>> Ray
>>> =

>>>>>> 7. In Section 8:
>>>>>> =

>>>>>>   The timestamp is formatted based on the NTP
>>>>>>   timestamp format as specified in [RFC5905].  If this field is
>>>>> empty,
>>>>>>   then it SHALL be set to 0.  This field MAY be left empty if
>>>>>> none
>>>> or
>>>>>>   only one of the receivers reported on presentation
>> timestamps.
>>>>>> =

>>>>>> Why a MAY here? Especially for the case when none of the
>>>>>> receivers reported, what content can be set there but 0 ?
>>>>>> =

>>>>>> [Ray: I believe it should be up to the implementation to decide
>>>>>> how it wants to handle the case of there being only one receiver
>>>>>> who reported on presentation timestamps].
>>>>>> =

>>>>> [[DR]] OK, so the cases when none of the receivers reported and
>>>>> one receiver only reported should be dealt with differently. This
>>>>> needs to be clarified.
>>>>> =

>>>>> [Ray] What exactly is the problem with the MAY here? IMO it
>>>>> doesn't create any interop issues: whatever is the reason for
>>>>> setting the value to 0, to the client the end result is the same:
>> ignore it.
>>>>> =

>>>> =

>>>> [[DR]] In the case when none of the receivers reported we want to
>>>> avoid leaving some garbage in this field which could be interpreted
>>>> differently - don't we?
>>>> =

>>>> [Ray] I think I see where we disagree. The paragraph says: "If this
>>>> field is empty, then it SHALL be set to 0. This field MAY be left
>>>> empty if none or only one of the receivers reported on presentation
>>>> timestamps". The way I read this is as: In the case the field is
>>>> declared empty (=3D contains NULL information), it SHALL be set to 0.
>>>> There can be different reasons for declaring the field empty/NULL,
>>>> one of those reasons is if none or only one receiver reported on
>>>> presentation timestamps. To me, the paragraph doesn't say that this
>>>> is the only possible reason, but it does specify very clearly that
>>>> if you decide the field should be empty, you SHALL set it to zero.
>>>> =

>>>> =

>>> =

>>> [[DR]] But then, why do not you take out 'if none or' - because for
>>> the option of 'none' there is no alternative but the 'null'
>>> information, and the MAY does not make sense.
>>> =

>>> [Ray] The fact that no receiver reported on the packet presentation
>>> timestamp does not necessarily mean that the MSAS does not want to
>>> indicate a proposed packet presentation timestamp. The absence of such
>>> reports just means that the proposed playout moment might not be
>>> realistic, or be supported by any receiver.
>>> =

>> =

>> [[DR]] yes, but is the field set to anything but 0 in such cases?
>> =

>> [Ray] If the MSAS decides to leave the field empty, it is set to 0
>> according to the SHALL. If the MSAS decides to include a timestamp
>> anyway, it is set to whatever value the MSAS proposes.
>> =

> =

> [[DR]] So two different implementations may behave differently in similar=
 situations. Is this a problem? =

> =


No, I don't think it is a problem if two different MSAS implementations beh=
ave differently in this regard. I see it as server-side configuration. Anyw=
ay, even if we would replace the MAY with a SHOULD or remove the sentence a=
ll together, there would still be different implementations: for example, l=
et's say we have a sync group of 12 devices, with 7 of them reporting prese=
ntation timestamps. What should the MSAS do? Set the field in the IDMS Sett=
ings Packet to 0 or not? I feel this decision should be up to the implement=
ation as I don't see an advantage to us specifying either one way or the ot=
her. =


Ray



> Dan
> =

This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From abegen@cisco.com  Mon Jun 10 09:24:48 2013
Return-Path: <abegen@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB2021F8EF2 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 09:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.448
X-Spam-Level: 
X-Spam-Status: No, score=-10.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjDxkHM0C6fQ for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 09:24:44 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id ACF3921F9622 for <gen-art@ietf.org>; Mon, 10 Jun 2013 09:24:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18365; q=dns/txt; s=iport; t=1370881483; x=1372091083; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=ejisfHCYPNoTaHotOCahBMN13QB/+kIJMfHx39xYakA=; b=Uu3BhOD0eMcnywMkY4mzvy9oY3A3rt59v6S/q4WvPs54ZoHVfITUucfJ /8mlJcKEFaRI8n/6YVS09MvQ2rRrmAcegWloNirb8BuDQEN2F014XzzXZ Cij3Fppq3JykXBpcoQGBp9Ziq6LRSCFfmduQQK+m4g45XVlBlGA5FPYl3 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFANP8tVGtJV2d/2dsb2JhbABagkUjITBJgnSzBYhKDXgWdIIjAQEBBCMKTBIBCBEDAQILHQMCBDAUCQgBAQQBDQUIiAUBC6gnkTWPBxYKEQYBgkwzYQOYaZAZgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,838,1363132800";  d="scan'208,217";a="221043301"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 10 Jun 2013 16:24:43 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r5AGOgAt030617 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Jun 2013 16:24:43 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 11:24:42 -0500
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-ietf-avtcore-6222bis-03
Thread-Index: Ac5luxdWTPgVtsT2RrKnG3rZqnZqqgAfvh8A
Date: Mon, 10 Jun 2013 16:24:39 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940D13003A@xmb-aln-x01.cisco.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C386F68@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.86.240.73]
Content-Type: multipart/alternative; boundary="_000_C15918F2FCDA0243A7C919DA7C4BE9940D13003Axmbalnx01ciscoc_"
MIME-Version: 1.0
Cc: "draft-ietf-avtcore-6222bis.all@tools.ietf.org" <draft-ietf-avtcore-6222bis.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-ietf-avtcore-6222bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 16:24:48 -0000

--_000_C15918F2FCDA0243A7C919DA7C4BE9940D13003Axmbalnx01ciscoc_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RnJvbTogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxt
YWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4NCkRhdGU6IE1vbmRheSwgSnVu
ZSAxMCwgMjAxMyAxMjoxNiBQTQ0KVG86ICJnZW4tYXJ0QGlldGYub3JnPG1haWx0bzpnZW4tYXJ0
QGlldGYub3JnPiIgPGdlbi1hcnRAaWV0Zi5vcmc8bWFpbHRvOmdlbi1hcnRAaWV0Zi5vcmc+Pg0K
Q2M6ICJkcmFmdC1pZXRmLWF2dGNvcmUtNjIyMmJpcy5hbGxAdG9vbHMuaWV0Zi5vcmc8bWFpbHRv
OmRyYWZ0LWlldGYtYXZ0Y29yZS02MjIyYmlzLmFsbEB0b29scy5pZXRmLm9yZz4iIDxkcmFmdC1p
ZXRmLWF2dGNvcmUtNjIyMmJpcy5hbGxAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYt
YXZ0Y29yZS02MjIyYmlzLmFsbEB0b29scy5pZXRmLm9yZz4+DQpTdWJqZWN0OiBHZW5hcnQgcmV2
aWV3IG9mIGRyYWZ0LWlldGYtYXZ0Y29yZS02MjIyYmlzLTAzDQpSZXNlbnQtRnJvbTogPGRyYWZ0
LWFsaWFzLWJvdW5jZXNAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWFsaWFzLWJvdW5jZXNA
dG9vbHMuaWV0Zi5vcmc+Pg0KUmVzZW50LVRvOiAiQWxpIEMuIEJlZ2VuIiA8YWJlZ2VuQGNpc2Nv
LmNvbTxtYWlsdG86YWJlZ2VuQGNpc2NvLmNvbT4+LCBDb2xpbiBQZXJraW5zIDxjc3BAY3NwZXJr
aW5zLm9yZzxtYWlsdG86Y3NwQGNzcGVya2lucy5vcmc+PiwgRGFuIFdpbmcgPGR3aW5nQGNpc2Nv
LmNvbTxtYWlsdG86ZHdpbmdAY2lzY28uY29tPj4sIDxla3JAcnRmbS5jb208bWFpbHRvOmVrckBy
dGZtLmNvbT4+LCBNYWdudXMgV2VzdGVybHVuZCA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24u
Y29tPG1haWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20+PiwgUmljaGFyZCBCYXJu
ZXMgPHJsYkBpcHYuc3g8bWFpbHRvOnJsYkBpcHYuc3g+PiwgPHJvbmkuZXZlbkBtYWlsMDEuaHVh
d2VpLmNvbTxtYWlsdG86cm9uaS5ldmVuQG1haWwwMS5odWF3ZWkuY29tPj4NClJlc2VudC1EYXRl
OiBNb25kYXksIEp1bmUgMTAsIDIwMTMgMTI6MTYgUE0NCg0KDQpJIGFtIHRoZSBhc3NpZ25lZCBH
ZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBGb3IgYmFja2dyb3VuZCBvbiBHZW4tQVJU
LCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQgPGh0dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEv
Z2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+DQoNCg0KDQpEb2N1bWVudDogICAgICAgICAgICAgICAg
ICAgICAgICAgZHJhZnQtaWV0Zi1hdnRjb3JlLTYyMjJiaXMtMDMNCg0KDQoNClJldmlld2VyOiAg
ICAgICAgICAgICAgICAgICAgICAgICAgIENocmlzdGVyIEhvbG1iZXJnDQoNCg0KDQpSZXZpZXcg
RGF0ZTogICAgICAgICAgICAgICAgICAgICAxMCBKdW5lIDIwMTMNCg0KDQoNCklFVEYgTEMgRW5k
IERhdGU6ICAgICAgICAgICAgIDExIEp1bmUgMjAxMw0KDQoNCg0KSUVURiBUZWxlY2hhdCBEYXRl
OiAgICAgICAgIE4vQQ0KDQoNCg0KU3VtbWFyeTogIFRoZXJlIGlzIGEgbWlub3IgaXNzdWUsIGRl
c2NyaWJlZCBiZWxvdywgdGhhdCBJIHRoaW5rIHNob3VsZCBiZSBjbGFyaWZpZWQgYmVmb3JlIHRo
ZSBkb2N1bWVudCBpcyBwdWJsaXNoZWQuDQoNCg0KDQpNYWpvciBJc3N1ZXM6IE5vbmUNCg0KDQoN
Ck1pbm9yIElzc3VlczoNCg0KDQoNClNlY3Rpb24gNC4xIHNheXM6DQoNCg0KDQogICDigJxUaGUg
UlRDUCBDTkFNRSBjYW4gYmUgZWl0aGVyIHBlcnNpc3RlbnQgYWNyb3NzIGRpZmZlcmVudCBSVFAg
c2Vzc2lvbnMNCg0KICAgZm9yIGFuIFJUUCBlbmRwb2ludCBvciB1bmlxdWUgcGVyIHNlc3Npb24s
IG1lYW5pbmcgdGhhdCBhbiBSVFANCg0KICAgZW5kcG9pbnQgY2hvb3NlcyBhIGRpZmZlcmVudCBS
VENQIENOQU1FIGZvciBlYWNoIFJUUCBzZXNzaW9uLuKAnQ0KDQoNCg0K4oCmYW5kOg0KDQoNCg0K
ICAg4oCcQW4gUlRQIGVuZHBvaW50IHRoYXQgaXMgZW1pdHRpbmcgbXVsdGlwbGUgcmVsYXRlZCBS
VFAgc3RyZWFtcyB0aGF0DQoNCiAgIHJlcXVpcmUgc3luY2hyb25pemF0aW9uIGF0IHRoZSBvdGhl
ciBlbmRwb2ludChzKSBNVVNUIHVzZSB0aGUgc2FtZQ0KDQogICBSVENQIENOQU1FIGZvciBhbGwg
c3RyZWFtcyB0aGF0IGFyZSB0byBiZSBzeW5jaHJvbml6ZWQuICBUaGlzDQoNCiAgIHJlcXVpcmVz
IGEgc2hvcnQtdGVybSBwZXJzaXN0ZW50IFJUQ1AgQ05BTUUgdGhhdCBpcyBjb21tb24gYWNyb3Nz
DQoNCiAgIHNldmVyYWwgUlRQIHN0cmVhbXMsIGFuZCBwb3RlbnRpYWxseSBhY3Jvc3Mgc2V2ZXJh
bCByZWxhdGVkIFJUUA0KDQogICBzZXNzaW9ucy4gIEEgY29tbW9uIGV4YW1wbGUgb2Ygc3VjaCB1
c2Ugb2NjdXJzIHdoZW4gbGlwLXN5bmNpbmcgYXVkaW8NCg0KICAgYW5kIHZpZGVvIHN0cmVhbXMg
aW4gYSBtdWx0aW1lZGlhIHNlc3Npb24sIHdoZXJlIGEgc2luZ2xlIHBhcnRpY2lwYW50DQoNCiAg
IGhhcyB0byB1c2UgdGhlIHNhbWUgUlRDUCBDTkFNRSBmb3IgaXRzIGF1ZGlvIFJUUCBzZXNzaW9u
IGFuZCBmb3IgaXRzDQoNCiAgIHZpZGVvIFJUUCBzZXNzaW9uLiAgQW5vdGhlciBleGFtcGxlIG1p
Z2h0IGJlIHRvIHN5bmNocm9uaXplIHRoZQ0KDQogICBsYXllcnMgb2YgYSBsYXllcmVkIGF1ZGlv
IGNvZGVjLCB3aGVyZSB0aGUgc2FtZSBSVENQIENOQU1FIGhhcyB0byBiZQ0KDQogICB1c2VkIGZv
ciBlYWNoIGxheWVyLuKAnQ0KDQoNCg0K4oCmZXRjLg0KDQoNCg0KVGhlIHRleHQgdGFsa3MgYWJv
dXQgdGhlIENOQU1FIGJlaW5nIHVuaXF1ZSB3aXRoaW4gYW4gUlRQIHNlc3Npb24sIG9yIHRvIHNw
YW4gb3ZlciBtdWx0aXBsZSBSVFAgc2Vzc2lvbnMsIGJ1dCBpdCBzZWVtcyB0byBvbWl0IHRoYXQs
ICp3aXRoaW4qIGFuIFJUUCBzZXNzaW9uLCB5b3UgY2FuIGFsc28gdXNlICpkaWZmZXJlbnQqIENO
QU1FIHZhbHVlcywgaWYgZS5nLiB0aGVyZSBpcyBubyBzeW5jaHJvbml6YXRpb24gcmVxdWlyZW1l
bnQgYmV0d2VlbiB0aGUgUlRQIHN0cmVhbXMuDQoNCkRvIHlvdSB0aGluayB3ZSBzaG91bGQgYWRk
IHRoZSBmb2xsb3dpbmcgc2VudGVuY2UgYmVsb3cgdGhlIHNlY29uZCBwYXJhZ3JhcGggeW91IHF1
b3RlIGFib3ZlPw0KDQpJZiB0aGUgbXVsdGlwbGUgUlRQIHN0cmVhbXMgaW4gYW4gUlRQIHNlc3Np
b24gYXJlIG5vdCByZWxhdGVkLCB0aHVzIGRvIG5vdCByZXF1aXJlIHN5bmNocm9uaXphdGlvbiwg
YW4gUlRQIGVuZHBvaW50IGNhbiB1c2UgZGlmZmVyZW50IFJUQ1AgQ05BTUVzIGZvciB0aGVzZSBz
dHJlYW1zLg0KDQoNCg0KDQoNCg0KRWRpdG9yaWFsIG5pdHM6IE5vbmUNCg0KDQoNCkJlc3QgcmVn
YXJkcywNCg0KDQoNCkNocmlzdGVyDQoNCg0KDQo=

--_000_C15918F2FCDA0243A7C919DA7C4BE9940D13003Axmbalnx01ciscoc_
Content-Type: text/html; charset="utf-8"
Content-ID: <DC20BE131A59634789E98D4C0A2412AC@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ29uc29sYXMsIHNhbnMtc2VyaWY7ICI+DQo8c3BhbiBpZD0iT0xL
X1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTsgZm9u
dC1zaXplOjExcHQ7IHRleHQtYWxpZ246bGVmdDsgY29sb3I6YmxhY2s7IEJPUkRFUi1CT1RUT006
IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDogbWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAw
aW47IFBBRERJTkctTEVGVDogMGluOyBQQURESU5HLVJJR0hUOiAwaW47IEJPUkRFUi1UT1A6ICNi
NWM0ZGYgMXB0IHNvbGlkOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRPUDog
M3B0Ij4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5Gcm9tOiA8L3NwYW4+Q2hyaXN0
ZXIgSG9sbWJlcmcgJmx0OzxhIGhyZWY9Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nv
bi5jb20iPmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4g
c3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkRhdGU6IDwvc3Bhbj5Nb25kYXksIEp1bmUgMTAsIDIw
MTMgMTI6MTYgUE08YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+VG86IDwvc3Bh
bj4mcXVvdDs8YSBocmVmPSJtYWlsdG86Z2VuLWFydEBpZXRmLm9yZyI+Z2VuLWFydEBpZXRmLm9y
ZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpnZW4tYXJ0QGlldGYub3JnIj5nZW4tYXJ0
QGlldGYub3JnPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+Q2M6
IDwvc3Bhbj4mcXVvdDs8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1hdnRjb3JlLTYyMjJiaXMu
YWxsQHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLWF2dGNvcmUtNjIyMmJpcy5hbGxAdG9vbHMu
aWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1hdnRjb3Jl
LTYyMjJiaXMuYWxsQHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLWF2dGNvcmUtNjIyMmJpcy5h
bGxAdG9vbHMuaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpi
b2xkIj5TdWJqZWN0OiA8L3NwYW4+R2VuYXJ0IHJldmlldyBvZiBkcmFmdC1pZXRmLWF2dGNvcmUt
NjIyMmJpcy0wMzxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5SZXNlbnQtRnJv
bTogPC9zcGFuPiZsdDs8YSBocmVmPSJtYWlsdG86ZHJhZnQtYWxpYXMtYm91bmNlc0B0b29scy5p
ZXRmLm9yZyI+ZHJhZnQtYWxpYXMtYm91bmNlc0B0b29scy5pZXRmLm9yZzwvYT4mZ3Q7PGJyPg0K
PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlJlc2VudC1UbzogPC9zcGFuPiZxdW90O0Fs
aSBDLiBCZWdlbiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFiZWdlbkBjaXNjby5jb20iPmFi
ZWdlbkBjaXNjby5jb208L2E+Jmd0OywgQ29saW4gUGVya2lucyAmbHQ7PGEgaHJlZj0ibWFpbHRv
OmNzcEBjc3BlcmtpbnMub3JnIj5jc3BAY3NwZXJraW5zLm9yZzwvYT4mZ3Q7LCBEYW4gV2luZyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOmR3aW5nQGNpc2NvLmNvbSI+ZHdpbmdAY2lzY28uY29tPC9hPiZn
dDssDQogJmx0OzxhIGhyZWY9Im1haWx0bzpla3JAcnRmbS5jb20iPmVrckBydGZtLmNvbTwvYT4m
Z3Q7LCBNYWdudXMgV2VzdGVybHVuZCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1hZ251cy53ZXN0ZXJs
dW5kQGVyaWNzc29uLmNvbSI+bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPC9hPiZndDss
IFJpY2hhcmQgQmFybmVzICZsdDs8YSBocmVmPSJtYWlsdG86cmxiQGlwdi5zeCI+cmxiQGlwdi5z
eDwvYT4mZ3Q7LCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJvbmkuZXZlbkBtYWlsMDEuaHVhd2VpLmNv
bSI+cm9uaS5ldmVuQG1haWwwMS5odWF3ZWkuY29tPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0i
Zm9udC13ZWlnaHQ6Ym9sZCI+UmVzZW50LURhdGU6IDwvc3Bhbj5Nb25kYXksIEp1bmUgMTAsIDIw
MTMgMTI6MTYgUE08YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBp
ZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZU
OiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxk
aXYgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVybjpz
Y2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVtYXMt
bWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWljcm9z
b2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvVFIv
UkVDLWh0bWw0MCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRlbnQ9Ik1pY3Jvc29mdCBX
b3JkIDE0IChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRp
b25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAx
NSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFs
LCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNv
UGxhaW5UZXh0LCBsaS5Nc29QbGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdp
bjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXtt
c28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwi
c2Fucy1zZXJpZiI7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7
bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJn
aW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFn
ZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtl
bmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJl
ZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0
PjwveG1sPjwhW2VuZGlmXS0tPg0KPGRpdiBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9
InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4g
Rm9yIGJhY2tncm91bmQgb24gR2VuLUFSVCwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0ICZsdDs8YSBo
cmVmPSJodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0
ZmFxIj5odHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0
ZmFxPC9hPiZndDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+RG9jdW1lbnQ6Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRyYWZ0LWlldGYtYXZ0Y29yZS02MjIyYmlzLTAzPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlJldmlld2VyOiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBDaHJpc3RlciBIb2xtYmVyZzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij5SZXZpZXcgRGF0ZTombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgMTAgSnVuZSAyMDEzPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPklFVEYgTEMgRW5kIERhdGU6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDExIEp1
bmUgMjAxMzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5JRVRGIFRlbGVjaGF0IERhdGU6
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IE4vQTxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5TdW1tYXJ5OiZuYnNwOyBUaGVyZSBpcyBhIG1pbm9y
IGlzc3VlLCBkZXNjcmliZWQgYmVsb3csIHRoYXQgSSB0aGluayBzaG91bGQgYmUgY2xhcmlmaWVk
IGJlZm9yZSB0aGUgZG9jdW1lbnQgaXMgcHVibGlzaGVkLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij5NYWpvciBJc3N1ZXM6IE5vbmU8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
TWlub3IgSXNzdWVzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5TZWN0aW9uIDQuMSBz
YXlzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsg4oCcVGhlIFJU
Q1AgQ05BTUUgY2FuIGJlIGVpdGhlciBwZXJzaXN0ZW50IGFjcm9zcyBkaWZmZXJlbnQgUlRQIHNl
c3Npb25zPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJz
cDsgZm9yIGFuIFJUUCBlbmRwb2ludCBvciB1bmlxdWUgcGVyIHNlc3Npb24sIG1lYW5pbmcgdGhh
dCBhbiBSVFA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZu
YnNwOyBlbmRwb2ludCBjaG9vc2VzIGEgZGlmZmVyZW50IFJUQ1AgQ05BTUUgZm9yIGVhY2ggUlRQ
IHNlc3Npb24u4oCdPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPuKApmFuZDo8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IOKAnEFuIFJUUCBlbmRwb2ludCB0
aGF0IGlzIGVtaXR0aW5nIG11bHRpcGxlIHJlbGF0ZWQgUlRQIHN0cmVhbXMgdGhhdDxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IHJlcXVpcmUgc3lu
Y2hyb25pemF0aW9uIGF0IHRoZSBvdGhlciBlbmRwb2ludChzKSBNVVNUIHVzZSB0aGUgc2FtZTxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IFJUQ1Ag
Q05BTUUgZm9yIGFsbCBzdHJlYW1zIHRoYXQgYXJlIHRvIGJlIHN5bmNocm9uaXplZC4mbmJzcDsg
VGhpczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7
IHJlcXVpcmVzIGEgc2hvcnQtdGVybSBwZXJzaXN0ZW50IFJUQ1AgQ05BTUUgdGhhdCBpcyBjb21t
b24gYWNyb3NzPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsm
bmJzcDsgc2V2ZXJhbCBSVFAgc3RyZWFtcywgYW5kIHBvdGVudGlhbGx5IGFjcm9zcyBzZXZlcmFs
IHJlbGF0ZWQgUlRQPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDsmbmJzcDsgc2Vzc2lvbnMuJm5ic3A7IEEgY29tbW9uIGV4YW1wbGUgb2Ygc3VjaCB1c2Ugb2Nj
dXJzIHdoZW4gbGlwLXN5bmNpbmcgYXVkaW88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOyZuYnNwOyBhbmQgdmlkZW8gc3RyZWFtcyBpbiBhIG11bHRpbWVkaWEg
c2Vzc2lvbiwgd2hlcmUgYSBzaW5nbGUgcGFydGljaXBhbnQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyBoYXMgdG8gdXNlIHRoZSBzYW1lIFJUQ1Ag
Q05BTUUgZm9yIGl0cyBhdWRpbyBSVFAgc2Vzc2lvbiBhbmQgZm9yIGl0czxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IHZpZGVvIFJUUCBzZXNzaW9u
LiZuYnNwOyBBbm90aGVyIGV4YW1wbGUgbWlnaHQgYmUgdG8gc3luY2hyb25pemUgdGhlPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsgbGF5ZXJzIG9m
IGEgbGF5ZXJlZCBhdWRpbyBjb2RlYywgd2hlcmUgdGhlIHNhbWUgUlRDUCBDTkFNRSBoYXMgdG8g
YmU8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyB1
c2VkIGZvciBlYWNoIGxheWVyLuKAnTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij7igKZl
dGMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRoZSB0ZXh0IHRhbGtzIGFib3V0IHRo
ZSBDTkFNRSBiZWluZyB1bmlxdWUgd2l0aGluIGFuIFJUUCBzZXNzaW9uLCBvciB0byBzcGFuIG92
ZXIgbXVsdGlwbGUgUlRQIHNlc3Npb25zLCBidXQgaXQgc2VlbXMgdG8gb21pdCB0aGF0LCAqPGI+
d2l0aGluPC9iPiogYW4gUlRQIHNlc3Npb24sIHlvdSBjYW4gYWxzbyB1c2UgKjxiPmRpZmZlcmVu
dDwvYj4qIENOQU1FIHZhbHVlcywgaWYgZS5nLiB0aGVyZSBpcyBubw0KIHN5bmNocm9uaXphdGlv
biByZXF1aXJlbWVudCBiZXR3ZWVuIHRoZSBSVFAgc3RyZWFtcy48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRp
dj5EbyB5b3UgdGhpbmsgd2Ugc2hvdWxkIGFkZCB0aGUgZm9sbG93aW5nIHNlbnRlbmNlIGJlbG93
IHRoZSBzZWNvbmQgcGFyYWdyYXBoIHlvdSBxdW90ZSBhYm92ZT88L2Rpdj4NCjxkaXY+PGJyPg0K
PC9kaXY+DQo8ZGl2PklmIHRoZSBtdWx0aXBsZSBSVFAgc3RyZWFtcyBpbiBhbiBSVFAgc2Vzc2lv
biBhcmUgbm90IHJlbGF0ZWQsIHRodXMgZG8gbm90IHJlcXVpcmUgc3luY2hyb25pemF0aW9uLCBh
biBSVFAgZW5kcG9pbnQgY2FuIHVzZSBkaWZmZXJlbnQgUlRDUCBDTkFNRXMgZm9yIHRoZXNlIHN0
cmVhbXMuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9T
RUNUSU9OIj4NCjxibG9ja3F1b3RlIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElPTl9CTE9DS1FV
T1RFIiBzdHlsZT0iQk9SREVSLUxFRlQ6ICNiNWM0ZGYgNSBzb2xpZDsgUEFERElORzowIDAgMCA1
OyBNQVJHSU46MCAwIDAgNTsiPg0KPGRpdiB4bWxuczp2PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQt
Y29tOnZtbCIgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNl
IiB4bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczpt
PSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5z
PSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxkaXYgbGFuZz0iRU4tVVMiIGxp
bms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkVkaXRvcmlhbCBuaXRz
OiBOb25lPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkJlc3QgcmVnYXJkcyw8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0K
PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_C15918F2FCDA0243A7C919DA7C4BE9940D13003Axmbalnx01ciscoc_--

From dromasca@avaya.com  Mon Jun 10 10:00:09 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11FEE21F8EF2; Mon, 10 Jun 2013 10:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.417
X-Spam-Level: 
X-Spam-Status: No, score=-103.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fooV8Ntl3C2k; Mon, 10 Jun 2013 10:00:02 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 2C38121F9750; Mon, 10 Jun 2013 10:00:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAAH/ZlHGmAcF/2dsb2JhbABQgmUhwX6BBxZ0gh8BAQEBAxIoPwwEAgEIDQQEAQEBChQJByERFAkIAgQOBQgah2ADDwGgR5M5DYlGF4xDgiImCwcGglphA5UeAYgKhUyFHIMLgig
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200"; d="scan'208";a="14969589"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Jun 2013 13:00:01 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Jun 2013 12:58:31 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 18:59:59 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/AAACXwtAAACxhQAAAZQ1gAAAuajAAAmW0KAAAUNTw
Date: Mon, 10 Jun 2013 16:59:59 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA19A0A6@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D520@EXC-MBX03.tsn.tno.nl>, <9904FB1B0159DA42B0B887B7FA8119CA199F21@AZ-FFEXMB04.global.avaya.com> <3DFD3155-BBD9-4BE0-8912-81B92C93D3CB@tno.nl>
In-Reply-To: <3DFD3155-BBD9-4BE0-8912-81B92C93D3CB@tno.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 17:00:09 -0000

> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 7:19 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even
> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: Re: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
>=20
>=20
> On 10 jun. 2013, at 17:11, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> wrote:
>=20
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> >> Sent: Monday, June 10, 2013 6:06 PM
> >> To: Romascanu, Dan (Dan)
> >> Cc: avt@ietf.org; General Area Review Team; Roni Even
> >> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> >> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> >> Sent: maandag 10 juni 2013 16:57
> >> To: Brandenburg, R. (Ray) van
> >> Cc: avt@ietf.org; General Area Review Team; Roni Even
> >> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> >> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>
> >>
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> >>> Sent: Monday, June 10, 2013 5:52 PM
> >>> To: Romascanu, Dan (Dan)
> >>> Cc: avt@ietf.org; General Area Review Team; Roni Even
> >>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> >>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>>
> >>> Hi Dan,
> >>>
> >>> See below...
> >>>
> >>> Best regards,
> >>>
> >>> Ray
> >>>
> >>> -----Original Message-----
> >>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> >>> Sent: maandag 10 juni 2013 16:35
> >>> To: Brandenburg, R. (Ray) van
> >>> Cc: avt@ietf.org; General Area Review Team; Roni Even
> >>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> >>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>>
> >>>
> >>> Yes, we seem to get closer and closer, focus on one last issue (and
> >>> much agreement deleted)
> >>>
> >>> Thanks and Regards,
> >>>
> >>> Dan
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> >>>> Sent: Monday, June 10, 2013 5:27 PM
> >>>> To: Romascanu, Dan (Dan)
> >>>> Cc: avt@ietf.org; General Area Review Team; Roni Even
> >>>> (ron.even.tlv@gmail.com);
> >>>> draft-ietf-avtcore-idms.all@tools.ietf.org
> >>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>>>
> >>>> Hi Dan,
> >>>>
> >>>> Please see inline. We seem to be converging:)
> >>>>
> >>>> Ray
> >>>
> >>>>>> 7. In Section 8:
> >>>>>>
> >>>>>>   The timestamp is formatted based on the NTP
> >>>>>>   timestamp format as specified in [RFC5905].  If this field is
> >>>>> empty,
> >>>>>>   then it SHALL be set to 0.  This field MAY be left empty if
> >>>>>> none
> >>>> or
> >>>>>>   only one of the receivers reported on presentation
> >> timestamps.
> >>>>>>
> >>>>>> Why a MAY here? Especially for the case when none of the
> >>>>>> receivers reported, what content can be set there but 0 ?
> >>>>>>
> >>>>>> [Ray: I believe it should be up to the implementation to decide
> >>>>>> how it wants to handle the case of there being only one receiver
> >>>>>> who reported on presentation timestamps].
> >>>>>>
> >>>>> [[DR]] OK, so the cases when none of the receivers reported and
> >>>>> one receiver only reported should be dealt with differently. This
> >>>>> needs to be clarified.
> >>>>>
> >>>>> [Ray] What exactly is the problem with the MAY here? IMO it
> >>>>> doesn't create any interop issues: whatever is the reason for
> >>>>> setting the value to 0, to the client the end result is the same:
> >> ignore it.
> >>>>>
> >>>>
> >>>> [[DR]] In the case when none of the receivers reported we want to
> >>>> avoid leaving some garbage in this field which could be interpreted
> >>>> differently - don't we?
> >>>>
> >>>> [Ray] I think I see where we disagree. The paragraph says: "If this
> >>>> field is empty, then it SHALL be set to 0. This field MAY be left
> >>>> empty if none or only one of the receivers reported on presentation
> >>>> timestamps". The way I read this is as: In the case the field is
> >>>> declared empty (=3D contains NULL information), it SHALL be set to 0=
.
> >>>> There can be different reasons for declaring the field empty/NULL,
> >>>> one of those reasons is if none or only one receiver reported on
> >>>> presentation timestamps. To me, the paragraph doesn't say that this
> >>>> is the only possible reason, but it does specify very clearly that
> >>>> if you decide the field should be empty, you SHALL set it to zero.
> >>>>
> >>>>
> >>>
> >>> [[DR]] But then, why do not you take out 'if none or' - because for
> >>> the option of 'none' there is no alternative but the 'null'
> >>> information, and the MAY does not make sense.
> >>>
> >>> [Ray] The fact that no receiver reported on the packet presentation
> >>> timestamp does not necessarily mean that the MSAS does not want to
> >>> indicate a proposed packet presentation timestamp. The absence of
> >>> such reports just means that the proposed playout moment might not
> >>> be realistic, or be supported by any receiver.
> >>>
> >>
> >> [[DR]] yes, but is the field set to anything but 0 in such cases?
> >>
> >> [Ray] If the MSAS decides to leave the field empty, it is set to 0
> >> according to the SHALL. If the MSAS decides to include a timestamp
> >> anyway, it is set to whatever value the MSAS proposes.
> >>
> >
> > [[DR]] So two different implementations may behave differently in
> similar situations. Is this a problem?
> >
>=20
> No, I don't think it is a problem if two different MSAS implementations
> behave differently in this regard. I see it as server-side
> configuration. Anyway, even if we would replace the MAY with a SHOULD or
> remove the sentence all together, there would still be different
> implementations: for example, let's say we have a sync group of 12
> devices, with 7 of them reporting presentation timestamps. What should
> the MSAS do? Set the field in the IDMS Settings Packet to 0 or not? I
> feel this decision should be up to the implementation as I don't see an
> advantage to us specifying either one way or the other.
>=20
> Ray
>=20

[[DR]] The open issue is not about this case but about the case when no rec=
eiver reported. You say one MSAS implementation may treat this as null info=
rmation setting the field to 0 (which would seem to me like the obvious thi=
ng to do), but other MSAS implementation may include a timestamp anyway (wh=
ich one?). My question 'Is this a problem' was about this case?=20

Dan


From prvs=987383d350=christer.holmberg@ericsson.com  Mon Jun 10 10:39:32 2013
Return-Path: <prvs=987383d350=christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE3521F8BE6 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 10:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.098
X-Spam-Level: 
X-Spam-Status: No, score=-6.098 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYpv4vHXSOr6 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 10:39:19 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 9E15621F96C6 for <gen-art@ietf.org>; Mon, 10 Jun 2013 10:39:18 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-68-51b60f453b4e
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 34.F8.18006.54F06B15; Mon, 10 Jun 2013 19:39:17 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 19:39:16 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-ietf-avtcore-6222bis-03
Thread-Index: Ac5luxdWTPgVtsT2RrKnG3rZqnZqqgAfvh8AAA4ycyA=
Date: Mon, 10 Jun 2013 17:39:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3875E1@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C386F68@ESESSMB209.ericsson.se> <C15918F2FCDA0243A7C919DA7C4BE9940D13003A@xmb-aln-x01.cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE9940D13003A@xmb-aln-x01.cisco.com>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3875E1ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMLMWRmVeSWpSXmKPExsUyM+Jvra4r/7ZAg/lHJS0ebJ/LaHF09kom i6uvPrM4MHtM+b2R1WPJkp9MHl8uf2YLYI7itklKLCkLzkzP07dL4M74+/ACc8GTk4wVJw+u ZGtg3HGEsYuRg0NCwETi9I7oLkZOIFNM4sK99WxdjFwcQgKHGSU6/2xmhHCWMEpcmbiQDaSB TcBCovufNkiDiEC4xNlXG1lBbGaBVIkL988zgdjCAtYSW1YsZYOosZE4cHAH2C4RASuJi+t5 QcIsAqoSZ1bdASvnFfCVWLF6LhPEqgmMEn8nr2cGqecESiz+KQ1Swwh02/dTa5ggVolLfDh4 nRniZgGJJXvOQ9miEi8f/2OFsJUkfmy4xAJRny9xcfoVFohdghInZz5hmcAoOgvJqFlIymYh KZsFdAWzgKbE+l36ECWKElO6H7JD2BoSrXPmsiOLL2BkX8XInpuYmZNebrSJERhnB7f8Vt3B eOecyCFGaQ4WJXFePd7FgUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4QQSXVAOjmWLEFNEZfCZi 8y11sl58DP9c+9Y1gz+ZN/Aa84tc2Ubb39cF91Z338/c3FByROGkGee0P/Fmj1YZKE+z5Lc4 ussmeOr7ZX4n++X2XajcOPFHz8FXyZoLFs9x11a18r0p8U2xfeLL48JCzzNs2Rcv67cIEpw8 VYeN5btOukHxncvzn2ntuSepxFKckWioxVxUnAgA5u4+L4YCAAA=
Cc: "draft-ietf-avtcore-6222bis.all@tools.ietf.org" <draft-ietf-avtcore-6222bis.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-ietf-avtcore-6222bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 17:39:32 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C3875E1ESESSMB209erics_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgQWxpLA0KDQpJIGRpZG7igJl0IGNvcHkgdGhlIHdob2xlIHNlY3Rpb24gNC4xLCBzbyBJIGRv
buKAmXQga25vdyB3aGV0aGVyIGJlbG93IHRoZSBzZWNvbmQgcGFyYWdyYXBoIGlzIHRoZSBiZXN0
IHBsYWNlIChJIGRvbuKAmXQgaGF2ZSB0aGUgZHJhZnQgaW4gZnJvbnQgb2YgbWUgYXQgdGhlIG1v
bWVudCkuIEJ1dCwgdGhlIHRleHQgeW91IHN1Z2dlc3QgYXMgc3VjaCBpcyBnb29kLCBzbyBJIHRy
dXN0IHlvdeKAmWxsIGZpbmQgYSBnb29kIHBsYWNlIGZvciBpdCA6KQ0KDQpSZWdhcmRzLA0KDQpD
aHJpc3Rlcg0KDQpMw6RoZXR0w6Rqw6Q6IEFsaSBDLiBCZWdlbiAoYWJlZ2VuKSBbbWFpbHRvOmFi
ZWdlbkBjaXNjby5jb21dDQpMw6RoZXRldHR5OiAxMC4ga2Vzw6RrdXV0YSAyMDEzIDE5OjI1DQpW
YXN0YWFub3R0YWphOiBDaHJpc3RlciBIb2xtYmVyZzsgZ2VuLWFydEBpZXRmLm9yZw0KS29waW86
IGRyYWZ0LWlldGYtYXZ0Y29yZS02MjIyYmlzLmFsbEB0b29scy5pZXRmLm9yZw0KQWloZTogUmU6
IEdlbmFydCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1hdnRjb3JlLTYyMjJiaXMtMDMNCg0KRnJvbTog
Q2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86
Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4NCkRhdGU6IE1vbmRheSwgSnVuZSAxMCwg
MjAxMyAxMjoxNiBQTQ0KVG86ICJnZW4tYXJ0QGlldGYub3JnPG1haWx0bzpnZW4tYXJ0QGlldGYu
b3JnPiIgPGdlbi1hcnRAaWV0Zi5vcmc8bWFpbHRvOmdlbi1hcnRAaWV0Zi5vcmc+Pg0KQ2M6ICJk
cmFmdC1pZXRmLWF2dGNvcmUtNjIyMmJpcy5hbGxAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0
LWlldGYtYXZ0Y29yZS02MjIyYmlzLmFsbEB0b29scy5pZXRmLm9yZz4iIDxkcmFmdC1pZXRmLWF2
dGNvcmUtNjIyMmJpcy5hbGxAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtYXZ0Y29y
ZS02MjIyYmlzLmFsbEB0b29scy5pZXRmLm9yZz4+DQpTdWJqZWN0OiBHZW5hcnQgcmV2aWV3IG9m
IGRyYWZ0LWlldGYtYXZ0Y29yZS02MjIyYmlzLTAzDQpSZXNlbnQtRnJvbTogPGRyYWZ0LWFsaWFz
LWJvdW5jZXNAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWFsaWFzLWJvdW5jZXNAdG9vbHMu
aWV0Zi5vcmc+Pg0KUmVzZW50LVRvOiAiQWxpIEMuIEJlZ2VuIiA8YWJlZ2VuQGNpc2NvLmNvbTxt
YWlsdG86YWJlZ2VuQGNpc2NvLmNvbT4+LCBDb2xpbiBQZXJraW5zIDxjc3BAY3NwZXJraW5zLm9y
ZzxtYWlsdG86Y3NwQGNzcGVya2lucy5vcmc+PiwgRGFuIFdpbmcgPGR3aW5nQGNpc2NvLmNvbTxt
YWlsdG86ZHdpbmdAY2lzY28uY29tPj4sIDxla3JAcnRmbS5jb208bWFpbHRvOmVrckBydGZtLmNv
bT4+LCBNYWdudXMgV2VzdGVybHVuZCA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPG1h
aWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20+PiwgUmljaGFyZCBCYXJuZXMgPHJs
YkBpcHYuc3g8bWFpbHRvOnJsYkBpcHYuc3g+PiwgPHJvbmkuZXZlbkBtYWlsMDEuaHVhd2VpLmNv
bTxtYWlsdG86cm9uaS5ldmVuQG1haWwwMS5odWF3ZWkuY29tPj4NClJlc2VudC1EYXRlOiBNb25k
YXksIEp1bmUgMTAsIDIwMTMgMTI6MTYgUE0NCg0KDQpJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJU
IHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBGb3IgYmFja2dyb3VuZCBvbiBHZW4tQVJULCBwbGVh
c2Ugc2VlIHRoZSBGQVEgYXQgPGh0dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3Ry
YWMvd2lraS9HZW5BcnRmYXE+DQoNCg0KDQpEb2N1bWVudDogICAgICAgICAgICAgICAgICAgICAg
ICAgZHJhZnQtaWV0Zi1hdnRjb3JlLTYyMjJiaXMtMDMNCg0KDQoNClJldmlld2VyOiAgICAgICAg
ICAgICAgICAgICAgICAgICAgIENocmlzdGVyIEhvbG1iZXJnDQoNCg0KDQpSZXZpZXcgRGF0ZTog
ICAgICAgICAgICAgICAgICAgICAxMCBKdW5lIDIwMTMNCg0KDQoNCklFVEYgTEMgRW5kIERhdGU6
ICAgICAgICAgICAgIDExIEp1bmUgMjAxMw0KDQoNCg0KSUVURiBUZWxlY2hhdCBEYXRlOiAgICAg
ICAgIE4vQQ0KDQoNCg0KU3VtbWFyeTogIFRoZXJlIGlzIGEgbWlub3IgaXNzdWUsIGRlc2NyaWJl
ZCBiZWxvdywgdGhhdCBJIHRoaW5rIHNob3VsZCBiZSBjbGFyaWZpZWQgYmVmb3JlIHRoZSBkb2N1
bWVudCBpcyBwdWJsaXNoZWQuDQoNCg0KDQpNYWpvciBJc3N1ZXM6IE5vbmUNCg0KDQoNCk1pbm9y
IElzc3VlczoNCg0KDQoNClNlY3Rpb24gNC4xIHNheXM6DQoNCg0KDQogICDigJxUaGUgUlRDUCBD
TkFNRSBjYW4gYmUgZWl0aGVyIHBlcnNpc3RlbnQgYWNyb3NzIGRpZmZlcmVudCBSVFAgc2Vzc2lv
bnMNCg0KICAgZm9yIGFuIFJUUCBlbmRwb2ludCBvciB1bmlxdWUgcGVyIHNlc3Npb24sIG1lYW5p
bmcgdGhhdCBhbiBSVFANCg0KICAgZW5kcG9pbnQgY2hvb3NlcyBhIGRpZmZlcmVudCBSVENQIENO
QU1FIGZvciBlYWNoIFJUUCBzZXNzaW9uLuKAnQ0KDQoNCg0K4oCmYW5kOg0KDQoNCg0KICAg4oCc
QW4gUlRQIGVuZHBvaW50IHRoYXQgaXMgZW1pdHRpbmcgbXVsdGlwbGUgcmVsYXRlZCBSVFAgc3Ry
ZWFtcyB0aGF0DQoNCiAgIHJlcXVpcmUgc3luY2hyb25pemF0aW9uIGF0IHRoZSBvdGhlciBlbmRw
b2ludChzKSBNVVNUIHVzZSB0aGUgc2FtZQ0KDQogICBSVENQIENOQU1FIGZvciBhbGwgc3RyZWFt
cyB0aGF0IGFyZSB0byBiZSBzeW5jaHJvbml6ZWQuICBUaGlzDQoNCiAgIHJlcXVpcmVzIGEgc2hv
cnQtdGVybSBwZXJzaXN0ZW50IFJUQ1AgQ05BTUUgdGhhdCBpcyBjb21tb24gYWNyb3NzDQoNCiAg
IHNldmVyYWwgUlRQIHN0cmVhbXMsIGFuZCBwb3RlbnRpYWxseSBhY3Jvc3Mgc2V2ZXJhbCByZWxh
dGVkIFJUUA0KDQogICBzZXNzaW9ucy4gIEEgY29tbW9uIGV4YW1wbGUgb2Ygc3VjaCB1c2Ugb2Nj
dXJzIHdoZW4gbGlwLXN5bmNpbmcgYXVkaW8NCg0KICAgYW5kIHZpZGVvIHN0cmVhbXMgaW4gYSBt
dWx0aW1lZGlhIHNlc3Npb24sIHdoZXJlIGEgc2luZ2xlIHBhcnRpY2lwYW50DQoNCiAgIGhhcyB0
byB1c2UgdGhlIHNhbWUgUlRDUCBDTkFNRSBmb3IgaXRzIGF1ZGlvIFJUUCBzZXNzaW9uIGFuZCBm
b3IgaXRzDQoNCiAgIHZpZGVvIFJUUCBzZXNzaW9uLiAgQW5vdGhlciBleGFtcGxlIG1pZ2h0IGJl
IHRvIHN5bmNocm9uaXplIHRoZQ0KDQogICBsYXllcnMgb2YgYSBsYXllcmVkIGF1ZGlvIGNvZGVj
LCB3aGVyZSB0aGUgc2FtZSBSVENQIENOQU1FIGhhcyB0byBiZQ0KDQogICB1c2VkIGZvciBlYWNo
IGxheWVyLuKAnQ0KDQoNCg0K4oCmZXRjLg0KDQoNCg0KVGhlIHRleHQgdGFsa3MgYWJvdXQgdGhl
IENOQU1FIGJlaW5nIHVuaXF1ZSB3aXRoaW4gYW4gUlRQIHNlc3Npb24sIG9yIHRvIHNwYW4gb3Zl
ciBtdWx0aXBsZSBSVFAgc2Vzc2lvbnMsIGJ1dCBpdCBzZWVtcyB0byBvbWl0IHRoYXQsICp3aXRo
aW4qIGFuIFJUUCBzZXNzaW9uLCB5b3UgY2FuIGFsc28gdXNlICpkaWZmZXJlbnQqIENOQU1FIHZh
bHVlcywgaWYgZS5nLiB0aGVyZSBpcyBubyBzeW5jaHJvbml6YXRpb24gcmVxdWlyZW1lbnQgYmV0
d2VlbiB0aGUgUlRQIHN0cmVhbXMuDQoNCkRvIHlvdSB0aGluayB3ZSBzaG91bGQgYWRkIHRoZSBm
b2xsb3dpbmcgc2VudGVuY2UgYmVsb3cgdGhlIHNlY29uZCBwYXJhZ3JhcGggeW91IHF1b3RlIGFi
b3ZlPw0KDQpJZiB0aGUgbXVsdGlwbGUgUlRQIHN0cmVhbXMgaW4gYW4gUlRQIHNlc3Npb24gYXJl
IG5vdCByZWxhdGVkLCB0aHVzIGRvIG5vdCByZXF1aXJlIHN5bmNocm9uaXphdGlvbiwgYW4gUlRQ
IGVuZHBvaW50IGNhbiB1c2UgZGlmZmVyZW50IFJUQ1AgQ05BTUVzIGZvciB0aGVzZSBzdHJlYW1z
Lg0KDQoNCg0KDQoNCg0KRWRpdG9yaWFsIG5pdHM6IE5vbmUNCg0KDQoNCkJlc3QgcmVnYXJkcywN
Cg0KDQoNCkNocmlzdGVyDQoNCg0KDQo=

--_000_7594FB04B1934943A5C02806D1A2204B1C3875E1ESESSMB209erics_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg
MiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNv
Tm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl
cmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVk
LCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1BsYWluVGV4
dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgltc28tc3R5bGUtbGluazoiVmFpbiB0ZWtzdGluw6QgQ2hhciI7DQoJbWFyZ2luOjBj
bTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0
ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1s
aW5rOiJTZWxpdGV0ZWtzdGkgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4w
MDAxcHQ7DQoJZm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNl
cmlmIjt9DQpzcGFuLlZhaW50ZWtzdGluQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiVmFpbiB0ZWtz
dGluw6QgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJW
YWluIHRla3N0aW7DpCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5TaGtwb3N0aXR5
eWxpMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnAuUGxhaW5UZXh0LCBsaS5QbGFp
blRleHQsIGRpdi5QbGFpblRleHQNCgl7bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRleHQiOw0KCW1z
by1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBs
YWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5r
OiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNw
YW4uU2hrcG9zdGl0eXlsaTIyDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFu
LlNlbGl0ZXRla3N0aUNoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlNlbGl0ZXRla3N0aSBDaGFyIjsN
Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6U2VsaXRldGVrc3RpOw0K
CWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQouTXNvQ2hwRGVmYXVsdA0KCXtt
c28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdv
cmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBw
dCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7
fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg
djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw
IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm
XS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRkkiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUi
Pg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj5IaSBBbGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SSBkaWRu4oCZdCBjb3B5IHRoZSB3aG9sZSBzZWN0aW9u
IDQuMSwgc28gSSBkb27igJl0IGtub3cgd2hldGhlciBiZWxvdyB0aGUgc2Vjb25kIHBhcmFncmFw
aCBpcyB0aGUgYmVzdCBwbGFjZSAoSSBkb27igJl0IGhhdmUgdGhlIGRyYWZ0IGluIGZyb250IG9m
IG1lIGF0IHRoZSBtb21lbnQpLiBCdXQsIHRoZSB0ZXh0IHlvdSBzdWdnZXN0IGFzIHN1Y2gNCiBp
cyBnb29kLCBzbyBJIHRydXN0IHlvdeKAmWxsIGZpbmQgYSBnb29kIHBsYWNlIGZvciBpdCA6KTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20g
MGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5Mw6RoZXR0w6Rqw6Q6PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IEFs
aSBDLiBCZWdlbiAoYWJlZ2VuKSBbbWFpbHRvOmFiZWdlbkBjaXNjby5jb21dDQo8YnI+DQo8Yj5M
w6RoZXRldHR5OjwvYj4gMTAuIGtlc8Oka3V1dGEgMjAxMyAxOToyNTxicj4NCjxiPlZhc3RhYW5v
dHRhamE6PC9iPiBDaHJpc3RlciBIb2xtYmVyZzsgZ2VuLWFydEBpZXRmLm9yZzxicj4NCjxiPktv
cGlvOjwvYj4gZHJhZnQtaWV0Zi1hdnRjb3JlLTYyMjJiaXMuYWxsQHRvb2xzLmlldGYub3JnPGJy
Pg0KPGI+QWloZTo8L2I+IFJlOiBHZW5hcnQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0Y29yZS02
MjIyYmlzLTAzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAw
Y20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5G
cm9tOiA8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+Q2hyaXN0ZXIgSG9sbWJl
cmcgJmx0OzxhIGhyZWY9Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20iPmNo
cmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPk1v
bmRheSwgSnVuZSAxMCwgMjAxMyAxMjoxNiBQTTxicj4NCjxiPlRvOiA8L2I+JnF1b3Q7PGEgaHJl
Zj0ibWFpbHRvOmdlbi1hcnRAaWV0Zi5vcmciPmdlbi1hcnRAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZs
dDs8YSBocmVmPSJtYWlsdG86Z2VuLWFydEBpZXRmLm9yZyI+Z2VuLWFydEBpZXRmLm9yZzwvYT4m
Z3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVvdDs8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1hdnRj
b3JlLTYyMjJiaXMuYWxsQHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLWF2dGNvcmUtNjIyMmJp
cy5hbGxAdG9vbHMuaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86ZHJhZnQt
aWV0Zi1hdnRjb3JlLTYyMjJiaXMuYWxsQHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLWF2dGNv
cmUtNjIyMmJpcy5hbGxAdG9vbHMuaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6IDwv
Yj5HZW5hcnQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0Y29yZS02MjIyYmlzLTAzPGJyPg0KPGI+
UmVzZW50LUZyb206IDwvYj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWFsaWFzLWJvdW5jZXNA
dG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWFsaWFzLWJvdW5jZXNAdG9vbHMuaWV0Zi5vcmc8L2E+Jmd0
Ozxicj4NCjxiPlJlc2VudC1UbzogPC9iPiZxdW90O0FsaSBDLiBCZWdlbiZxdW90OyAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmFiZWdlbkBjaXNjby5jb20iPmFiZWdlbkBjaXNjby5jb208L2E+Jmd0Oywg
Q29saW4gUGVya2lucyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNzcEBjc3BlcmtpbnMub3JnIj5jc3BA
Y3NwZXJraW5zLm9yZzwvYT4mZ3Q7LCBEYW4gV2luZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmR3aW5n
QGNpc2NvLmNvbSI+ZHdpbmdAY2lzY28uY29tPC9hPiZndDssICZsdDs8YSBocmVmPSJtYWlsdG86
ZWtyQHJ0Zm0uY29tIj5la3JAcnRmbS5jb208L2E+Jmd0OywNCiBNYWdudXMgV2VzdGVybHVuZCAm
bHQ7PGEgaHJlZj0ibWFpbHRvOm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbSI+bWFnbnVz
Lndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPC9hPiZndDssIFJpY2hhcmQgQmFybmVzICZsdDs8YSBo
cmVmPSJtYWlsdG86cmxiQGlwdi5zeCI+cmxiQGlwdi5zeDwvYT4mZ3Q7LCAmbHQ7PGEgaHJlZj0i
bWFpbHRvOnJvbmkuZXZlbkBtYWlsMDEuaHVhd2VpLmNvbSI+cm9uaS5ldmVuQG1haWwwMS5odWF3
ZWkuY29tPC9hPiZndDs8YnI+DQo8Yj5SZXNlbnQtRGF0ZTogPC9iPk1vbmRheSwgSnVuZSAxMCwg
MjAxMyAxMjoxNiBQTTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5
OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQjVD
NERGIDQuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6My43NXB0O21h
cmdpbi1yaWdodDowY20iIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJjb2xvcjpibGFjayI+SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBm
b3IgdGhpcyBkcmFmdC4gRm9yIGJhY2tncm91bmQgb24gR2VuLUFSVCwgcGxlYXNlIHNlZSB0aGUg
RkFRIGF0ICZsdDs8YSBocmVmPSJodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90
cmFjL3dpa2kvR2VuQXJ0ZmFxIj5odHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90
cmFjL3dpa2kvR2VuQXJ0ZmFxPC9hPiZndDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4m
bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5Eb2N1bWVudDombmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgZHJhZnQtaWV0Zi1hdnRjb3JlLTYyMjJiaXMtMDM8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5S
ZXZpZXdlcjombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgQ2hyaXN0
ZXIgSG9sbWJlcmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImNvbG9yOmJsYWNrIj5SZXZpZXcgRGF0ZTombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgMTAgSnVuZSAyMDEzPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFj
ayI+SUVURiBMQyBFbmQgRGF0ZTombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgMTEgSnVuZSAyMDEzPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+
SUVURiBUZWxlY2hhdCBEYXRlOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBOL0E8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5TdW1tYXJ5OiZuYnNwOyBUaGVyZSBpcyBhIG1pbm9yIGlz
c3VlLCBkZXNjcmliZWQgYmVsb3csIHRoYXQgSSB0aGluayBzaG91bGQgYmUgY2xhcmlmaWVkIGJl
Zm9yZSB0aGUgZG9jdW1lbnQgaXMgcHVibGlzaGVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6Ymxh
Y2siPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPk1ham9yIElzc3VlczogTm9u
ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29s
b3I6YmxhY2siPk1pbm9yIElzc3Vlczo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJz
cDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5TZWN0aW9uIDQuMSBzYXlzOjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2si
PiZuYnNwOyZuYnNwOyDigJxUaGUgUlRDUCBDTkFNRSBjYW4gYmUgZWl0aGVyIHBlcnNpc3RlbnQg
YWNyb3NzIGRpZmZlcmVudCBSVFAgc2Vzc2lvbnM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNr
Ij4mbmJzcDsmbmJzcDsgZm9yIGFuIFJUUCBlbmRwb2ludCBvciB1bmlxdWUgcGVyIHNlc3Npb24s
IG1lYW5pbmcgdGhhdCBhbiBSVFA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsm
bmJzcDsgZW5kcG9pbnQgY2hvb3NlcyBhIGRpZmZlcmVudCBSVENQIENOQU1FIGZvciBlYWNoIFJU
UCBzZXNzaW9uLuKAnTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iY29sb3I6YmxhY2siPuKApmFuZDo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNr
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsg4oCcQW4g
UlRQIGVuZHBvaW50IHRoYXQgaXMgZW1pdHRpbmcgbXVsdGlwbGUgcmVsYXRlZCBSVFAgc3RyZWFt
cyB0aGF0PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IHJlcXVpcmUg
c3luY2hyb25pemF0aW9uIGF0IHRoZSBvdGhlciBlbmRwb2ludChzKSBNVVNUIHVzZSB0aGUgc2Ft
ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyBSVENQIENOQU1FIGZv
ciBhbGwgc3RyZWFtcyB0aGF0IGFyZSB0byBiZSBzeW5jaHJvbml6ZWQuJm5ic3A7IFRoaXM8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgcmVxdWlyZXMgYSBzaG9ydC10
ZXJtIHBlcnNpc3RlbnQgUlRDUCBDTkFNRSB0aGF0IGlzIGNvbW1vbiBhY3Jvc3M8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgc2V2ZXJhbCBSVFAgc3RyZWFtcywgYW5k
IHBvdGVudGlhbGx5IGFjcm9zcyBzZXZlcmFsIHJlbGF0ZWQgUlRQPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJj
b2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IHNlc3Npb25zLiZuYnNwOyBBIGNvbW1vbiBleGFtcGxl
IG9mIHN1Y2ggdXNlIG9jY3VycyB3aGVuIGxpcC1zeW5jaW5nIGF1ZGlvPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IGFuZCB2aWRlbyBzdHJlYW1zIGluIGEgbXVsdGlt
ZWRpYSBzZXNzaW9uLCB3aGVyZSBhIHNpbmdsZSBwYXJ0aWNpcGFudDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyBoYXMgdG8gdXNlIHRoZSBzYW1lIFJUQ1AgQ05BTUUg
Zm9yIGl0cyBhdWRpbyBSVFAgc2Vzc2lvbiBhbmQgZm9yIGl0czxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29s
b3I6YmxhY2siPiZuYnNwOyZuYnNwOyB2aWRlbyBSVFAgc2Vzc2lvbi4mbmJzcDsgQW5vdGhlciBl
eGFtcGxlIG1pZ2h0IGJlIHRvIHN5bmNocm9uaXplIHRoZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6
YmxhY2siPiZuYnNwOyZuYnNwOyBsYXllcnMgb2YgYSBsYXllcmVkIGF1ZGlvIGNvZGVjLCB3aGVy
ZSB0aGUgc2FtZSBSVENQIENOQU1FIGhhcyB0byBiZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6Ymxh
Y2siPiZuYnNwOyZuYnNwOyB1c2VkIGZvciBlYWNoIGxheWVyLuKAnTxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Y29sb3I6YmxhY2siPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPuKApmV0Yy48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OmJsYWNrIj5UaGUgdGV4dCB0YWxrcyBhYm91dCB0aGUgQ05BTUUgYmVpbmcgdW5pcXVlIHdpdGhp
biBhbiBSVFAgc2Vzc2lvbiwgb3IgdG8gc3BhbiBvdmVyIG11bHRpcGxlIFJUUCBzZXNzaW9ucywg
YnV0IGl0IHNlZW1zIHRvIG9taXQgdGhhdCwgKjxiPndpdGhpbjwvYj4qIGFuIFJUUCBzZXNzaW9u
LCB5b3UgY2FuIGFsc28gdXNlICo8Yj5kaWZmZXJlbnQ8L2I+Kg0KIENOQU1FIHZhbHVlcywgaWYg
ZS5nLiB0aGVyZSBpcyBubyBzeW5jaHJvbml6YXRpb24gcmVxdWlyZW1lbnQgYmV0d2VlbiB0aGUg
UlRQIHN0cmVhbXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxv
Y2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6Ymxh
Y2siPkRvIHlvdSB0aGluayB3ZSBzaG91bGQgYWRkIHRoZSBmb2xsb3dpbmcgc2VudGVuY2UgYmVs
b3cgdGhlIHNlY29uZCBwYXJhZ3JhcGggeW91IHF1b3RlIGFib3ZlPzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xv
cjpibGFjayI+SWYgdGhlIG11bHRpcGxlIFJUUCBzdHJlYW1zIGluIGFuIFJUUCBzZXNzaW9uIGFy
ZSBub3QgcmVsYXRlZCwgdGh1cyBkbyBub3QgcmVxdWlyZSBzeW5jaHJvbml6YXRpb24sIGFuIFJU
UCBlbmRwb2ludCBjYW4gdXNlIGRpZmZlcmVudCBSVENQIENOQU1FcyBmb3IgdGhlc2Ugc3RyZWFt
cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTpDb25zb2xhcztj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2tx
dW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0I1QzRERiA0LjVwdDtw
YWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4tcmlnaHQ6
MGNtIiBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSI+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29s
b3I6YmxhY2siPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPkVkaXRvcmlhbCBuaXRzOiBOb25lPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+QmVz
dCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6YmxhY2siPkNocmlzdGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5i
c3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_7594FB04B1934943A5C02806D1A2204B1C3875E1ESESSMB209erics_--

From prvs=8873d10d0e=suresh.krishnan@ericsson.com  Mon Jun 10 12:13:13 2013
Return-Path: <prvs=8873d10d0e=suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8ABD21F95D7 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 12:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rmgrrhvQnsvp for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 12:13:08 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id DABD921F9A4B for <gen-art@ietf.org>; Mon, 10 Jun 2013 12:13:03 -0700 (PDT)
X-AuditID: c618062d-b7f936d000004481-cf-51b6253e7eb5
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id FD.FA.17537.E3526B15; Mon, 10 Jun 2013 21:13:03 +0200 (CEST)
Received: from eusaamw0711.eamcs.ericsson.se (147.117.20.178) by EUSAAHC001.ericsson.se (147.117.188.75) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 10 Jun 2013 15:13:02 -0400
Received: from [164.48.125.57] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 10 Jun 2013 15:13:01 -0400
Message-ID: <51B6249D.8010501@ericsson.com>
Date: Mon, 10 Jun 2013 15:10:21 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: <draft-ietf-sipcore-sip-websocket.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgluLIzCtJLcpLzFFi42KZXLrHW9dedVugwYYWDosZ9/4zWlx99ZnF gcljyZKfTB5fLn9mC2CK4rZJSiwpC85Mz9O3S+DOeDevnbGglbui9et39gbGDxxdjJwcEgIm EhOf72ODsMUkLtxbD2RzcQgJHGWUOLavFcrZwygxZ9ZHVghnK6PEr31fmEBaeAW0JZa8ngJm swioSixcOJ8VxGYDGrth52ewuKhAmMSHZUug6gUlTs58wgJiiwhkSWz4PB1oAweHsIC3RNf+ OogrJCW2vGhnB7GZBfQkplxtYYSw5SW2v53DDGILCWhKbF3znXUCo8AsJFNnIWmZhaRlASPz KkaO0uLUstx0I4NNjMAAPCbBpruDcc9Ly0OM0hwsSuK8aryLA4UE0hNLUrNTUwtSi+KLSnNS iw8xMnFwggguqQZGjc+u7qvFQ4O/bXN2MZgWd8Xg/562yYb7ZqhqBr1r+b351tWVFhzeIltC byq7v5xpOkNrgk8fR9WRFzxv7RglpxpzFxRl/Jn5dbfOXLUbEhVLAxSbHi+aIvzB4XrbEb8X U15s/RF23iXkrcijdQLNXbeirYMfsbXc2NHOz9djmBctIpwpknlRiaU4I9FQi7moOBEADxKX 3BMCAAA=
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-sipcore-sip-websocket-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 19:13:13 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-sipcore-sip-websocket-08.txt
Reviewer: Suresh Krishnan
Review Date: 2013/06/10
IESG Telechat date: 2013/06/13

Summary: This draft is almost ready for publication as a Proposed
Standard, but has some minor issues that need to be fixed as identified
in my last call review dated 2013/04/16. One of the issues I raised was
clarified as common practice in the RAI wgs and I have removed it from
the list. The authors had agreed to fix the following issues but I have
not seen an updated draft yet.

Minor
=====

* Section 4.1

There is no error handling specified. i.e. What happens if the server
does not send a 101 reply with sip in the Sec-WebSocket-Protocol header?

* Section 5.2.2

RFC4168 does not update transport-param. Is this a copy and paste error?

* Section 5.2.4

Maybe it is just me, but the way I read it, this section leaves the
client without any mandatory to implement transport protocol for SIP
since it relaxes the need to implement UDP and TCP, as well as allowing
the implementation of the websocket transport using a MAY.

Thanks
Suresh



From prvs=787369ff58=suresh.krishnan@ericsson.com  Mon Jun 10 12:18:33 2013
Return-Path: <prvs=787369ff58=suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C23821F8607 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 12:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zbgmhGII3pm6 for <gen-art@ietfa.amsl.com>; Mon, 10 Jun 2013 12:18:23 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0F421F9A6D for <gen-art@ietf.org>; Mon, 10 Jun 2013 12:18:23 -0700 (PDT)
X-AuditID: c6180641-b7f0e6d0000015f1-6d-51b6267e1f4c
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 68.96.05617.E7626B15; Mon, 10 Jun 2013 21:18:23 +0200 (CEST)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC004.ericsson.se (147.117.188.84) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 10 Jun 2013 15:18:22 -0400
Received: from [164.48.125.57] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 10 Jun 2013 15:18:21 -0400
Message-ID: <51B625D8.6020402@ericsson.com>
Date: Mon, 10 Jun 2013 15:15:36 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: <draft-ietf-geopriv-held-measurements.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgluLIzCtJLcpLzFFi42KZXLonRLdebVugwdoWTos7W6+wW1x99ZnF gcljyZKfTB5fLn9mC2CK4rZJSiwpC85Mz9O3S+DOWL7SqeAbV8W5pXNYGhhfcnQxcnJICJhI LLv1mx3CFpO4cG89WxcjF4eQwFFGickLJ7FAOHsYJS5dnMUO4WxllOg5cJ4NpIVXQFvi4bFH jCA2i4CqxKZfd5hAbDagsRt2fgazRQXCJD4sW8IEUS8ocXLmExYQW0QgT+L0rgNgcWEBf4m/ nd2sEGdISmx50Q52ErOAnsSUqy2MELa8xPa3c5hBbCEBTYmta76zTmAUmIVk7CwkLbOQtCxg ZF7FyFFanFqWm25kuIkRGIDHJNgcdzAu+GR5iFGag0VJnFeHd3GgkEB6YklqdmpqQWpRfFFp TmrxIUYmDk4QwSXVwLhyedXGspUvzzy8tHDmrmQLUy7PjrjVDHdV3t9bHBahvex0wZ7ItyxG 7NWXXrLva5P4MGWR0VrVy9+erViaspRVfcb7mF7Bf7lld/5o1mWmb2U0NrmjKhtczeCiLnFT OLFEkvH+w5Mze1uOXZHWWxMtppq9kDchUnr7oeB1aR19MixOGeKLVZVYijMSDbWYi4oTAago Sq0TAgAA
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-geopriv-held-measurements-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 19:18:33 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-geopriv-held-measurements-07.txt
Reviewer: Suresh Krishnan
Review Date: 2013/06/10
IESG Telechat date: 2013/06/13


Summary: This draft is almost ready for publication as a Proposed
Standard, but I had a few minor comments as identified
in my last call review dated 2013/05/08. The authors had agreed to fix
the following issues but I have not seen an updated draft yet.

Minor
=====

* Section 5.2

- The Interface-Id option is the DHCPv6 equivalent of the circuit
identifier defined in RFC3046. Please add a reference to Section 22.18
of RFC3315 that describes this option.

- Is there any specific reason that the giaddr is being specified using
the IPv4-mapped IPv6 address format? From my reading giaddr is of type
bt:ipAddressType and it allows specification of both IPv4 and IPv6
addresses natively.

* Section 8.7 Page 53

I think there may be an off-by-one error here.

 <xs:maxInclusive value="268435456"/>

Shouldn't this be

 <xs:maxInclusive value="268435455"/>

so that the largest value will fit in 28 bits?

Thanks
Suresh



From ibc@aliax.net  Tue Jun 11 00:48:05 2013
Return-Path: <ibc@aliax.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7779821F9A70 for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 00:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q3xvUAICrzZU for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 00:48:01 -0700 (PDT)
Received: from mail-qe0-f45.google.com (mail-qe0-f45.google.com [209.85.128.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE7F21F9A75 for <gen-art@ietf.org>; Tue, 11 Jun 2013 00:47:58 -0700 (PDT)
Received: by mail-qe0-f45.google.com with SMTP id w7so1721631qeb.18 for <gen-art@ietf.org>; Tue, 11 Jun 2013 00:47:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=nC9oSqNrMzu8zKjyzpL5AC7dqDNTF+36khJtA4lS7Xo=; b=Ld/J4a/B7hog/cUGzPdwbeLp4DXan59CFOT0X2Kg/b2YPNUScTHYKHYjQfbKfgs52F Gpqk4gbdqxzxX/nriLm+XnYbSZH9ChYDcrW9md4mCTGH3ptLOBuDjpPUAPcAwnO4Z+Ck b17Kg+F5VHEj659AYXRaFvy/2nZLFc0WGvIQKWqb1JXbkn9c32wGvLZMFKKKuvWJGV5Y y2QOhlBJR4jm1Fkse8PoDt6C9C/N0p6d+5pdsGCmv/RAgg7o4FBqTJ/6RgcLDm6YYtK9 EXFpiR48ptXfn1diAbncPRPwe6inpOPWhD6XXg8JUgmU70qCcXJTdo4WOOBgsUFut78B pYXg==
X-Received: by 10.49.49.167 with SMTP id v7mr15143782qen.10.1370936877937; Tue, 11 Jun 2013 00:47:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Tue, 11 Jun 2013 00:47:37 -0700 (PDT)
In-Reply-To: <51B6249D.8010501@ericsson.com>
References: <51B6249D.8010501@ericsson.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Tue, 11 Jun 2013 09:47:37 +0200
Message-ID: <CALiegfnaTYGnetA6MNn9aArm2E0szvXjdWsosxnJy9C5ScUfbg@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQn/AroIVWGAsACcrkVIedkuQQtKIAb9EJSvsLTGRansdtsZBuPbuG2X7SQ3dk+eFBPaLQjl
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-sipcore-sip-websocket-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 07:48:05 -0000

Hi Suresh,

Sorry for the delay. This week I will publish a new version 09 of the
draft addressing all the pending issues.

Thanks a lot.


2013/6/10 Suresh Krishnan <suresh.krishnan@ericsson.com>:
> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document:  draft-ietf-sipcore-sip-websocket-08.txt
> Reviewer: Suresh Krishnan
> Review Date: 2013/06/10
> IESG Telechat date: 2013/06/13
>
> Summary: This draft is almost ready for publication as a Proposed
> Standard, but has some minor issues that need to be fixed as identified
> in my last call review dated 2013/04/16. One of the issues I raised was
> clarified as common practice in the RAI wgs and I have removed it from
> the list. The authors had agreed to fix the following issues but I have
> not seen an updated draft yet.
>
> Minor
> =3D=3D=3D=3D=3D
>
> * Section 4.1
>
> There is no error handling specified. i.e. What happens if the server
> does not send a 101 reply with sip in the Sec-WebSocket-Protocol header?
>
> * Section 5.2.2
>
> RFC4168 does not update transport-param. Is this a copy and paste error?
>
> * Section 5.2.4
>
> Maybe it is just me, but the way I read it, this section leaves the
> client without any mandatory to implement transport protocol for SIP
> since it relaxes the need to implement UDP and TCP, as well as allowing
> the implementation of the websocket transport using a MAY.
>
> Thanks
> Suresh
>
>



--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ray.vanbrandenburg@tno.nl  Tue Jun 11 03:30:13 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA9EE21F9425; Tue, 11 Jun 2013 03:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhKpNXonZnqL; Tue, 11 Jun 2013 03:30:08 -0700 (PDT)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id AF07821F9433; Tue, 11 Jun 2013 03:30:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,844,1363129200";  d="scan'208";a="9709115"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.222]) by mailhost1a.tno.nl with ESMTP; 11 Jun 2013 12:29:56 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.85]) by EXC-CASHUB03.tsn.tno.nl ([134.221.225.222]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 12:29:56 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: Ac5k5mDClosY2XEXSFmBhpnaPpC1lwAw3NGAAAWr/5AAA+nLUAAASPBwAAJBThAAAsYU4AAAcx/AAACXwtAAACxhQAAAZQ1gAAAuajAAAmW0KAAAUNTwACTzZ6A=
Date: Tue, 11 Jun 2013 10:29:55 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581F34EEA4@EXC-MBX03.tsn.tno.nl>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D520@EXC-MBX03.tsn.tno.nl>, <9904FB1B0159DA42B0B887B7FA8119CA199F21@AZ-FFEXMB04.global.avaya.com> <3DFD3155-BBD9-4BE0-8912-81B92C93D3CB@tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA19A0A6@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA19A0A6@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.191]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 10:30:14 -0000

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] =

Sent: maandag 10 juni 2013 19:00
To: Brandenburg, R. (Ray) van
Cc: avt@ietf.org; General Area Review Team; Roni Even (ron.even.tlv@gmail.c=
om); draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09





> -----Original Message-----
> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> Sent: Monday, June 10, 2013 7:19 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: Re: Gen-ART review of draft-ietf-avtcore-idms-09
> =

> =

> =

> On 10 jun. 2013, at 17:11, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> wrote:
> =

> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> >> Sent: Monday, June 10, 2013 6:06 PM
> >> To: Romascanu, Dan (Dan)
> >> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> >> (ron.even.tlv@gmail.com); =

> >> draft-ietf-avtcore-idms.all@tools.ietf.org
> >> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> >> Sent: maandag 10 juni 2013 16:57
> >> To: Brandenburg, R. (Ray) van
> >> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> >> (ron.even.tlv@gmail.com); =

> >> draft-ietf-avtcore-idms.all@tools.ietf.org
> >> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>
> >>
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
> >>> Sent: Monday, June 10, 2013 5:52 PM
> >>> To: Romascanu, Dan (Dan)
> >>> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> >>> (ron.even.tlv@gmail.com); =

> >>> draft-ietf-avtcore-idms.all@tools.ietf.org
> >>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>>
> >>> Hi Dan,
> >>>
> >>> See below...
> >>>
> >>> Best regards,
> >>>
> >>> Ray
> >>>
> >>> -----Original Message-----
> >>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> >>> Sent: maandag 10 juni 2013 16:35
> >>> To: Brandenburg, R. (Ray) van
> >>> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> >>> (ron.even.tlv@gmail.com); =

> >>> draft-ietf-avtcore-idms.all@tools.ietf.org
> >>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>>
> >>>
> >>> Yes, we seem to get closer and closer, focus on one last issue =

> >>> (and much agreement deleted)
> >>>
> >>> Thanks and Regards,
> >>>
> >>> Dan
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Brandenburg, R. (Ray) van =

> >>>> [mailto:ray.vanbrandenburg@tno.nl]
> >>>> Sent: Monday, June 10, 2013 5:27 PM
> >>>> To: Romascanu, Dan (Dan)
> >>>> Cc: avt@ietf.org; General Area Review Team; Roni Even =

> >>>> (ron.even.tlv@gmail.com); =

> >>>> draft-ietf-avtcore-idms.all@tools.ietf.org
> >>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
> >>>>
> >>>> Hi Dan,
> >>>>
> >>>> Please see inline. We seem to be converging:)
> >>>>
> >>>> Ray
> >>>
> >>>>>> 7. In Section 8:
> >>>>>>
> >>>>>>   The timestamp is formatted based on the NTP
> >>>>>>   timestamp format as specified in [RFC5905].  If this field is
> >>>>> empty,
> >>>>>>   then it SHALL be set to 0.  This field MAY be left empty if =

> >>>>>> none
> >>>> or
> >>>>>>   only one of the receivers reported on presentation
> >> timestamps.
> >>>>>>
> >>>>>> Why a MAY here? Especially for the case when none of the =

> >>>>>> receivers reported, what content can be set there but 0 ?
> >>>>>>
> >>>>>> [Ray: I believe it should be up to the implementation to decide =

> >>>>>> how it wants to handle the case of there being only one =

> >>>>>> receiver who reported on presentation timestamps].
> >>>>>>
> >>>>> [[DR]] OK, so the cases when none of the receivers reported and =

> >>>>> one receiver only reported should be dealt with differently. =

> >>>>> This needs to be clarified.
> >>>>>
> >>>>> [Ray] What exactly is the problem with the MAY here? IMO it =

> >>>>> doesn't create any interop issues: whatever is the reason for =

> >>>>> setting the value to 0, to the client the end result is the same:
> >> ignore it.
> >>>>>
> >>>>
> >>>> [[DR]] In the case when none of the receivers reported we want to =

> >>>> avoid leaving some garbage in this field which could be =

> >>>> interpreted differently - don't we?
> >>>>
> >>>> [Ray] I think I see where we disagree. The paragraph says: "If =

> >>>> this field is empty, then it SHALL be set to 0. This field MAY be =

> >>>> left empty if none or only one of the receivers reported on =

> >>>> presentation timestamps". The way I read this is as: In the case =

> >>>> the field is declared empty (=3D contains NULL information), it SHAL=
L be set to 0.
> >>>> There can be different reasons for declaring the field =

> >>>> empty/NULL, one of those reasons is if none or only one receiver =

> >>>> reported on presentation timestamps. To me, the paragraph doesn't =

> >>>> say that this is the only possible reason, but it does specify =

> >>>> very clearly that if you decide the field should be empty, you SHALL=
 set it to zero.
> >>>>
> >>>>
> >>>
> >>> [[DR]] But then, why do not you take out 'if none or' - because =

> >>> for the option of 'none' there is no alternative but the 'null'
> >>> information, and the MAY does not make sense.
> >>>
> >>> [Ray] The fact that no receiver reported on the packet =

> >>> presentation timestamp does not necessarily mean that the MSAS =

> >>> does not want to indicate a proposed packet presentation =

> >>> timestamp. The absence of such reports just means that the =

> >>> proposed playout moment might not be realistic, or be supported by an=
y receiver.
> >>>
> >>
> >> [[DR]] yes, but is the field set to anything but 0 in such cases?
> >>
> >> [Ray] If the MSAS decides to leave the field empty, it is set to 0 =

> >> according to the SHALL. If the MSAS decides to include a timestamp =

> >> anyway, it is set to whatever value the MSAS proposes.
> >>
> >
> > [[DR]] So two different implementations may behave differently in
> similar situations. Is this a problem?
> >
> =

> No, I don't think it is a problem if two different MSAS =

> implementations behave differently in this regard. I see it as =

> server-side configuration. Anyway, even if we would replace the MAY =

> with a SHOULD or remove the sentence all together, there would still =

> be different
> implementations: for example, let's say we have a sync group of 12 =

> devices, with 7 of them reporting presentation timestamps. What should =

> the MSAS do? Set the field in the IDMS Settings Packet to 0 or not? I =

> feel this decision should be up to the implementation as I don't see =

> an advantage to us specifying either one way or the other.
> =

> Ray
> =


[[DR]] The open issue is not about this case but about the case when no rec=
eiver reported. You say one MSAS implementation may treat this as null info=
rmation setting the field to 0 (which would seem to me like the obvious thi=
ng to do), but other MSAS implementation may include a timestamp anyway (wh=
ich one?). My question 'Is this a problem' was about this case? =


[Ray] I don't see a difference between the two cases: in both cases the MSA=
S can decide to send 'some' timestamp.  I'm not saying this is recommended,=
 but I also don't see any interop issues. In any synchronization group ther=
e will be a maximum of 1 MSAS, so all receivers will receive the same prese=
ntation timestamp. What they do with that timestamp is up to the SCs themse=
lves. =


Ray

This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From jari.arkko@piuha.net  Tue Jun 11 14:24:35 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D988321F94DF for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 14:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level: 
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, J_CHICKENPOX_64=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5wnoZY8ULycS for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 14:24:31 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A37B021F88D8 for <gen-art@ietf.org>; Tue, 11 Jun 2013 14:24:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 231C52CC48; Wed, 12 Jun 2013 00:24:28 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jiSCZif8L7El; Wed, 12 Jun 2013 00:24:26 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A1C872CC3C; Wed, 12 Jun 2013 00:24:26 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5183C4F7.1020905@isode.com>
Date: Tue, 11 Jun 2013 16:24:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <30C7D834-5F4D-46C5-91A5-516C33820A7A@piuha.net>
References: <5183C4F7.1020905@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1503)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-6man-impatient-nud.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-6man-impatient-nud-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 21:24:36 -0000

Alexey,

Thank you very much for this review. I'm balloting a Yes based on your =
review and my own review.

Thanks all,

Jari

On May 3, 2013, at 9:08 AM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,  please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> Document: =
draft-ietf-6man-impatient-nud-06 Reviewer:  Alexey Melnikov Review Date: =
03 May 2013 IETF LC End Date: 9 May 2013 IETF Telechat Date: unknown =
Summary: This draft is ready for publication as Proposed Standard
> - Major Issues:None - Minor Issues:None - Nits: None
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jun 11 22:45:04 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA8B121F9B97 for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 22:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkSZANxIVPt6 for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 22:45:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9325721F9A27 for <gen-art@ietf.org>; Tue, 11 Jun 2013 22:44:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DF0212CC48; Wed, 12 Jun 2013 08:44:58 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yEULQYFcQSCo; Wed, 12 Jun 2013 08:44:57 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 46C002CC3C; Wed, 12 Jun 2013 08:44:57 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51B625D8.6020402@ericsson.com>
Date: Wed, 12 Jun 2013 00:44:57 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B22B5CA9-6D5C-45F9-B0F4-7251CD1A3C1B@piuha.net>
References: <51B625D8.6020402@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1503)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-geopriv-held-measurements.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-geopriv-held-measurements-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 05:45:04 -0000

Thank you very much for the review, Suresh. I followed your discussion =
with Martin, and the conclusions seem correct to me. But I don't think =
we should approve the draft until the -08 appears. Martin?

Jari

On Jun 10, 2013, at 2:15 PM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:

> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document:  draft-ietf-geopriv-held-measurements-07.txt
> Reviewer: Suresh Krishnan
> Review Date: 2013/06/10
> IESG Telechat date: 2013/06/13
>=20
>=20
> Summary: This draft is almost ready for publication as a Proposed
> Standard, but I had a few minor comments as identified
> in my last call review dated 2013/05/08. The authors had agreed to fix
> the following issues but I have not seen an updated draft yet.
>=20
> Minor
> =3D=3D=3D=3D=3D
>=20
> * Section 5.2
>=20
> - The Interface-Id option is the DHCPv6 equivalent of the circuit
> identifier defined in RFC3046. Please add a reference to Section 22.18
> of RFC3315 that describes this option.
>=20
> - Is there any specific reason that the giaddr is being specified =
using
> the IPv4-mapped IPv6 address format? =46rom my reading giaddr is of =
type
> bt:ipAddressType and it allows specification of both IPv4 and IPv6
> addresses natively.
>=20
> * Section 8.7 Page 53
>=20
> I think there may be an off-by-one error here.
>=20
> <xs:maxInclusive value=3D"268435456"/>
>=20
> Shouldn't this be
>=20
> <xs:maxInclusive value=3D"268435455"/>
>=20
> so that the largest value will fit in 28 bits?
>=20
> Thanks
> Suresh
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jun 11 23:08:41 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8A1521F9C13 for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 23:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.313
X-Spam-Level: 
X-Spam-Status: No, score=-102.313 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsUEkjZWrkrq for <gen-art@ietfa.amsl.com>; Tue, 11 Jun 2013 23:08:37 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A9B9821F9C0E for <gen-art@ietf.org>; Tue, 11 Jun 2013 23:08:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0E0522CC48; Wed, 12 Jun 2013 09:08:35 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bCzxoTY578Zq; Wed, 12 Jun 2013 09:08:34 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4248A2CC3C; Wed, 12 Jun 2013 09:08:34 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CALiegfnaTYGnetA6MNn9aArm2E0szvXjdWsosxnJy9C5ScUfbg@mail.gmail.com>
Date: Wed, 12 Jun 2013 09:08:34 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD8B3396-59DD-44F2-9361-1FC42578163C@piuha.net>
References: <51B6249D.8010501@ericsson.com> <CALiegfnaTYGnetA6MNn9aArm2E0szvXjdWsosxnJy9C5ScUfbg@mail.gmail.com>
To: =?windows-1252?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-Mailer: Apple Mail (2.1503)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-sipcore-sip-websocket-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 06:08:41 -0000

Suresh: Many thanks for the review. I=F1aki: thank you for agreeing to =
accommodate the suggested changes. Will we see a -09 soon? I think we =
should wait for the all updates to be posted before the final approval =
of the document=85

Jari

On Jun 11, 2013, at 2:47 AM, I=F1aki Baz Castillo <ibc@aliax.net> wrote:

> Hi Suresh,
>=20
> Sorry for the delay. This week I will publish a new version 09 of the
> draft addressing all the pending issues.
>=20
> Thanks a lot.
>=20
>=20
> 2013/6/10 Suresh Krishnan <suresh.krishnan@ericsson.com>:
>> I have been selected as the General Area Review Team (Gen-ART)
>> reviewer for this draft (for background on Gen-ART, please see
>> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>>=20
>> Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>>=20
>> Document:  draft-ietf-sipcore-sip-websocket-08.txt
>> Reviewer: Suresh Krishnan
>> Review Date: 2013/06/10
>> IESG Telechat date: 2013/06/13
>>=20
>> Summary: This draft is almost ready for publication as a Proposed
>> Standard, but has some minor issues that need to be fixed as =
identified
>> in my last call review dated 2013/04/16. One of the issues I raised =
was
>> clarified as common practice in the RAI wgs and I have removed it =
from
>> the list. The authors had agreed to fix the following issues but I =
have
>> not seen an updated draft yet.
>>=20
>> Minor
>> =3D=3D=3D=3D=3D
>>=20
>> * Section 4.1
>>=20
>> There is no error handling specified. i.e. What happens if the server
>> does not send a 101 reply with sip in the Sec-WebSocket-Protocol =
header?
>>=20
>> * Section 5.2.2
>>=20
>> RFC4168 does not update transport-param. Is this a copy and paste =
error?
>>=20
>> * Section 5.2.4
>>=20
>> Maybe it is just me, but the way I read it, this section leaves the
>> client without any mandatory to implement transport protocol for SIP
>> since it relaxes the need to implement UDP and TCP, as well as =
allowing
>> the implementation of the websocket transport using a MAY.
>>=20
>> Thanks
>> Suresh
>>=20
>>=20
>=20
>=20
>=20
> --=20
> I=F1aki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From martin.thomson@skype.net  Wed Jun 12 09:23:48 2013
Return-Path: <martin.thomson@skype.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F0321E804D for <gen-art@ietfa.amsl.com>; Wed, 12 Jun 2013 09:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level: 
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-CgqsJgt57Z for <gen-art@ietfa.amsl.com>; Wed, 12 Jun 2013 09:23:38 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBF411E80E8 for <gen-art@ietf.org>; Wed, 12 Jun 2013 09:23:38 -0700 (PDT)
Received: from BY2FFO11FD017.protection.gbl (10.1.15.202) by BY2FFO11HUB030.protection.gbl (10.1.14.115) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 12 Jun 2013 16:23:37 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD017.mail.protection.outlook.com (10.1.14.105) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 12 Jun 2013 16:23:37 +0000
Received: from TK5EX14MBXC253.redmond.corp.microsoft.com ([169.254.3.236]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Wed, 12 Jun 2013 16:23:21 +0000
From: Martin Thomson <martin.thomson@skype.net>
To: Jari Arkko <jari.arkko@piuha.net>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: [Gen-art] Gen-ART Telechat review of draft-ietf-geopriv-held-measurements-07.txt
Thread-Index: AQHOZg9SypXMqLPm9kq1DhKEqtmivpkxk9KAgACx7QA=
Date: Wed, 12 Jun 2013 16:23:19 +0000
Message-ID: <88EA7D224AA4F24F9D7628368F7572A911CCF222@TK5EX14MBXC253.redmond.corp.microsoft.com>
References: <51B625D8.6020402@ericsson.com> <B22B5CA9-6D5C-45F9-B0F4-7251CD1A3C1B@piuha.net>
In-Reply-To: <B22B5CA9-6D5C-45F9-B0F4-7251CD1A3C1B@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(24454002)(51704005)(377454002)(13464003)(189002)(45984002)(199002)(479174002)(85664002)(77096001)(20776003)(74502001)(76786001)(54356001)(66066001)(74662001)(77982001)(59766001)(6806003)(79102001)(54316002)(74706001)(56776001)(76796001)(80022001)(65816001)(56816003)(74876001)(74366001)(47776003)(81342001)(55846006)(23726002)(63696002)(4396001)(50466002)(31966008)(47446002)(16406001)(81542001)(50986001)(47976001)(46102001)(33656001)(46406003)(76482001)(49866001)(69226001)(47736001)(44976003)(15202345002)(53806001)(51856001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB030; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08756AC3C8
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-geopriv-held-measurements.all@tools.ietf.org" <draft-ietf-geopriv-held-measurements.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-geopriv-held-measurements-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 16:23:48 -0000

Correct.  There are a number of DISCUSS positions that will be resolved by =
-08.  I haven't read all the DISCUSS material yet, but I expect that there =
will need to be a few more edits to catch the rest of them.  I'll have to c=
oordinate with Richard to determine when to ship -08.  I don't want to inte=
rfere with AD reviews.

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]
> Sent: Tuesday, 11 June, 2013 22:45
> To: Suresh Krishnan
> Cc: draft-ietf-geopriv-held-measurements.all@tools.ietf.org; General Area
> Review Team
> Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-geopriv-held=
-
> measurements-07.txt
>=20
> Thank you very much for the review, Suresh. I followed your discussion wi=
th
> Martin, and the conclusions seem correct to me. But I don't think we shou=
ld
> approve the draft until the -08 appears. Martin?
>=20
> Jari
>=20
> On Jun 10, 2013, at 2:15 PM, Suresh Krishnan
> <suresh.krishnan@ericsson.com> wrote:
>=20
> > I have been selected as the General Area Review Team (Gen-ART)
> > reviewer for this draft (for background on Gen-ART, please see
> > http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
> >
> > Please wait for direction from your document shepherd or AD before
> > posting a new version of the draft.
> >
> > Document:  draft-ietf-geopriv-held-measurements-07.txt
> > Reviewer: Suresh Krishnan
> > Review Date: 2013/06/10
> > IESG Telechat date: 2013/06/13
> >
> >
> > Summary: This draft is almost ready for publication as a Proposed
> > Standard, but I had a few minor comments as identified in my last call
> > review dated 2013/05/08. The authors had agreed to fix the following
> > issues but I have not seen an updated draft yet.
> >
> > Minor
> > =3D=3D=3D=3D=3D
> >
> > * Section 5.2
> >
> > - The Interface-Id option is the DHCPv6 equivalent of the circuit
> > identifier defined in RFC3046. Please add a reference to Section 22.18
> > of RFC3315 that describes this option.
> >
> > - Is there any specific reason that the giaddr is being specified
> > using the IPv4-mapped IPv6 address format? From my reading giaddr is
> > of type bt:ipAddressType and it allows specification of both IPv4 and
> > IPv6 addresses natively.
> >
> > * Section 8.7 Page 53
> >
> > I think there may be an off-by-one error here.
> >
> > <xs:maxInclusive value=3D"268435456"/>
> >
> > Shouldn't this be
> >
> > <xs:maxInclusive value=3D"268435455"/>
> >
> > so that the largest value will fit in 28 bits?
> >
> > Thanks
> > Suresh
> >
> >
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
>=20


From jari.arkko@piuha.net  Thu Jun 13 09:07:37 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 627E121F9A1F; Thu, 13 Jun 2013 09:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3e8ie6I1Bz6; Thu, 13 Jun 2013 09:07:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4575A21F925A; Thu, 13 Jun 2013 09:07:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7F0EC2CC56; Thu, 13 Jun 2013 19:07:21 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0rA1p9X8DA4y; Thu, 13 Jun 2013 19:07:21 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id AAADB2CC61; Thu, 13 Jun 2013 19:07:20 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712980CA213@MX15A.corp.emc.com>
Date: Thu, 13 Jun 2013 19:07:19 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DC72F40-E427-4F50-9CA9-73F5C89F2E2C@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE712980C9EA5@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712980CA206@MX15A.corp.emc.com> <CAF4+nEER=JdeKV6PU_8m2jJ8O182WHcsQ-ayODUTCp1jRx-X+w@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE712980CA213@MX15A.corp.emc.com>
To: David Black <david.black@emc.com>
X-Mailer: Apple Mail (2.1503)
Cc: Donald Eastlake <d3e3e3@gmail.com>, joelja@bogus.com, General Area Review Team <gen-art@ietf.org>, joe.abley@icann.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2013 16:07:37 -0000

> I'm concerned about readers who aren't as
> cognizant of and comfortable/familiar with the relationships among
> OUIs and the identifiers based on them as people like you and me.

Thanks your review, David. The Gen-ART reviews are important for me in =
helping decide if the documents may have issues where I need to dig in =
deeper.

In this case I agree with the issue you raise and think it is a mistake =
that should be corrected. I see that Barry has already raised a discuss =
about that, however. I am balloting a No-Objection based on your review.

Jari



From mahoney@nostrum.com  Thu Jun 13 14:32:12 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4A121F9AF9 for <gen-art@ietfa.amsl.com>; Thu, 13 Jun 2013 14:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id omQdmIjkkXed for <gen-art@ietfa.amsl.com>; Thu, 13 Jun 2013 14:32:10 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DC13B21F9AE0 for <gen-art@ietf.org>; Thu, 13 Jun 2013 14:32:04 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5DLW1Nd066487 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 13 Jun 2013 16:32:02 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51BA3A4C.8070801@nostrum.com>
Date: Thu, 13 Jun 2013 16:31:56 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-06-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2013 21:32:12 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------

Kathleen Moriarty 2013-06-21  draft-ietf-ipsecme-ad-vpn-problem-07 *

Peter Yee         2013-06-27   draft-ietf-appsawg-rfc5451bis-07

Russ Housley      2013-06-27   draft-ietf-manet-rfc6622-bis-02

Roni Even         2013-06-24   draft-ietf-pkix-est-07 *

* On the June 27th telechat


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From ibc@aliax.net  Fri Jun 14 00:49:48 2013
Return-Path: <ibc@aliax.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C08F21F9248 for <gen-art@ietfa.amsl.com>; Fri, 14 Jun 2013 00:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.528
X-Spam-Level: 
X-Spam-Status: No, score=-1.528 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEyFMqCPb40C for <gen-art@ietfa.amsl.com>; Fri, 14 Jun 2013 00:49:48 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E988621F9133 for <gen-art@ietf.org>; Fri, 14 Jun 2013 00:49:47 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id hu16so2307qab.1 for <gen-art@ietf.org>; Fri, 14 Jun 2013 00:49:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=ozqtFlEE4h7qMaMrrJbgAHJ+S/hXcYMnqUx9/vRzqB8=; b=HfEdlLGi2SvaGFBTsD9gSRCMd4QGDf5XY0qGe0B4trGfXRuCtHLnGDwNPToKX+K7YN KQwp6eGFY7xtT0AYlpeRgeZ8w8r07H7nXUa1e5YubETXSMzP7BK52SpHSu7DRkrcy1+7 9rcnlbkIo8kOswjw5yHCD5MsRMKfT42tKThdbFgmM+UkZGc+k7Y4nq3iXWD3pPiTRzse BNIBbCSO8CMv/rYp8mt2iIJUAbmTUax9WtsGkymaxkjBUc0rls71EW64dP7oFAJHMupB ruruNhxJlzt8Qh4QVMHGYnU8aS0wV4CGsSY12P+cQ0XNa0kQsxxRXgjncDZlCh4XFeIV YmWA==
X-Received: by 10.49.109.72 with SMTP id hq8mr1108264qeb.38.1371196187063; Fri, 14 Jun 2013 00:49:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Fri, 14 Jun 2013 00:49:27 -0700 (PDT)
In-Reply-To: <516CF028.2030406@ericsson.com>
References: <516CF028.2030406@ericsson.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Fri, 14 Jun 2013 09:49:27 +0200
Message-ID: <CALiegfn_XKdZDaqKqYHgwNQnrTFSa6o0sN+8Gt=HYSfNDmcfFA@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQl9ABBU+r7ozgIpvVu5P4loO++zS/0DiOJRIp1Zs+I8m+BbctiiMGDvdoW/4+MNgs8Hiqse
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-sipcore-sip-websocket-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 07:49:48 -0000

Hi Suresh,

I reply again to your mail after having new rev 09 submitted:



2013/4/16 Suresh Krishnan <suresh.krishnan@ericsson.com>:


> * Section 4.1
>
> There is no error handling specified. i.e. What happens if the server
> does not send a 101 reply with sip in the Sec-WebSocket-Protocol header?

Addressed in rev 09:

- Improved section "Handshake" (under "The WebSocket SIP
Sub-Protocol") by mentioning the error handling when establishing a
WebSocket connection.



> * Section 5.2
>
> The updated ABNF provided in section 5.2.1. is confusing. e.g. RFC4168
> specifies the entire transport rule as follows
>
> transport         =3D  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP"
>                         / other-transport
>
> while this document just uses an incremental alternative and calls it an
> updated rule. I would have expected an *updated* rule to say
>
> transport         =3D  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP" / "WS"
>                         / "WSS" / other-transport

This has been explained within current mail thread. I expect then that
using the incremental style is appropriate.




> * Section 5.2.2
>
> RFC4168 does not update transport-param. Is this a copy and paste error?

Addressed in rev 09:

- Mention to RFC 4168 (SIP SCTP) removed from the "SIP URI Transport
Parameter" section.



> * Section 5.2.4
>
> Maybe it is just me, but the way I read it, this section leaves the
> client without any mandatory to implement transport protocol for SIP
> since it relaxes the need to implement UDP and TCP, as well as allowing
> the implementation of the websocket transport using a MAY.

Addressed by rev 09:

- "SIP transport implementation requirements" section clarified by
removing the "MAY" keyword and exact section from RFC 3261 section 18
amended.



Hope those actions address all the issues you reported.

Thanks a lot for your help and comments.



--
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From mahoney@nostrum.com  Fri Jun 14 08:18:56 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3731F21F9B8D for <gen-art@ietfa.amsl.com>; Fri, 14 Jun 2013 08:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3v84EIhs7TvC for <gen-art@ietfa.amsl.com>; Fri, 14 Jun 2013 08:18:55 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id C82EB21F9C6E for <gen-art@ietf.org>; Fri, 14 Jun 2013 08:18:53 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5EFIqjf088500 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 14 Jun 2013 10:18:53 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51BB3457.9000806@nostrum.com>
Date: Fri, 14 Jun 2013 10:18:47 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-06-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 15:18:56 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------

Alexey Melnikov   2013-06-28   draft-ietf-ipfix-protocol-rfc5101bis-08

Suresh Krishnan   2013-06-21   draft-ietf-ipsecme-ad-vpn-problem-07 *

Wassim Haddad     2013-06-27   draft-ietf-l2vpn-pbb-vpls-pe-model-07

* On the June 27th telechat


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From housley@vigilsec.com  Fri Jun 14 13:23:53 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132D521F9CC3; Fri, 14 Jun 2013 13:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RfgaREJGLlGQ; Fri, 14 Jun 2013 13:23:48 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E8E5A21F9B82; Fri, 14 Jun 2013 13:23:47 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8BB39F2407D; Fri, 14 Jun 2013 16:23:51 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id o1kzzxD7pdlj; Fri, 14 Jun 2013 16:23:44 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id BC3DFF24078; Fri, 14 Jun 2013 16:23:50 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Jun 2013 16:23:45 -0400
Message-Id: <90D2B755-F68F-4C58-A645-84E4445C73BE@vigilsec.com>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@ietf.org>, manet@ietf.org
Subject: [Gen-art] Gen-ART Review of draft-ietf-manet-rfc6622-bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 20:23:53 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-manet-rfc6622-bis-02
Reviewer: Russ Housley
Review Date: 2013-06-15
IETF LC End Date: 2013-06-27
IESG Telechat date: Unknown

Summary:  The document is almost ready for publication as a
standards track RFC.  I raise one major concern, and once it
is resolved, the document will be ready.

Major Concern:

In Section 12.2.3, is there any difference in processing when the
source IP address is IPv4 as opposed to IPv6?  Obviously, the two have
a different length.  Off the top of my head I cannot find a way for an
attacker to exploit one party using IPv4 in the ICV calculation and the
other party using IPv6.  Since the IPv6 address is 12 octets longer
than the IPv4 address, there may be some opportunity for an attacker.
Anyway, concerns like this are usually thwarted by including the length
of the overall hash function input as the first octet or two of the
value-to-be-hashed.  Such a value does not need to be transmitted.
Each party knows how many octets it passed to the hash function.


Minor Concerns:  

I find Section 1.1 a bit confusing.  I think it should start by saying
that RFC 6622 defined two ICV TLV extension types (0 and 1).  This
document repeats those definitions and adds a third ICV TLV extension
type (2).


Section 5 says:

  An ICV TLV with type extension = 2 specifies a modified version of
  this definition.
 
This is unclear.  I believe that an ICV TLV with type extension = 2 is
an update to ICV TLV with type extension = 1.  It would be good to
introduce the need for this update.  I suggest:

  An ICV TLV with type extension = 2 is the same as an ICV TLV with
  type extension = 1, except that the integrity protection also covers
  the source address of the IP datagram carrying the packet, message,
  or address block.

If you accept this suggestion, the following paragraph should also be
revised.  I suggest:

  Specifically, with type extension = 1 or type extension = 2, the
  <value> field contains the result of combining a cryptographic
  function and a hash function.  The <value> field contains multiple
  sub-fields indicating which hash function and cryptographic function
  have been used as specified in Section 12.


From kathleen.moriarty@emc.com  Sat Jun 15 00:46:29 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D30A21F9B1C; Sat, 15 Jun 2013 00:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7XkCADoQCgYH; Sat, 15 Jun 2013 00:46:25 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 15C1821F9B14; Sat, 15 Jun 2013 00:46:24 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5F7kMhR028589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Jun 2013 03:46:23 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sat, 15 Jun 2013 03:46:05 -0400
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5F7k4Xt000478; Sat, 15 Jun 2013 03:46:04 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Sat, 15 Jun 2013 03:46:03 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-ipfix-protocol-rfc5101bis.all@tools.ietf.org" <draft-ietf-ipfix-protocol-rfc5101bis.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "bclaise@cisco.com" <bclaise@cisco.com>, Brian Trammell <trammell@tik.ee.ethz.ch>, "paitken@cisco.com" <paitken@cisco.com>
Date: Sat, 15 Jun 2013 03:46:04 -0400
Thread-Topic: Gen-art review of: draft-ietf-ipfix-protocol-rfc5101bis-08
Thread-Index: AQHOaZxiqROw8XObW0GvKH8+DRPkAQ==
Message-ID: <182B306DD37FAD4882AB1C1EBE2CA9020EC6741390@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [Gen-art] Gen-art review of: draft-ietf-ipfix-protocol-rfc5101bis-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jun 2013 07:46:29 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-ipfix-protocol-rfc5101bis-08
Reviewer: Kathleen Moriarty
Review Date: June 15, 2013
IETF LC End Date:
IESG Telechat date: (if known)

Summary:   The draft is well written and ready for publication.  There is a=
t least one idnit that should be corrected, but should be fine for the Auth=
48 process.

Major issues:

Minor issues:

Nits/editorial comments:  From idnits, the first 2 should be fine:

    (See RFCs 3967 and 4897 for information about using normative reference=
s
     to lower-maturity documents in RFCs)

  -- Possible downref: Normative reference to a draft: ref. 'RFC5102bis'=20

  -- Possible downref: Non-RFC (?) normative reference: ref. 'IPFIX-IANA'

  =3D=3D Outdated reference: A later version (-04) exists of
     draft-ietf-ipfix-mediation-protocol-03



Sorry this took a while, my travel schedule has been hectic.=

From david.black@emc.com  Mon Jun 17 19:39:51 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B425F21F9CA1; Mon, 17 Jun 2013 19:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OD3-PUlgH65b; Mon, 17 Jun 2013 19:39:47 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D7E8B21F9C57; Mon, 17 Jun 2013 19:39:46 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5I2djDB011711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Jun 2013 22:39:45 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 17 Jun 2013 22:39:31 -0400
Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5I2dUJF026235; Mon, 17 Jun 2013 22:39:31 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Mon, 17 Jun 2013 22:39:30 -0400
From: "Black, David" <david.black@emc.com>
To: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, "jsalowey@cisco.com" <jsalowey@cisco.com>, General Area Review Team <gen-art@ietf.org>
Date: Mon, 17 Jun 2013 22:39:28 -0400
Thread-Topic: Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 02:39:51 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-abfab-eapapplicability-03
Reviewer: David L. Black
Review Date: June 17, 2003
IETF LC End Date: June 17, 2003

Summary:
This draft is on the right track but has open issues, described in the revi=
ew.

This draft updates the applicability statement for EAP to include usage
for application layer access via EAP over GSSAPI.  Additional security
requirements are introduced for environments in which EAP is used for
that purpose.

I found one open issue, which is minor, and may be editorial

Major issues: None

Minor issues: One

The next to last paragraph on p.3 begins with this sentence:

   For these reasons, channel binding MUST be implemented by peers, EAP
   servers and AAA servers in environments where EAP authentication is
   used to access application layer services.

It appear that this "MUST" requirement applies to all uses of EAP,
including network access authentication, not just application layer access
authentication.  If so, that's not immediately obvious from the text, and
an additional sentence should be added to make this clearer.  If not,
the above sentence needs to exclude network access authentication from
that requirement.

Nits/editorial comments:

The same paragraph (p.3) continues with:

   In addition, channel
   binding MUST default to being required by peers for non-network
   authentication.  If the EAP server is aware that authentication is
   for something other than a network service, it too MUST default to
   requiring channel binding.

What is meant by "non-network authentication" and "other than a network
service"?  If those mean "other than for network access authentication"
as the term "network access authentication" is used in section 1 and
RFC 3748, that meaning should be clarified.

idnits 2.12.17 generated this comment:

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If yo=
u
     have contacted all the original authors and they are all willing to gr=
ant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ign=
ore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer.=
=20
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.)

idnits appears to be confused ;-).  The -00 version of this draft is from 2=
012,
and this draft does not contain sufficient material from RFC 3748 that woul=
d
raise that concern, so this comment should be ok to ignore.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From chris.dearlove@baesystems.com  Tue Jun 18 02:16:08 2013
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4312821F9B20; Tue, 18 Jun 2013 02:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.261
X-Spam-Level: 
X-Spam-Status: No, score=-10.261 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8RnWvMIyioE8; Tue, 18 Jun 2013 02:16:04 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 7FCF621F8904; Tue, 18 Jun 2013 02:16:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,887,1363132800"; d="scan'208";a="347486685"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 18 Jun 2013 10:15:56 +0100
X-IronPort-AV: E=Sophos;i="4.87,887,1363132800"; d="scan'208";a="19264460"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasmds017.greenlnk.net with ESMTP; 18 Jun 2013 10:15:55 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0328.009; Tue, 18 Jun 2013 10:15:55 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-manet-rfc6622-bis-02
Thread-Index: AQHOaT0eFhzEQVZMPEinJ81AQTFy/Jk7MyUg
Date: Tue, 18 Jun 2013 09:15:54 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D250921AA@GLKXM0002V.GREENLNK.net>
References: <90D2B755-F68F-4C58-A645-84E4445C73BE@vigilsec.com>
In-Reply-To: <90D2B755-F68F-4C58-A645-84E4445C73BE@vigilsec.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: IETF Gen-ART <gen-art@ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-manet-rfc6622-bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 09:16:08 -0000

Comments below, marked >>>. I think (though I need my co-authors to agree o=
f course) that a draft with these revisions (and any others we need) will b=
e appropriate following any other IETF LC comments.

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Rus=
s Housley
Sent: 14 June 2013 21:24
To: IETF
Cc: IETF Gen-ART; manet@ietf.org
Subject: Gen-ART Review of draft-ietf-manet-rfc6622-bis-02

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-manet-rfc6622-bis-02
Reviewer: Russ Housley
Review Date: 2013-06-15
IETF LC End Date: 2013-06-27
IESG Telechat date: Unknown

Summary:  The document is almost ready for publication as a
standards track RFC.  I raise one major concern, and once it
is resolved, the document will be ready.

Major Concern:

In Section 12.2.3, is there any difference in processing when the
source IP address is IPv4 as opposed to IPv6?  Obviously, the two have
a different length.  Off the top of my head I cannot find a way for an
attacker to exploit one party using IPv4 in the ICV calculation and the
other party using IPv6.  Since the IPv6 address is 12 octets longer
than the IPv4 address, there may be some opportunity for an attacker.
Anyway, concerns like this are usually thwarted by including the length
of the overall hash function input as the first octet or two of the
value-to-be-hashed.  Such a value does not need to be transmitted.
Each party knows how many octets it passed to the hash function.

>>> As it happens, this value is present in the packet header, but not in t=
he message header, and we do not want to introduce a difference between the=
m. In addition, being after the address might not work.
>>> Like you, I can't see how to exploit and still maintain a legal structu=
re following, but attackers can be very resourceful. and I don't see that t=
his can be guaranteed.
>>> Thus, this appears a good suggestion, with minimal computational overhe=
ad and no over the air overhead.


Minor Concerns:  =


I find Section 1.1 a bit confusing.  I think it should start by saying
that RFC 6622 defined two ICV TLV extension types (0 and 1).  This
document repeats those definitions and adds a third ICV TLV extension
type (2).

>>> OK.

Section 5 says:

  An ICV TLV with type extension =3D 2 specifies a modified version of
  this definition.
 =

This is unclear.  I believe that an ICV TLV with type extension =3D 2 is
an update to ICV TLV with type extension =3D 1.  It would be good to
introduce the need for this update.  I suggest:

  An ICV TLV with type extension =3D 2 is the same as an ICV TLV with
  type extension =3D 1, except that the integrity protection also covers
  the source address of the IP datagram carrying the packet, message,
  or address block.

>>> Might tweak that a little, but OK.

If you accept this suggestion, the following paragraph should also be
revised.  I suggest:

  Specifically, with type extension =3D 1 or type extension =3D 2, the
  <value> field contains the result of combining a cryptographic
  function and a hash function.  The <value> field contains multiple
  sub-fields indicating which hash function and cryptographic function
  have been used as specified in Section 12.

>>> Essentially moving detail from this paragraph to previous one.


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From prvs=3881e1e3e5=magnus.westerlund@ericsson.com  Tue Jun 18 04:41:57 2013
Return-Path: <prvs=3881e1e3e5=magnus.westerlund@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BCA221F9BFF; Tue, 18 Jun 2013 04:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.083
X-Spam-Level: 
X-Spam-Status: No, score=-106.083 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQo9H494EDTZ; Tue, 18 Jun 2013 04:41:51 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF4F21F9BD9; Tue, 18 Jun 2013 04:41:50 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-10-51c0477cc1fc
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id F5.63.15700.C7740C15; Tue, 18 Jun 2013 13:41:49 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Tue, 18 Jun 2013 13:41:49 +0200
Message-ID: <51C047BC.1050207@ericsson.com>
Date: Tue, 18 Jun 2013 13:42:52 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <51AFB3FF.7000009@nostrum.com>
In-Reply-To: <51AFB3FF.7000009@nostrum.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHLMWRmVeSWpSXmKPExsUyM+JvrW6t+4FAg/NfOC2u7Z7CZHH11WcW i2cb57NYTF3+mMXi2pxGNgdWjyVLfjJ5zNr5hMXjy+XPbAHMUdw2SYklZcGZ6Xn6dgncGV+n TGUqeLOXseLCs2fsDYxPpjF2MXJySAiYSFx4dYwJwhaTuHBvPVsXIxeHkMApRom172YyQjjL GSXe71rNClLFK6Atsf5BD1g3i4CqxJEdE8G62QQsJG7+aGQDsUUFgiWObN/MAlEvKHFy5hMw W0RAQ+LakiXsIEOZBSYzSszbcAmsQVjATWLGsY3sILaQgJbEww/nwBo4gZZNXX0B6jxJiS0v 2sFqmAUMJI4smsMKYctLNG+dzQzRqy3R0NTBOoFRaBaS3bOQtMxC0rKAkXkVI3tuYmZOernh JkZgcB/c8lt3B+OpcyKHGKU5WJTEeT+c2hUoJJCeWJKanZpakFoUX1Sak1p8iJGJgxNEcEk1 MCbJ+Eyo92Lc7ZoV6LQh/MT6k+t3pzNJ7Npz5s33Wev9VzVcDEqSWHqqdq3Ho5aShItz2zZs kCm9Iii3OnmNPs/y+CCmeM4Jf3rfBHoZPulKt5hgIrI8N+0uu9iJypdt4QYK977Jr36hUmBY +klSRnWDs82Zve1XCo2n6DH/OqaU43HW4mZYkxJLcUaioRZzUXEiAAs+RylBAgAA
Cc: draft-ietf-mmusic-rfc2326bis@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, mmusic@ietf.org
Subject: Re: [Gen-art] Gen-art last call review: draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 11:41:57 -0000

Hi Robert,

Thanks for the massive review. A number of really good comments in here.
Below you will find my answers, comments, questions and in most cases
clarifications what I see us doing with your comment. These covers your
major and minor comments. The nits we will simply implement as we see
fit, if we have questions we will comeback with those.

WG, there are a number of issues in here that would be greatly helped by
your input!

On 2013-06-05 23:56, Robert Sparks wrote:
> Document: draft-ietf-mmusic-rfc2326bis-34
> Reviewer: Robert Sparks
> Review Date: 05-Jun-2013
> IETF LC End Date: 04-Jun-2013
> IESG Telechat date: not yet on a telechat
>
>
> The document is very long, and the structure is unusual - much of the
> definition of the protocol itself is in the appendices. You are missing
> an opportunity to make this document much shorter (thereby likely
> increasing its effectiveness). Much of the jump in from RFC2326 was
> importing the description of headers and responses from HTTP, tailoring
> them to RTSP. That was a good exercise in that it highlights some issues
> that would otherwise be non-obvious (and raises a few questions below).
> But you followed the style from HTTP perhaps too closely - much shorter
> descriptions without examples might have done the job better. Overall,
> separating exposition and examples from the protocol definition would
> make it much easier for an implementer to find the definition of the
> protocol, and use the document as a reference when diagnosing a failure
> to interoperate.

Agree, it would be differently structure if we wrote it from scratch
today. But it is an document that is 10 years in the making with dual
heritage in RFC 2326 and RFC 2068.

>
> Major Issues
>
> I'm not seeing what instructs an RTSP element on how to find the server
> it would try to open a connection to given an rtsp or rtsps URI? Are you
> assuming it would be doing A or AAAA DNS lookups? 

Yes, using A or AAAA DNS records are assumed. No problem making that
explicit.

Should this protocol
> use NAPTR/SRV? 

Potentially, but as everyone have been using A records for all these
years, I think it is not worth defining it at this stage.

The document should be explicit. On a related note, (and
> maybe I missed this), but where do you talk about what an element should
> check in the server's certificate when connecting over TLS? Are you
> assuming a common name match? Or are you expecting some SubjectAltName
> processing?

This draft says in Section 19.2 the following regarding this:

   RTSP MUST follow the same guidelines with
   regards to TLS [RFC5246] usage as specified for HTTP, see [RFC2818].

Where section 3.1 (Server Identity) of RFC 2818 contains the following:

   If a subjectAltName extension of type dNSName is present, that MUST
   be used as the identity. Otherwise, the (most specific) Common Name
   field in the Subject field of the certificate MUST be used.

Isn't that clear enough on that matter?

>
> The document should say more about when connection reuse is appropriate,
> particularly when the connections happened because of an rtsps uri. Two
> different names might resolve to the same IP address - reusing a
> connection formed when looking at the first name (and verifying the
> server's cert) is dangerous. A new connection needs to be formed (and
> verified) instead.

I want to check my understanding of the issue you are seeing here. So a
client looks ups foo.example.org, gets an ip address A and establishes
an TCP/TLS connection and verifies that there are a SubjectAltName that
matches foo.example.org works. Then client is going to open
bar.example.com and looks up that address and gets the same IP address A.
Client matches A against existing connections and simply sends a request to
bar.example.com. Thus bypassing the certificate verification.

If we clarify that in the process of opening rtsps://bar.example.com the
client MUST verify that the server certificate for the TLS connection it
considers re-using has an SubjectAltName of bar.example.com, does that
resolve your concerns. If not, please explain the concern further.


>
> The text talks about the option to queue S->C requests if there isn't a
> connection to the client available. Ostensibly, this means the request
> can go down some future connection. It's not clear how the server can
> tell the right client connected. In particular, when using rtsps, how do
> you prevent a malicious client from getting such a queued message that
> wasn't meant for him?


Okay, this security issue I have totally missed but it is clearly
serious. I don't see any easy way of fixing this. Thus I would suggest
that we simply make it clear that a server MUST NOT queue the S->C RTSP
message, independent if they are requests PLAY_NOTIFY and TEARDOWN or
responses to client requests.


>
> Given that the text talks about queuing S-C requests, it should
> explicitly call out whether a server can queue a response if the
> connection the associated request arrived on is no longer available. I
> think what you want to say is that such a response must not be queued,
> and must be dropped.

Agreed, lets mandate that they are dropped.


>
> There are several places in the text that talk about using a 503
> response with a Retry-After header to push back on traffic from an
> element (the first is section 10.7).
> * It's not clear what the subject of a 503 is. Is it intended to be
> scoped to requests to the resource in the RURI of the associated
> request? Is it intended to be scoped to the domain in that resource? Or
> is it, like in SIP, intended to be scoped to the server issuing the
> response, independent of what the RURI contained?

Very good question. It is far from obvious what the best choice is. And
I think even talking only about URI related scope may not be the best.

The case I have in mind is if a proxy that has several already
established RTSP sessions over a persistent connection. When a client
connected to the proxy requests to establish a new session the server
may have insufficient resource to handle the SETUP request and send a
503 answer. However if another client already having an RTSP session for
the same resource want to terminate that session it would be strange to
refuse to process the message as it will actually free up resources.

This makes me believe that you need to have a RTSP Session scope for any
request carrying a Session-ID and a general server, or host name scope
for non-associated that doesn't prevent established sessions to try.

Thoughts on this?


> * If the intent is that the 503 talks about the server, then you should
> clarify that a proxy doesn't simply forward 503 responses (after
> rewriting CSeqs), and should probably have a response of its own.
> Otherwise, clients that might be talking to two different servers
> through one proxy would lose access to both of them when one of the
> servers 503ed.

If we us a host and session scope then this issue would not be present.
However, if the proxy is actually overloaded that still needs its own
552 Proxy Unavailable response with the same scope rules as for the 503,
but where unassociated requests concerns sending to the proxy at all.

>
> Section 4.9.1 lists values the Seek-Style header can take, but 18.45
> lists a completely different set (which most of the rest of the document
> uses). Should 4.9.1 be changed to use the values in 18.45? Are the right
> strings being used in sections 13.4.4 through 13.4.6? Those appear to be
> using strings from 4.9.1.

Yes, clearly an inconsistency issue that needs to be resolved.

>
> The document will not stand if you delete some of the appendices. They
> aren't supplementary material. Please consider restructuring the
> normative sections back into the main document, or clearly identifying
> which ones define protocol and which are background information.

I would like to characterize this differently. I think you will have a
working protocol of RTSP, but you can't use it for anything. This as you
will have no media transport (C), no media description protocol (D), and
no parameters format (F). But, these appendixes are replaceable with
other protocol solutions.

The Introduction section (1) says:

                                 The appendixes describe and define some
   functionalities that are not part of the core RTSP specification, but
   which are still important to enable some usages.  Among them, the RTP
   usage is defined in Appendix C and the SDP usage with RTSP is defined
   in Appendix D, which are two mandatory appendixes.

I note that we should add F to this list.

I think we should be clear in each of this appendices that if one
support Foo for the purpose of bar then this appendix defines
normatively how one does it.


>
> Section 15 talks about a "transparent' proxy, but there is no
> description in this document of what protocol such a thing should
> follow. What bad thing happens if you remove all mention of
> "transparent" proxies from the document? As far as I can tell, that
> won't affect the protocol definition at all.

Not really, there is no definition of transparent proxies currently.
There is one security concern that make require some word smithing if we
remove transparent proxies.

>From my perspective a transparent proxy is something that hijacks a TCP
connection towards an RTSP server to be a proxy between client and
server. Further is not detectable from the client's or the servers
perspective, but still may modify RTSP messages within the bounds of the
RTSP protocol.

But, in reality as we have proxies that are visible we should focus on
those and forget this bastard version.

>
> The list of steps for establishing an SRTP cryptographic context in
> C.1.4.1 says "This specification does not specify an explicit method for
> indicating this SRTP cryptographic context establishment method, but
> future specifications may." in the context of looking at the SDP. SDP
> _has_ methods of indicating what keying mechanism is used with SRTP -
> are you talking about something different? 

I think you are considering the methods for keying SRTP that are
Offer/Answer dependent. The only RTSP SDP using method that exist is the
one defined in RFC 4567, which we are explicit on not using.

Why doesn't this section say
> something like "the use of SRTP with RTSP is only defined with MIKEY
> with keys established as defined in this section. Future documents may
> talk about how an RTSP implementation might treat SDP that indicates
> some other key mechanism be used"? 

Yes, that is appears better, but we will have to make it clear that is
is regarding RTSP 2.0. Must also think if RFC 4567 needs to be worked
into that sentence.

Could you provide an example in the
> document of an RTSP message carrying SDP reflecting the use of SRTP as
> defined in this document?

The point is that the only difference is that he RTP profile is SAVP/RTP
or SAVPF/RTP in the SDP. Thus making such an SDP isn't difficult.
Question is if it provides a benefit?



> Minor Issues
>
> The document uses the notion of a "control connection" (it appears first
> in section 2.5) without defining what that is, or what kind of
> connections you might have that aren't control connections.

The "control connection" is the connection established for sending RTSP
messages on it. I agree it is undefined and could likely be replaced by
the "RTSP connection" or "connection for RTSP messages"

>
> The update to the registration of the rtsp and rtsps schema call out
> that there are changes that can result in interoperability issues. It
> doesn't say what the issues are, or who might encounter them. I can
> infer that the point is that there might be problems if a URI following
> this updated registration were to be processed by an RTSP 1.0
> implementation (or any other application that relied on the previous
> definition). It would be better to say that explicitly, and talk about
> how a previous implementation is likely to act when presented with a URI
> that exercised these new changes.

I have gotten these comment elsewhere and have prepared a text update
for section 4.2:

   The details of the syntax of "rtsp" and "rtsps" URIs has been changed
   from RTSP 1.0.  These changes are:

   o  Support for IPV6 literal in host part and future IP literals
      through RFC 3986 defined mechanism.

   o  A new relative format to use in the RTSP protocol elements that is
      not required to start with "/".

   Neither should have any significant impact on interoperability.  If
   one is required to use IPv6 literals to reach an RTSP server, then
   that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
   IPv6 capable protocol.  If an RTSP 1.0 client attempts to process the
   URI it will not match the allowed syntax and be considered invalid
   and processing will be stopped.  This is clearly a failure to reach
   the resource, however it is not a signification issue as RTSP 2.0
   support was needed anyway in both server and client.  Thus failure
   will only occur in a later step when there is a RTSP version
   mismatch between client and server.  The second change will only
   occur in RTSP messages, that are explicitly identified as being RTSP
   2.0 messages, thus a RTSP 1.0 only agent will not be required to
   parse this variant.

Clear enough?

The above is Edited In.

 (It's not clear to me that all of the
> thread at www.ietf.org—msg01567.html
> <http://www.ietf.org/mail-archive/web/uri-review/current/msg01567.html>
> concluded - I see how the fragments question ended, but what about
> things like the addition of IPV6 literals? In particular, I'm not
> finding a response where Ted Hardie agreed that the potential for
> interoperability failure had been adequately addressed).

I talked to him in person about this just after the discussion to better
understand his comments. If we want a confirmation I think we need to
loop him into a discussion regarding this particular issue.

I provided a clarification to the designated URI reviewer which accepted
the request.

>
>
> I think you've said something different than you mean in 5.4 item 1. I
> think you mean to say that an RTSP implementation would ignore any body
> that happened to come in message that MUST NOT contain one. What you've
> said is that the part of the parser that's doing framing has to stop
> framing at the end of the headers, and that such an errant body would be
> parsed as a separate message. As written this would keep someone from
> using an Internet Message Format parser since it would have to ignore
> any Content-Length that might have appeared, even though it wasn't
> supposed to.

Yes, it is clearly sufficient to ignore the body, and likely much better
from an error handling consideration.

We will propose a text change.


>
> In section 10.4, it looks like a server can keep an RTSP transaction
> pending forever if it sends 100 responses often enough. I assume the
> client's recourse if it doesn't want to remain involved is to close the
> connection. If that's right, it's worth calling it out explicitly in
> this section.

This is likely a good suggestion, and works fine if the client simply
wants to abort the request and is anyway abandoning the RTSP session.
However, the question is what to do if just the request becomes
irrelevant and instead want to do something else with the RTSP session.
A single client may abandon the connection, open a new one and issue a
request, to a potentially undetermined session state. Yet another
complexity is what a proxy does that has multiple RTSP sessions on the
same server. Here the rules for processing in order the different
requests and their relation to answers in the same order.

This makes me want to weaken the recommendation on re-using an
connection for multiple RTSP sessions.


>
> Somewhere, probably in section 15.2, you should be explicit that a proxy
> that is multiplexing requests MUST keep the requests in the same order
> as they are folded together. You can infer that, or things simply break,
> but saying it explicitly would be better.

Probably, as a clarification to what is already present in section 18.19
(CSeq header)

   Proxies that aggregate several sessions on the same transport will
   have to ensure that the requests sent towards a particular server
   have a joint sequence number space, i.e., they will regularly need to
   renumber the CSeq header field in requests (from proxy to server) and
   responses (from server to proxy) to fulfill the rules for the header.
   The proxy MUST increase the CSeq by one for each request it
   transmits, without regard of different sessions.


>
> Both GET_PARAMETER and SET_PARAMETER are listed as keep-alive methods in
> 10.5, but the note in section 13 on table 7 only uses that as a reason
> for requiring SET_PARAMETER. Why doesn't it also apply to GET_PARAMETER?
> And why is this only required at servers? "Required" in this section
> means Mandatory to Implement, I think. If that's right, it should be
> made explicit. If that's not right, what does it mean?

Yes, required is Required to implement in the server. The GET_PARAMETER
is not required as only one method for keep-alive is necessary. Thus,
the ones that needs to use GET/SET_PARAMETER for keep-alive will have to
choose SET_PARAMETER.

It is only required at the server, as it is in the client implementation
choice of how to ensure keep-alive works. As this is also dependent on
the media transport support one has, the client may not need a method
based keep-alive.

Clarifying "Required" should be straightforward.

>
> Section 13.8 makes a good argument for always putting parameters to be
> retrieved in a body. Why are you keeping the complexity of also allowing
> them in headers?

Some arguments are probably lost in the passage of time. However, the
headers specified to be suitable for inclusion in a GET_PARAMETER
requests are used for providing these information also in other methods,
thus we have not wanted to duplicate the representation of this
information in both a body and a header form.

>
> Section 13.10: "That should not provide any benefit." is not clear - can
> you expand it a little?

   If the REDIRECT request times out following the rules in Section 10.4
   the server MAY terminate the session or transport connection that
   would be redirected by the request.  This is a safeguard against
   misbehaving clients that refuse to respond to a REDIRECT request.
   That should not provide any benefit.

The intention here is to make clear that there shouldn't be an incentive
in the protocol to not acknowledge a REDIRECT request and instead simply
go on as it wasn't received or seen. Thus, we want to make clear that
the server may simply terminate the session in those cases.

I propose we change this sentence to:

Thus, removing any incentive to not acknowledge the reception of a
REDIRECT request.

Edited In

>
> In Section 13.10 you talk about clients _sending_ media (search for
> "send or receive media"). Do you mean anything more than possibly RTCP?
> Can you make that clear in the section?

You mean this sentence:

   After a REDIRECT request has been processed, a client that wants to
   continue to send or receive media for the resource identified by the
   Request-URI will have to establish a new session with the designated
   host.

The mentioning of send media is likely a RECORD reference. In this case
I don't see any issue with removing it.

Edited In

>
> Section 15.2's second paragraph appears to be the only place the proxy
> rewriting of CSeq in order to multiplex requests is defined, and it is
> very loose. It would be easy for a reader to fail to recognize this as
> an interoperability requirement. Please consider expanding how this is
> specified when addressing the comment about above about keeping requests
> in relative order when multiplexing.

There are text in Section 18.19 CSeq also. But I do think I agree that
this should be clarified.

>
> You follow the principle of saying a client should treat a response with
> an unknown response code, the same as it would treat the x00 of that
> class (e.g. 400 for an unknown 4xx). However, you do not define what a
> response code of 300 means. How is a client supposed to handle an
> unknown 3xx response?

Sorry, I don't quite get this comment. Section 17.3 says:

   If a 3rr response is received for a request in relation to
   an established session, the client SHOULD send a TEARDOWN request for
   the session, and MAY reestablish the session using the resource
   indicated by the Location.

   If the Location header is used in a response it MUST contain an
   absolute URI pointing out the media resource the client is redirected
   to, the URI MUST NOT only contain the host name.

As explained above unknown 3XX codes will be 3rr codes, as 304 isn't
unknown.

If you don't believe this is sufficient can you please be more explicit
about the issue?

>
> As written, a client and server can use HTTP Basic authentication over
> TCP that is not protected with TLS. Consider restricting it's use to TLS
> only. Are you sure you don't need to say anything RTSP specific about
> DIGEST computations (I don't think you need to go as far as SIP did
> talking about DIGEST, but I'm surprised you haven't run into issues
> relying only on 2617 literally.

Are you referring to Section 19.1 here?

Yes, I would not have any issue with requiring Basic to be combined with
TLS. I think that is appropriate.

When it comes to DIGEST, are you referring to section 22.4 in RFC 3261?

That section indicates that some clarifications are likely needed.

>
>
> How does 411 Length Required for this protocol make sense? Given that
> you've restricted the protocol to TCP and require the Content-Length
> header to be present if there is a body, in what circumstance would a
> server need to send a 411?

It really should occur for malformed messages, which we could use 400 as
response. So yes, 411 could be removed.

>
>
> Section 18.19 requires senders to increment CSeq by 1. We have a
> reliable transport with no request retransmission, so there should never
> be gaps at the receiver. Should the receiver check and react some way if
> there are gaps? I think you should explicitly tell them not to even
> look. If you agree, why is incrementing by one important as long as you
> are always strictly increasing?

I agree that for TCP or other reliable transports the receiver
SHOULD/SHALL ignore gaps. For any future specification of an unreliable
transport of RTSP messages this would be needed. As noted in Appendix G,
CSeq is retained for future support of unreliable transport.

>
> You call out several places where RTCP is essential to allow RTSP using
> RTP to work correctly, yet section C.1.2 sets up conditions where RTCP
> MUST NOT be sent. Why are you allowing those instead of treating the
> conditions you describe as errors?

Good question. I think it is a case we must ensure that you can
negotiate and configure your desired way, without really considering if
it should be allowed at all. I think mandating usage of RTCP with RTP
for RTSP 2.0 would be good. But, I think that needs to be verified with
the WG.

cheers


Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From hartmans@painless-security.com  Tue Jun 18 07:19:16 2013
Return-Path: <hartmans@painless-security.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5177C21F9F12; Tue, 18 Jun 2013 07:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWb5-QCOOfSL; Tue, 18 Jun 2013 07:19:10 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 6240121F9EE1; Tue, 18 Jun 2013 07:19:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id BC2032013A; Tue, 18 Jun 2013 10:15:09 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bd8b3jpw8fH3; Tue, 18 Jun 2013 10:15:08 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 18 Jun 2013 10:15:08 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 525ED80046; Tue, 18 Jun 2013 10:18:50 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: "Black\, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com>
Date: Tue, 18 Jun 2013 10:18:50 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> (David Black's message of "Mon, 17 Jun 2013 22:39:28 -0400")
Message-ID: <tsl38sfbiyd.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Tue, 18 Jun 2013 07:20:56 -0700
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "jsalowey@cisco.com" <jsalowey@cisco.com>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 14:19:16 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:

    Black,> The next to last paragraph on p.3 begins with this sentence:

    Black,>    For these reasons, channel binding MUST be implemented by
    Black,> peers, EAP servers and AAA servers in environments where EAP
    Black,> authentication is used to access application layer services.

    Black,> It appear that this "MUST" requirement applies to all uses
    Black,> of EAP, including network access authentication, not just
    Black,> application layer access authentication.  If so, that's not
    Black,> immediately obvious from the text, and an additional
    Black,> sentence should be added to make this clearer.  If not, the
    Black,> above sentence needs to exclude network access
    Black,> authentication from that requirement.


I know you're correct that AAA servers and EAP servers need to implement
channel binding for network access in such environments.
I'm not sure whether peers only doing network access SHOULD implement
channel binding or MUST implement channel binding.

Practically speaking, it will be a while before peers implement channel
binding for network access.
The sorts of attacks that result without channel binding are attacks
where a peer thinks it is doing network access authentication but what
it's really doing is helping an attacker access an application.
If all the application access peers support channel binding, then you
could potentially require the eap-lower-layer attribute or similar for
application authentication and work securely in environments where peers
for network access have not been updated yet.
It's also kind of tempting to stick our head in the sand and just add
the clarification that "yes, we mean network access too."

--Sam

From rjsparks@nostrum.com  Tue Jun 18 07:21:36 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E0FD21F949F; Tue, 18 Jun 2013 07:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.277
X-Spam-Level: 
X-Spam-Status: No, score=-102.277 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZmQ3PEWLTCW; Tue, 18 Jun 2013 07:21:34 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6C8E621F9133; Tue, 18 Jun 2013 07:21:32 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5IELLtJ024140 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 18 Jun 2013 09:21:22 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <51C06CDC.9050804@nostrum.com>
Date: Tue, 18 Jun 2013 09:21:16 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <51AFB3FF.7000009@nostrum.com> <51C047BC.1050207@ericsson.com>
In-Reply-To: <51C047BC.1050207@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Cc: draft-ietf-mmusic-rfc2326bis@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, mmusic@ietf.org
Subject: Re: [Gen-art] Gen-art last call review: draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 14:21:37 -0000

Hi Magnus -

Thanks for your careful treatment of these comments - I think you're on 
a good path with all the suggestions below.
Responses to questions and a few comments inline:

On 6/18/13 6:42 AM, Magnus Westerlund wrote:
> Hi Robert,
>
> Thanks for the massive review. A number of really good comments in here.
> Below you will find my answers, comments, questions and in most cases
> clarifications what I see us doing with your comment. These covers your
> major and minor comments. The nits we will simply implement as we see
> fit, if we have questions we will comeback with those.
>
> WG, there are a number of issues in here that would be greatly helped by
> your input!
>
> On 2013-06-05 23:56, Robert Sparks wrote:
>> Document: draft-ietf-mmusic-rfc2326bis-34
>> Reviewer: Robert Sparks
>> Review Date: 05-Jun-2013
>> IETF LC End Date: 04-Jun-2013
>> IESG Telechat date: not yet on a telechat
>>
>>
>> The document is very long, and the structure is unusual - much of the
>> definition of the protocol itself is in the appendices. You are missing
>> an opportunity to make this document much shorter (thereby likely
>> increasing its effectiveness). Much of the jump in from RFC2326 was
>> importing the description of headers and responses from HTTP, tailoring
>> them to RTSP. That was a good exercise in that it highlights some issues
>> that would otherwise be non-obvious (and raises a few questions below).
>> But you followed the style from HTTP perhaps too closely - much shorter
>> descriptions without examples might have done the job better. Overall,
>> separating exposition and examples from the protocol definition would
>> make it much easier for an implementer to find the definition of the
>> protocol, and use the document as a reference when diagnosing a failure
>> to interoperate.
> Agree, it would be differently structure if we wrote it from scratch
> today. But it is an document that is 10 years in the making with dual
> heritage in RFC 2326 and RFC 2068.
>
>> Major Issues
>>
>> I'm not seeing what instructs an RTSP element on how to find the server
>> it would try to open a connection to given an rtsp or rtsps URI? Are you
>> assuming it would be doing A or AAAA DNS lookups?
> Yes, using A or AAAA DNS records are assumed. No problem making that
> explicit.
>
> Should this protocol
>> use NAPTR/SRV?
> Potentially, but as everyone have been using A records for all these
> years, I think it is not worth defining it at this stage.
>
> The document should be explicit. On a related note, (and
>> maybe I missed this), but where do you talk about what an element should
>> check in the server's certificate when connecting over TLS? Are you
>> assuming a common name match? Or are you expecting some SubjectAltName
>> processing?
> This draft says in Section 19.2 the following regarding this:
>
>     RTSP MUST follow the same guidelines with
>     regards to TLS [RFC5246] usage as specified for HTTP, see [RFC2818].
>
> Where section 3.1 (Server Identity) of RFC 2818 contains the following:
>
>     If a subjectAltName extension of type dNSName is present, that MUST
>     be used as the identity. Otherwise, the (most specific) Common Name
>     field in the Subject field of the certificate MUST be used.
>
> Isn't that clear enough on that matter?
Yes - I was worried that I might have missed it before.
>
>> The document should say more about when connection reuse is appropriate,
>> particularly when the connections happened because of an rtsps uri. Two
>> different names might resolve to the same IP address - reusing a
>> connection formed when looking at the first name (and verifying the
>> server's cert) is dangerous. A new connection needs to be formed (and
>> verified) instead.
> I want to check my understanding of the issue you are seeing here. So a
> client looks ups foo.example.org, gets an ip address A and establishes
> an TCP/TLS connection and verifies that there are a SubjectAltName that
> matches foo.example.org works. Then client is going to open
> bar.example.com and looks up that address and gets the same IP address A.
> Client matches A against existing connections and simply sends a request to
> bar.example.com. Thus bypassing the certificate verification.
>
> If we clarify that in the process of opening rtsps://bar.example.com the
> client MUST verify that the server certificate for the TLS connection it
> considers re-using has an SubjectAltName of bar.example.com, does that
> resolve your concerns. If not, please explain the concern further.
You understood what I intended, and your resolution looks sufficient.
>
>
>> The text talks about the option to queue S->C requests if there isn't a
>> connection to the client available. Ostensibly, this means the request
>> can go down some future connection. It's not clear how the server can
>> tell the right client connected. In particular, when using rtsps, how do
>> you prevent a malicious client from getting such a queued message that
>> wasn't meant for him?
>
> Okay, this security issue I have totally missed but it is clearly
> serious. I don't see any easy way of fixing this. Thus I would suggest
> that we simply make it clear that a server MUST NOT queue the S->C RTSP
> message, independent if they are requests PLAY_NOTIFY and TEARDOWN or
> responses to client requests.
Works for me. Does this mean you are removing cross-connection queueing 
altogether?
>
>
>> Given that the text talks about queuing S-C requests, it should
>> explicitly call out whether a server can queue a response if the
>> connection the associated request arrived on is no longer available. I
>> think what you want to say is that such a response must not be queued,
>> and must be dropped.
> Agreed, lets mandate that they are dropped.
>
>
>> There are several places in the text that talk about using a 503
>> response with a Retry-After header to push back on traffic from an
>> element (the first is section 10.7).
>> * It's not clear what the subject of a 503 is. Is it intended to be
>> scoped to requests to the resource in the RURI of the associated
>> request? Is it intended to be scoped to the domain in that resource? Or
>> is it, like in SIP, intended to be scoped to the server issuing the
>> response, independent of what the RURI contained?
> Very good question. It is far from obvious what the best choice is. And
> I think even talking only about URI related scope may not be the best.
>
> The case I have in mind is if a proxy that has several already
> established RTSP sessions over a persistent connection. When a client
> connected to the proxy requests to establish a new session the server
> may have insufficient resource to handle the SETUP request and send a
> 503 answer. However if another client already having an RTSP session for
> the same resource want to terminate that session it would be strange to
> refuse to process the message as it will actually free up resources.
>
> This makes me believe that you need to have a RTSP Session scope for any
> request carrying a Session-ID and a general server, or host name scope
> for non-associated that doesn't prevent established sessions to try.
>
> Thoughts on this?
That seems like it might work - exploring the idea should get some
WG cycles.
>
>
>> * If the intent is that the 503 talks about the server, then you should
>> clarify that a proxy doesn't simply forward 503 responses (after
>> rewriting CSeqs), and should probably have a response of its own.
>> Otherwise, clients that might be talking to two different servers
>> through one proxy would lose access to both of them when one of the
>> servers 503ed.
> If we us a host and session scope then this issue would not be present.
> However, if the proxy is actually overloaded that still needs its own
> 552 Proxy Unavailable response with the same scope rules as for the 503,
> but where unassociated requests concerns sending to the proxy at all.
If you build one of these, please be sure to highlight the impact of the
other sessions already established, and call out the potential for
problems if you forward one as a Proxy, as opposed to generating your
own based on the situation.
>
>> Section 4.9.1 lists values the Seek-Style header can take, but 18.45
>> lists a completely different set (which most of the rest of the document
>> uses). Should 4.9.1 be changed to use the values in 18.45? Are the right
>> strings being used in sections 13.4.4 through 13.4.6? Those appear to be
>> using strings from 4.9.1.
> Yes, clearly an inconsistency issue that needs to be resolved.
>
>> The document will not stand if you delete some of the appendices. They
>> aren't supplementary material. Please consider restructuring the
>> normative sections back into the main document, or clearly identifying
>> which ones define protocol and which are background information.
> I would like to characterize this differently. I think you will have a
> working protocol of RTSP, but you can't use it for anything. This as you
> will have no media transport (C), no media description protocol (D), and
> no parameters format (F). But, these appendixes are replaceable with
> other protocol solutions.
>
> The Introduction section (1) says:
>
>                                   The appendixes describe and define some
>     functionalities that are not part of the core RTSP specification, but
>     which are still important to enable some usages.  Among them, the RTP
>     usage is defined in Appendix C and the SDP usage with RTSP is defined
>     in Appendix D, which are two mandatory appendixes.
>
> I note that we should add F to this list.
>
> I think we should be clear in each of this appendices that if one
> support Foo for the purpose of bar then this appendix defines
> normatively how one does it.
Makes my head swim, but maybe it's must me.

fwiw - I'm still worried that there are information in Appendix B that's 
not captured in the main text, but I can't find easy things to point to. 
Elwyn seems more comfortable that everything is covered.
>
>
>> Section 15 talks about a "transparent' proxy, but there is no
>> description in this document of what protocol such a thing should
>> follow. What bad thing happens if you remove all mention of
>> "transparent" proxies from the document? As far as I can tell, that
>> won't affect the protocol definition at all.
> Not really, there is no definition of transparent proxies currently.
> There is one security concern that make require some word smithing if we
> remove transparent proxies.
>
> >From my perspective a transparent proxy is something that hijacks a TCP
> connection towards an RTSP server to be a proxy between client and
> server. Further is not detectable from the client's or the servers
> perspective, but still may modify RTSP messages within the bounds of the
> RTSP protocol.
>
> But, in reality as we have proxies that are visible we should focus on
> those and forget this bastard version.
>
>> The list of steps for establishing an SRTP cryptographic context in
>> C.1.4.1 says "This specification does not specify an explicit method for
>> indicating this SRTP cryptographic context establishment method, but
>> future specifications may." in the context of looking at the SDP. SDP
>> _has_ methods of indicating what keying mechanism is used with SRTP -
>> are you talking about something different?
> I think you are considering the methods for keying SRTP that are
> Offer/Answer dependent. The only RTSP SDP using method that exist is the
> one defined in RFC 4567, which we are explicit on not using.
>
> Why doesn't this section say
>> something like "the use of SRTP with RTSP is only defined with MIKEY
>> with keys established as defined in this section. Future documents may
>> talk about how an RTSP implementation might treat SDP that indicates
>> some other key mechanism be used"?
> Yes, that is appears better, but we will have to make it clear that is
> is regarding RTSP 2.0. Must also think if RFC 4567 needs to be worked
> into that sentence.
>
> Could you provide an example in the
>> document of an RTSP message carrying SDP reflecting the use of SRTP as
>> defined in this document?
> The point is that the only difference is that he RTP profile is SAVP/RTP
> or SAVPF/RTP in the SDP. Thus making such an SDP isn't difficult.
> Question is if it provides a benefit?
I think it would be worth the extra space it would take up.
>
>
>
>> Minor Issues
>>
>> The document uses the notion of a "control connection" (it appears first
>> in section 2.5) without defining what that is, or what kind of
>> connections you might have that aren't control connections.
> The "control connection" is the connection established for sending RTSP
> messages on it. I agree it is undefined and could likely be replaced by
> the "RTSP connection" or "connection for RTSP messages"
>
>> The update to the registration of the rtsp and rtsps schema call out
>> that there are changes that can result in interoperability issues. It
>> doesn't say what the issues are, or who might encounter them. I can
>> infer that the point is that there might be problems if a URI following
>> this updated registration were to be processed by an RTSP 1.0
>> implementation (or any other application that relied on the previous
>> definition). It would be better to say that explicitly, and talk about
>> how a previous implementation is likely to act when presented with a URI
>> that exercised these new changes.
> I have gotten these comment elsewhere and have prepared a text update
> for section 4.2:
>
>     The details of the syntax of "rtsp" and "rtsps" URIs has been changed
>     from RTSP 1.0.  These changes are:
>
>     o  Support for IPV6 literal in host part and future IP literals
>        through RFC 3986 defined mechanism.
>
>     o  A new relative format to use in the RTSP protocol elements that is
>        not required to start with "/".
>
>     Neither should have any significant impact on interoperability.  If
>     one is required to use IPv6 literals to reach an RTSP server, then
>     that RTSP server must be IPv6 capable, and RTSP 1.0 is not a fully
>     IPv6 capable protocol.  If an RTSP 1.0 client attempts to process the
>     URI it will not match the allowed syntax and be considered invalid
>     and processing will be stopped.  This is clearly a failure to reach
>     the resource, however it is not a signification issue as RTSP 2.0
>     support was needed anyway in both server and client.  Thus failure
>     will only occur in a later step when there is a RTSP version
>     mismatch between client and server.  The second change will only
>     occur in RTSP messages, that are explicitly identified as being RTSP
>     2.0 messages, thus a RTSP 1.0 only agent will not be required to
>     parse this variant.
>
> Clear enough?
Maybe. In the last sentence, are you saying you would never see a relative
URL in a request URI? If you're not already saying that explicitly in 
the document
(you might be) please consider doing so. Saying it that way in this text 
would
also help.
>
> The above is Edited In.
>
>   (It's not clear to me that all of the
>> thread at www.ietf.org—msg01567.html
>> <http://www.ietf.org/mail-archive/web/uri-review/current/msg01567.html>
>> concluded - I see how the fragments question ended, but what about
>> things like the addition of IPV6 literals? In particular, I'm not
>> finding a response where Ted Hardie agreed that the potential for
>> interoperability failure had been adequately addressed).
> I talked to him in person about this just after the discussion to better
> understand his comments. If we want a confirmation I think we need to
> loop him into a discussion regarding this particular issue.
I suggest the shepherd/AD double-check with him if he doesn't jump into 
this thread before.
>
> I provided a clarification to the designated URI reviewer which accepted
> the request.
>
>>
>> I think you've said something different than you mean in 5.4 item 1. I
>> think you mean to say that an RTSP implementation would ignore any body
>> that happened to come in message that MUST NOT contain one. What you've
>> said is that the part of the parser that's doing framing has to stop
>> framing at the end of the headers, and that such an errant body would be
>> parsed as a separate message. As written this would keep someone from
>> using an Internet Message Format parser since it would have to ignore
>> any Content-Length that might have appeared, even though it wasn't
>> supposed to.
> Yes, it is clearly sufficient to ignore the body, and likely much better
> from an error handling consideration.
>
> We will propose a text change.
>
>
>> In section 10.4, it looks like a server can keep an RTSP transaction
>> pending forever if it sends 100 responses often enough. I assume the
>> client's recourse if it doesn't want to remain involved is to close the
>> connection. If that's right, it's worth calling it out explicitly in
>> this section.
> This is likely a good suggestion, and works fine if the client simply
> wants to abort the request and is anyway abandoning the RTSP session.
> However, the question is what to do if just the request becomes
> irrelevant and instead want to do something else with the RTSP session.
> A single client may abandon the connection, open a new one and issue a
> request, to a potentially undetermined session state. Yet another
> complexity is what a proxy does that has multiple RTSP sessions on the
> same server. Here the rules for processing in order the different
> requests and their relation to answers in the same order.
>
> This makes me want to weaken the recommendation on re-using an
> connection for multiple RTSP sessions.
Are there also considerations here wrt pipelining?
>
>
>> Somewhere, probably in section 15.2, you should be explicit that a proxy
>> that is multiplexing requests MUST keep the requests in the same order
>> as they are folded together. You can infer that, or things simply break,
>> but saying it explicitly would be better.
> Probably, as a clarification to what is already present in section 18.19
> (CSeq header)
>
>     Proxies that aggregate several sessions on the same transport will
>     have to ensure that the requests sent towards a particular server
>     have a joint sequence number space, i.e., they will regularly need to
>     renumber the CSeq header field in requests (from proxy to server) and
>     responses (from server to proxy) to fulfill the rules for the header.
>     The proxy MUST increase the CSeq by one for each request it
>     transmits, without regard of different sessions.
>
>
>> Both GET_PARAMETER and SET_PARAMETER are listed as keep-alive methods in
>> 10.5, but the note in section 13 on table 7 only uses that as a reason
>> for requiring SET_PARAMETER. Why doesn't it also apply to GET_PARAMETER?
>> And why is this only required at servers? "Required" in this section
>> means Mandatory to Implement, I think. If that's right, it should be
>> made explicit. If that's not right, what does it mean?
> Yes, required is Required to implement in the server. The GET_PARAMETER
> is not required as only one method for keep-alive is necessary. Thus,
> the ones that needs to use GET/SET_PARAMETER for keep-alive will have to
> choose SET_PARAMETER.
>
> It is only required at the server, as it is in the client implementation
> choice of how to ensure keep-alive works. As this is also dependent on
> the media transport support one has, the client may not need a method
> based keep-alive.
>
> Clarifying "Required" should be straightforward.
>
>> Section 13.8 makes a good argument for always putting parameters to be
>> retrieved in a body. Why are you keeping the complexity of also allowing
>> them in headers?
> Some arguments are probably lost in the passage of time. However, the
> headers specified to be suitable for inclusion in a GET_PARAMETER
> requests are used for providing these information also in other methods,
> thus we have not wanted to duplicate the representation of this
> information in both a body and a header form.
>
>> Section 13.10: "That should not provide any benefit." is not clear - can
>> you expand it a little?
>     If the REDIRECT request times out following the rules in Section 10.4
>     the server MAY terminate the session or transport connection that
>     would be redirected by the request.  This is a safeguard against
>     misbehaving clients that refuse to respond to a REDIRECT request.
>     That should not provide any benefit.
>
> The intention here is to make clear that there shouldn't be an incentive
> in the protocol to not acknowledge a REDIRECT request and instead simply
> go on as it wasn't received or seen. Thus, we want to make clear that
> the server may simply terminate the session in those cases.
>
> I propose we change this sentence to:
>
> Thus, removing any incentive to not acknowledge the reception of a
> REDIRECT request.
>
> Edited In
>
>> In Section 13.10 you talk about clients _sending_ media (search for
>> "send or receive media"). Do you mean anything more than possibly RTCP?
>> Can you make that clear in the section?
> You mean this sentence:
>
>     After a REDIRECT request has been processed, a client that wants to
>     continue to send or receive media for the resource identified by the
>     Request-URI will have to establish a new session with the designated
>     host.
>
> The mentioning of send media is likely a RECORD reference. In this case
> I don't see any issue with removing it.
>
> Edited In
>
>> Section 15.2's second paragraph appears to be the only place the proxy
>> rewriting of CSeq in order to multiplex requests is defined, and it is
>> very loose. It would be easy for a reader to fail to recognize this as
>> an interoperability requirement. Please consider expanding how this is
>> specified when addressing the comment about above about keeping requests
>> in relative order when multiplexing.
> There are text in Section 18.19 CSeq also. But I do think I agree that
> this should be clarified.
>
>> You follow the principle of saying a client should treat a response with
>> an unknown response code, the same as it would treat the x00 of that
>> class (e.g. 400 for an unknown 4xx). However, you do not define what a
>> response code of 300 means. How is a client supposed to handle an
>> unknown 3xx response?
> Sorry, I don't quite get this comment. Section 17.3 says:
>
>     If a 3rr response is received for a request in relation to
>     an established session, the client SHOULD send a TEARDOWN request for
>     the session, and MAY reestablish the session using the resource
>     indicated by the Location.
>
>     If the Location header is used in a response it MUST contain an
>     absolute URI pointing out the media resource the client is redirected
>     to, the URI MUST NOT only contain the host name.
>
> As explained above unknown 3XX codes will be 3rr codes, as 304 isn't
> unknown.
>
> If you don't believe this is sufficient can you please be more explicit
> about the issue?
Sure. It might be quickest if you look at the table of contents.
Note that you define 100 in 17.1.1, 200 in 17.2.1, 400 in 17.4.1, 500 in 
17.5.1, but you do not define 300 anywhere - you jump straight to 301.
Please add a section defining it, or declaring that you will never see a 
literal 300 on the wire, but if you did you would do (what you quote 
above) and nothing else.

>
>> As written, a client and server can use HTTP Basic authentication over
>> TCP that is not protected with TLS. Consider restricting it's use to TLS
>> only. Are you sure you don't need to say anything RTSP specific about
>> DIGEST computations (I don't think you need to go as far as SIP did
>> talking about DIGEST, but I'm surprised you haven't run into issues
>> relying only on 2617 literally.
> Are you referring to Section 19.1 here?
Yes
>
> Yes, I would not have any issue with requiring Basic to be combined with
> TLS. I think that is appropriate.
>
> When it comes to DIGEST, are you referring to section 22.4 in RFC 3261?
Yes
>
> That section indicates that some clarifications are likely needed.
>
>>
>> How does 411 Length Required for this protocol make sense? Given that
>> you've restricted the protocol to TCP and require the Content-Length
>> header to be present if there is a body, in what circumstance would a
>> server need to send a 411?
> It really should occur for malformed messages, which we could use 400 as
> response. So yes, 411 could be removed.
>
>>
>> Section 18.19 requires senders to increment CSeq by 1. We have a
>> reliable transport with no request retransmission, so there should never
>> be gaps at the receiver. Should the receiver check and react some way if
>> there are gaps? I think you should explicitly tell them not to even
>> look. If you agree, why is incrementing by one important as long as you
>> are always strictly increasing?
> I agree that for TCP or other reliable transports the receiver
> SHOULD/SHALL ignore gaps. For any future specification of an unreliable
> transport of RTSP messages this would be needed. As noted in Appendix G,
> CSeq is retained for future support of unreliable transport.
>
>> You call out several places where RTCP is essential to allow RTSP using
>> RTP to work correctly, yet section C.1.2 sets up conditions where RTCP
>> MUST NOT be sent. Why are you allowing those instead of treating the
>> conditions you describe as errors?
> Good question. I think it is a case we must ensure that you can
> negotiate and configure your desired way, without really considering if
> it should be allowed at all. I think mandating usage of RTCP with RTP
> for RTSP 2.0 would be good. But, I think that needs to be verified with
> the WG.
Ack
>
> cheers
>
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>


From david.black@emc.com  Tue Jun 18 07:43:47 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF5911E80DF; Tue, 18 Jun 2013 07:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AOw19EIogZJb; Tue, 18 Jun 2013 07:43:42 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 427E321E8053; Tue, 18 Jun 2013 07:43:38 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IEhaPN032387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jun 2013 10:43:37 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 18 Jun 2013 10:43:06 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IEh5dK006895; Tue, 18 Jun 2013 10:43:05 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Tue, 18 Jun 2013 10:43:05 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans@painless-security.com>
Date: Tue, 18 Jun 2013 10:43:03 -0400
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5sLtL2MQaEvFULRLupG53n6IyQQgAAT1zw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129826522D@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu>
In-Reply-To: <tsl38sfbiyd.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "jsalowey@cisco.com" <jsalowey@cisco.com>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 14:43:47 -0000

Sam,

I was concerned that something along these lines was lurking in here :-(.

I think this is the crucial "running code" consideration to start from:

> Practically speaking, it will be a while before peers implement channel
> binding for network access.

Assuming that network access does not use channel binding, how does one
avoid the proxy attack on network access authentication via application
access authentication when the latter is introduced?

For environments where EAP is used for network access authentication,
the suggestion of a "MUST use" requirement for channel binding with=20
application access authentication sounds like the right approach:

> If all the application access peers support channel binding, then you
> could potentially require the eap-lower-layer attribute or similar for
> application authentication and work securely in environments where peers
> for network access have not been updated yet.

Is that plausible and reasonable in practice?

This would be in addition to the "MUST implement" requirements for AAA
servers, EAP serves and peers doing application access:

> I know you're correct that AAA servers and EAP servers need to implement
> channel binding for network access in such environments.

Thanks,
--David


> -----Original Message-----
> From: Sam Hartman [mailto:hartmans@painless-security.com]
> Sent: Tuesday, June 18, 2013 10:19 AM
> To: Black, David
> Cc: stefan.winter@restena.lu; jsalowey@cisco.com; General Area Review Tea=
m;
> abfab@ietf.org; ietf@ietf.org
> Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-=
03
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>     Black,> The next to last paragraph on p.3 begins with this sentence:
>=20
>     Black,>    For these reasons, channel binding MUST be implemented by
>     Black,> peers, EAP servers and AAA servers in environments where EAP
>     Black,> authentication is used to access application layer services.
>=20
>     Black,> It appear that this "MUST" requirement applies to all uses
>     Black,> of EAP, including network access authentication, not just
>     Black,> application layer access authentication.  If so, that's not
>     Black,> immediately obvious from the text, and an additional
>     Black,> sentence should be added to make this clearer.  If not, the
>     Black,> above sentence needs to exclude network access
>     Black,> authentication from that requirement.
>=20
>=20
> I know you're correct that AAA servers and EAP servers need to implement
> channel binding for network access in such environments.
> I'm not sure whether peers only doing network access SHOULD implement
> channel binding or MUST implement channel binding.
>=20
> Practically speaking, it will be a while before peers implement channel
> binding for network access.
> The sorts of attacks that result without channel binding are attacks
> where a peer thinks it is doing network access authentication but what
> it's really doing is helping an attacker access an application.
> If all the application access peers support channel binding, then you
> could potentially require the eap-lower-layer attribute or similar for
> application authentication and work securely in environments where peers
> for network access have not been updated yet.
> It's also kind of tempting to stick our head in the sand and just add
> the clarification that "yes, we mean network access too."
>=20
> --Sam


From jsalowey@cisco.com  Tue Jun 18 10:10:26 2013
Return-Path: <jsalowey@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E8611E80F0; Tue, 18 Jun 2013 10:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjsZs7F81wtv; Tue, 18 Jun 2013 10:10:21 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id AEC3921F9B7D; Tue, 18 Jun 2013 10:10:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3564; q=dns/txt; s=iport; t=1371575421; x=1372785021; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+hlGh+C++SrXDUQzquKhgpIyxvVI+lyR41mFbWx3p6c=; b=gfzZQRI498ui8ajAaKuqPEDxRMrYTYCIBzj/rw9Irytkm90faOGjIf5B HjIX8Y5eewwOL3Q0Kb5OhVBKlZOYJgyQxVOgXON/h/OpS4TqYPC7kApuo vzBHWMz5JXYkKJuAWQBwpw9obPjZfu9QTvfMnj1nb/uAWEa+msI9ueyBS c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAAaUwFGtJXG//2dsb2JhbABPCoMJer8PgQIWdIIjAQEBAwE6PwULAgEIIhQQMiUBAQQOBQiIAAa7Eo1/gQkCMQeDAGEDqQSDD4FqJBo
X-IronPort-AV: E=Sophos;i="4.87,890,1363132800"; d="scan'208";a="224374188"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 18 Jun 2013 17:10:20 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5IHAKcY000945 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 17:10:20 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Tue, 18 Jun 2013 12:10:19 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Sam Hartman <hartmans@painless-security.com>
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQA=
Date: Tue, 18 Jun 2013 17:10:19 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu>
In-Reply-To: <tsl38sfbiyd.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4F7AA199DE677B4EBAFAEF02DB1C2F7F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "abfab@ietf.org" <abfab@ietf.org>, "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 17:10:26 -0000

On Jun 18, 2013, at 7:18 AM, Sam Hartman <hartmans@painless-security.com>
 wrote:

>>>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>    Black,> The next to last paragraph on p.3 begins with this sentence:
>=20
>    Black,>    For these reasons, channel binding MUST be implemented by
>    Black,> peers, EAP servers and AAA servers in environments where EAP
>    Black,> authentication is used to access application layer services.
>=20
>    Black,> It appear that this "MUST" requirement applies to all uses
>    Black,> of EAP, including network access authentication, not just
>    Black,> application layer access authentication.  If so, that's not
>    Black,> immediately obvious from the text, and an additional
>    Black,> sentence should be added to make this clearer.  If not, the
>    Black,> above sentence needs to exclude network access
>    Black,> authentication from that requirement.
>=20
>=20
> I know you're correct that AAA servers and EAP servers need to implement
> channel binding for network access in such environments.
> I'm not sure whether peers only doing network access SHOULD implement
> channel binding or MUST implement channel binding.
>=20
> Practically speaking, it will be a while before peers implement channel
> binding for network access.
> The sorts of attacks that result without channel binding are attacks
> where a peer thinks it is doing network access authentication but what
> it's really doing is helping an attacker access an application.
> If all the application access peers support channel binding, then you
> could potentially require the eap-lower-layer attribute or similar for
> application authentication and work securely in environments where peers
> for network access have not been updated yet.

[Joe]  I'm trying to get a handle on the attack mechanism here.   In this a=
ttack a valid network service is trying to spoof an application service?  S=
ince it knows the MSK it can do this if the channel-binding of the lower-la=
yer into the EAP conversation is not enforced.  If the AAA server always en=
forces channel bindings for applications then it will catch the spoofing at=
tempt.   The reverse case may also be an issue where an application service=
 is trying to spoof a network service.   In this case, if the AAA server va=
lidates that the application channel binding is not present then it can pre=
vent the spoofing.  However the server MUST understand channel bindings eve=
n if the peers do not.   I think the document did try to capture this in th=
e following sentence:

"If the EAP server is aware that authentication is
   for something other than a network service, it too MUST default to
   requiring channel binding."

I think we could state this a bit better as something like:

"In environments where EAP is used for applications authentication and netw=
ork access authentication all EAP servers MUST understand channel bindings =
and require that application bindings MUST be present in application authen=
tication and that application bindings MUST be absent in network authentica=
tion.   All network access EAP peer implementations SHOULD support channel =
binding to explicitly identify the reason for authentication.  Any new usag=
e of EAP MUST support channel bindings to prevent confusion with network ac=
cess usage. "=20



> It's also kind of tempting to stick our head in the sand and just add
> the clarification that "yes, we mean network access too."
>=20
> --Sam


From david.black@emc.com  Tue Jun 18 10:28:44 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C5811E80E3; Tue, 18 Jun 2013 10:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFsFab+5vvBv; Tue, 18 Jun 2013 10:28:39 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4725111E80E6; Tue, 18 Jun 2013 10:28:38 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IHSaXR016150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jun 2013 13:28:37 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Tue, 18 Jun 2013 13:28:19 -0400
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IHSIKd002504; Tue, 18 Jun 2013 13:28:18 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Tue, 18 Jun 2013 13:28:17 -0400
From: "Black, David" <david.black@emc.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Date: Tue, 18 Jun 2013 13:28:17 -0400
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4A==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com>
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 17:28:44 -0000

> [Joe]  I'm trying to get a handle on the attack mechanism here.   In this
> attack a valid network service is trying to spoof an application service?
> Since it knows the MSK it can do this if the channel-binding of the lower=
-
> layer into the EAP conversation is not enforced.  If the AAA server alway=
s
> enforces channel bindings for applications then it will catch the spoofin=
g
> attempt.   The reverse case may also be an issue where an application ser=
vice
> is trying to spoof a network service.

While both cases appear to be relevant, my concern started from the reverse
case - here's the draft's text describing the attack:

   One
   potentially serious attack exists when channel binding is not
   required and EAP authentication is introduced into an existing non-
   network service.  A device can be created that impersonates a Network
   Access Service to peers, but actually proxies the authentication to
   the new application service that accepts EAP authentications.  This
   may decrease the security of this service even for users who
   previously used non-EAP means of authentication to the service.

> In this case, if the AAA server
> validates that the application channel binding is not present then it can
> prevent the spoofing.  However the server MUST understand channel binding=
s
> even if the peers do not.   I think the document did try to capture this =
in
> the following sentence:
>=20
> "If the EAP server is aware that authentication is
>    for something other than a network service, it too MUST default to
>    requiring channel binding."
>=20
> I think we could state this a bit better as something like:
>=20
> "In environments where EAP is used for applications authentication and ne=
twork
> access authentication all EAP servers MUST understand channel bindings an=
d
> require that application bindings MUST be present in application
> authentication and that application bindings MUST be absent in network
> authentication.   All network access EAP peer implementations SHOULD supp=
ort
> channel binding to explicitly identify the reason for authentication.  An=
y new
> usage of EAP MUST support channel bindings to prevent confusion with netw=
ork
> access usage. "

That text is an improvement, and it's headed in the same direction as Sam's
comment - "application bindings MUST be present in application authenticati=
on"
is a "MUST use" requirement, not just a "MUST implement" requirement.

OTOH, I'm not clear on what "application bindings" means, as that term's no=
t
in the current draft.  Specifically, I'm a bit unclear on "application bind=
ings
MUST be absent in network authentication" - does that mean that channel
binding must be absent, or that channel binding is optional, but if channel
binding is present, it MUST NOT be an "application binding", whatever that =
is?

Thanks,
--David

> -----Original Message-----
> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
> Sent: Tuesday, June 18, 2013 1:10 PM
> To: Sam Hartman
> Cc: Black, David; stefan.winter@restena.lu; General Area Review Team;
> abfab@ietf.org; ietf@ietf.org
> Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-=
03
>=20
>=20
> On Jun 18, 2013, at 7:18 AM, Sam Hartman <hartmans@painless-security.com>
>  wrote:
>=20
> >>>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
> >
> >    Black,> The next to last paragraph on p.3 begins with this sentence:
> >
> >    Black,>    For these reasons, channel binding MUST be implemented by
> >    Black,> peers, EAP servers and AAA servers in environments where EAP
> >    Black,> authentication is used to access application layer services.
> >
> >    Black,> It appear that this "MUST" requirement applies to all uses
> >    Black,> of EAP, including network access authentication, not just
> >    Black,> application layer access authentication.  If so, that's not
> >    Black,> immediately obvious from the text, and an additional
> >    Black,> sentence should be added to make this clearer.  If not, the
> >    Black,> above sentence needs to exclude network access
> >    Black,> authentication from that requirement.
> >
> >
> > I know you're correct that AAA servers and EAP servers need to implemen=
t
> > channel binding for network access in such environments.
> > I'm not sure whether peers only doing network access SHOULD implement
> > channel binding or MUST implement channel binding.
> >
> > Practically speaking, it will be a while before peers implement channel
> > binding for network access.
> > The sorts of attacks that result without channel binding are attacks
> > where a peer thinks it is doing network access authentication but what
> > it's really doing is helping an attacker access an application.
> > If all the application access peers support channel binding, then you
> > could potentially require the eap-lower-layer attribute or similar for
> > application authentication and work securely in environments where peer=
s
> > for network access have not been updated yet.
>=20
> [Joe]  I'm trying to get a handle on the attack mechanism here.   In this
> attack a valid network service is trying to spoof an application service?
> Since it knows the MSK it can do this if the channel-binding of the lower=
-
> layer into the EAP conversation is not enforced.  If the AAA server alway=
s
> enforces channel bindings for applications then it will catch the spoofin=
g
> attempt.   The reverse case may also be an issue where an application ser=
vice
> is trying to spoof a network service.   In this case, if the AAA server
> validates that the application channel binding is not present then it can
> prevent the spoofing.  However the server MUST understand channel binding=
s
> even if the peers do not.   I think the document did try to capture this =
in
> the following sentence:
>=20
> "If the EAP server is aware that authentication is
>    for something other than a network service, it too MUST default to
>    requiring channel binding."
>=20
> I think we could state this a bit better as something like:
>=20
> "In environments where EAP is used for applications authentication and ne=
twork
> access authentication all EAP servers MUST understand channel bindings an=
d
> require that application bindings MUST be present in application
> authentication and that application bindings MUST be absent in network
> authentication.   All network access EAP peer implementations SHOULD supp=
ort
> channel binding to explicitly identify the reason for authentication.  An=
y new
> usage of EAP MUST support channel bindings to prevent confusion with netw=
ork
> access usage. "
>=20
>=20
>=20
> > It's also kind of tempting to stick our head in the sand and just add
> > the clarification that "yes, we mean network access too."
> >
> > --Sam
>=20


From jsalowey@cisco.com  Tue Jun 18 10:47:10 2013
Return-Path: <jsalowey@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9523A11E80DF; Tue, 18 Jun 2013 10:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRUCxIPRbfch; Tue, 18 Jun 2013 10:47:05 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id E391C11E80EC; Tue, 18 Jun 2013 10:47:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2198; q=dns/txt; s=iport; t=1371577625; x=1372787225; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Tl0W1XPlBj7Q7T8U4EZPVfIrpXaWB8G9FYDbLyRLqJI=; b=cZvKpaWkdEdheb+GuYb9/qy3lsQVZaaLVXj3eSSn3Hw+I37mNtYzLHxo NXMu5jlhPexVFY2tLTsZIlCdzuUA5yRaZDZb7S1vY1dO11A3Rglkyfptn 2H9TWvQGiFQNm6cd/oc58A2Q+wWE9OT2NQ9Bcn2nE4nXtIDtcun2ixFAS U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FALecwFGtJV2d/2dsb2JhbABPCoMJer8PgQIWdIIkAQEEOj8QAgEIIhQQMiUBAQQODYgGuwuNf4EJAjEHgwBhA6kEgw+CKA
X-IronPort-AV: E=Sophos;i="4.87,890,1363132800"; d="scan'208";a="224169702"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 18 Jun 2013 17:47:04 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r5IHl4iY016128 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 17:47:04 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Tue, 18 Jun 2013 12:47:04 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GA
Date: Tue, 18 Jun 2013 17:47:03 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6D250E7F34578C4DB2BC1DE691351E73@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 17:47:10 -0000

>>=20
>> I think we could state this a bit better as something like:
>>=20
>> "In environments where EAP is used for applications authentication and n=
etwork
>> access authentication all EAP servers MUST understand channel bindings a=
nd
>> require that application bindings MUST be present in application
>> authentication and that application bindings MUST be absent in network
>> authentication.   All network access EAP peer implementations SHOULD sup=
port
>> channel binding to explicitly identify the reason for authentication.  A=
ny new
>> usage of EAP MUST support channel bindings to prevent confusion with net=
work
>> access usage. "
>=20
> That text is an improvement, and it's headed in the same direction as Sam=
's
> comment - "application bindings MUST be present in application authentica=
tion"
> is a "MUST use" requirement, not just a "MUST implement" requirement.
>=20
> OTOH, I'm not clear on what "application bindings" means, as that term's =
not
> in the current draft.  Specifically, I'm a bit unclear on "application bi=
ndings
> MUST be absent in network authentication" - does that mean that channel
> binding must be absent, or that channel binding is optional, but if chann=
el
> binding is present, it MUST NOT be an "application binding", whatever tha=
t is?
>=20

[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access a=
uthentication all EAP servers MUST enforce channel bindings.  For applicati=
on authentication, the EAP server MUST require that the correct EAP lower-l=
ayer attribute be present in the channel binding data.   For network access=
 authentication, the EAP server MUST require that if channel bindings are p=
resent they MUST contain the correct EAP lower-layer attribute.   All netwo=
rk access EAP peer implementations SHOULD use channel bindings including th=
e EAP lower-layer attribute to explicitly identify the reason for authentic=
ation.  Any new usage of EAP MUST use channel bindings including the EAP lo=
wer-layer attribute to prevent confusion with network access usage. "

Does this help?

Thanks,

Joe


From hartmans@painless-security.com  Tue Jun 18 11:39:23 2013
Return-Path: <hartmans@painless-security.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D58BD11E80F7; Tue, 18 Jun 2013 11:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvRUC7f+lfIX; Tue, 18 Jun 2013 11:39:18 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id A88AE11E80F8; Tue, 18 Jun 2013 11:39:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 36D902013A; Tue, 18 Jun 2013 14:35:24 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAFbtdoguduW; Tue, 18 Jun 2013 14:35:23 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 18 Jun 2013 14:35:23 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2DA9980047; Tue, 18 Jun 2013 14:39:05 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
Date: Tue, 18 Jun 2013 14:39:05 -0400
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> (Joseph Salowey's message of "Tue, 18 Jun 2013 17:47:03 +0000")
Message-ID: <tsl38sf9sc6.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "abfab@ietf.org" <abfab@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 18:39:24 -0000

Joe, eap-lower-layer is not required for application authentication if
there's some other attribute that's specific to the lower layer.  For
example Moonshot sends gss-acceptor-service-name but does not currently
send eap-lower-layer, and doing that seems consistent with the
requirements of the channel binding spec.

Adding a requirement for eap-lower-layer all the time would be new, but
might be reasonable.

--Sam

From david.black@emc.com  Tue Jun 18 12:35:26 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74DA421E80C1; Tue, 18 Jun 2013 12:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwUFxhG5gcMO; Tue, 18 Jun 2013 12:35:21 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5A18B21E80C0; Tue, 18 Jun 2013 12:35:17 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IJZGCe028823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jun 2013 15:35:16 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 18 Jun 2013 15:34:57 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5IJYhuw023324; Tue, 18 Jun 2013 15:34:55 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Tue, 18 Jun 2013 15:34:45 -0400
From: "Black, David" <david.black@emc.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Date: Tue, 18 Jun 2013 15:34:44 -0400
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GAgAA80uA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 19:35:26 -0000

> [Joe] Good points, the text can be more specific:
>=20
> "In environments where EAP is used for purposes other than network access
> authentication all EAP servers MUST enforce channel bindings.  For applic=
ation
> authentication, the EAP server MUST require that the correct EAP lower-la=
yer
> attribute be present in the channel binding data.   For network access
> authentication, the EAP server MUST require that if channel bindings are
> present they MUST contain the correct EAP lower-layer attribute.   All ne=
twork
> access EAP peer implementations SHOULD use channel bindings including the=
 EAP
> lower-layer attribute to explicitly identify the reason for authenticatio=
n.
> Any new usage of EAP MUST use channel bindings including the EAP lower-la=
yer
> attribute to prevent confusion with network access usage. "

This is looking good, modulo Sam's comment on EAP lower-layer vs. something
else that I'll leave to you and he to sort out.  I have a suggested rewrite=
,
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and
to reformat into a structured bullet list of requirements (this is not
intended to change any requirements from what you wrote):

"In environments where EAP is used for purposes other than network access
authentication:

	o All EAP servers and all application access EAP peers MUST
		support channel bindings.  All network access EAP peers
		SHOULD support channel bindings.

	o Channel binding MUST be used for all application authentication.
		The EAP server MUST require that the correct EAP lower-layer
		attribute be present in the channel binding data for
		application authentication.

	o Channel binding SHOULD be used for all network access authentication,
		and when channel binding data is present, the EAP server MUST
		require that it contain the correct EAP lower-layer attribute
		to explicitly identify the reason for authentication.

	o Any new usage of EAP MUST use channel bindings including the
		EAP lower-layer attribute to prevent confusion with network
		access usage."

Thanks,
--David


> -----Original Message-----
> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
> Sent: Tuesday, June 18, 2013 1:47 PM
> To: Black, David
> Cc: stefan.winter@restena.lu; General Area Review Team; abfab@ietf.org;
> ietf@ietf.org
> Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-=
03
>=20
> >>
> >> I think we could state this a bit better as something like:
> >>
> >> "In environments where EAP is used for applications authentication and=
 network
> >> access authentication all EAP servers MUST understand channel bindings=
 and
> >> require that application bindings MUST be present in application
> >> authentication and that application bindings MUST be absent in network
> >> authentication.   All network access EAP peer implementations SHOULD s=
upport
> >> channel binding to explicitly identify the reason for authentication. =
 Any new
> >> usage of EAP MUST support channel bindings to prevent confusion with n=
etwork
> >> access usage. "
> >
> > That text is an improvement, and it's headed in the same direction as S=
am's
> > comment - "application bindings MUST be present in application authenti=
cation"
> > is a "MUST use" requirement, not just a "MUST implement" requirement.
> >
> > OTOH, I'm not clear on what "application bindings" means, as that term'=
s not
> > in the current draft.  Specifically, I'm a bit unclear on "application =
bindings
> > MUST be absent in network authentication" - does that mean that channel
> > binding must be absent, or that channel binding is optional, but if cha=
nnel
> > binding is present, it MUST NOT be an "application binding", whatever t=
hat
> is?
> >
>=20
> [Joe] Good points, the text can be more specific:
>=20
> "In environments where EAP is used for purposes other than network access
> authentication all EAP servers MUST enforce channel bindings.  For applic=
ation
> authentication, the EAP server MUST require that the correct EAP lower-la=
yer
> attribute be present in the channel binding data.   For network access
> authentication, the EAP server MUST require that if channel bindings are
> present they MUST contain the correct EAP lower-layer attribute.   All ne=
twork
> access EAP peer implementations SHOULD use channel bindings including the=
 EAP
> lower-layer attribute to explicitly identify the reason for authenticatio=
n.
> Any new usage of EAP MUST use channel bindings including the EAP lower-la=
yer
> attribute to prevent confusion with network access usage. "
>=20
> Does this help?
>=20
> Thanks,
>=20
> Joe
>=20


From jsalowey@cisco.com  Tue Jun 18 13:00:26 2013
Return-Path: <jsalowey@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C373021E80B6; Tue, 18 Jun 2013 13:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gr57FFocfblg; Tue, 18 Jun 2013 13:00:20 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id DE6D921E80BD; Tue, 18 Jun 2013 13:00:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=868; q=dns/txt; s=iport; t=1371585620; x=1372795220; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eB/jRNm4UWz/7giJ74P44658v9HNsMtyBDBq+TrXiwM=; b=fhA1BWL/N24VkIc2NpKZ1I1UCQWOE7NnH0BjelSKH0U4FPGh91MolZKp ep8B7XujsZ9rA6TgXNeVWZvNafK9Y5nB8TReZ6chOrjolQcXpSbOSQwL2 egt1ykf1chuVSiNydT1cXq17JGr6Z0VALC6Up8cyOtgUQusPHtfMBs3Ht Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4FACS7wFGtJXHA/2dsb2JhbABZgwl6gjq8VYEEFnSCIwEBAQMBOj8FCwIBCCIUEDIlAgQOBQiIAAa6fI8IAjEHgwBhA6kEgw+BaAc5
X-IronPort-AV: E=Sophos;i="4.87,891,1363132800"; d="scan'208";a="224230285"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 18 Jun 2013 20:00:19 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5IK0J4d013814 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 20:00:19 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Tue, 18 Jun 2013 15:00:18 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Sam Hartman <hartmans@painless-security.com>
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: AQHObFMc5Vr98eb9RParuraCHgwUcpk8OBOA
Date: Tue, 18 Jun 2013 20:00:17 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628CFBE45@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <tsl38sf9sc6.fsf@mit.edu>
In-Reply-To: <tsl38sf9sc6.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3E45AE4402E8FD46832FA550ED86D443@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "abfab@ietf.org" <abfab@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 20:00:26 -0000

On Jun 18, 2013, at 11:39 AM, Sam Hartman <hartmans@painless-security.com>
 wrote:

> Joe, eap-lower-layer is not required for application authentication if
> there's some other attribute that's specific to the lower layer.  For
> example Moonshot sends gss-acceptor-service-name but does not currently
> send eap-lower-layer, and doing that seems consistent with the
> requirements of the channel binding spec.
>=20
> Adding a requirement for eap-lower-layer all the time would be new, but
> might be reasonable.
>=20

[Joe] Ah yes, I remember this.  It would be simpler to just use eap lower-l=
ayer attribute.  I think we could massage the text to say something like "e=
ap lower-layer layer attribute or equivalent attribute indicating the EAP l=
ower layer in use" .   Let me see what I can do with the text David provide=
d. =20


> --Sam


From jsalowey@cisco.com  Wed Jun 19 16:23:11 2013
Return-Path: <jsalowey@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10E3F21F9D69; Wed, 19 Jun 2013 16:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bS54rLKLBgZi; Wed, 19 Jun 2013 16:23:05 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 33D5421F9D5B; Wed, 19 Jun 2013 16:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14139; q=dns/txt; s=iport; t=1371684185; x=1372893785; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=UMC3pumKxAdqjVQNgYLKqxTstKU6qCVlVRhqL7fKB1c=; b=i7jhDQctPk04RQa/EoOYrd3s1HH0KfMP18GWAC+yWegrcz8xNKy0LEvq XF/kTlaaO1fItEBefrZcCNRmht503U6giqETf24B3WDXzkf+tHKdXXVIt 7UDQ4QkqBUyKJ9TkiTdN12sxymkJG5CHa8a0NUD1iKHYnlaOmYWocs8O5 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEFALY8wlGtJXHA/2dsb2JhbABQCoMJMUm2YYg6gQAWdIIjAQEBBHkMBAIBCBEEAQELHQcyFAkIAgQOBQiIBrwGjgaBCzEHBgOCd2EDmGqKeYUigw+CKA
X-IronPort-AV: E=Sophos;i="4.87,900,1363132800";  d="scan'208,217";a="225035286"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 19 Jun 2013 23:23:04 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5JNN4gd009359 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Jun 2013 23:23:04 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.004; Wed, 19 Jun 2013 18:23:04 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GAgAA80uCAAbNjgA==
Date: Wed, 19 Jun 2013 23:23:03 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.222]
Content-Type: multipart/alternative; boundary="_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_"
MIME-Version: 1.0
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 23:23:11 -0000

--_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the text,  some revision to address
On Jun 18, 2013, at 12:34 PM, "Black, David" <david.black@emc.com<mailto:da=
vid.black@emc.com>> wrote:

[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

This is looking good, modulo Sam's comment on EAP lower-layer vs. something
else that I'll leave to you and he to sort out.  I have a suggested rewrite=
,
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and
to reformat into a structured bullet list of requirements (this is not
intended to change any requirements from what you wrote):

"In environments where EAP is used for purposes other than network access
authentication:

o All EAP servers and all application access EAP peers MUST
support channel bindings.  All network access EAP peers
SHOULD support channel bindings.

o Channel binding MUST be used for all application authentication.
The EAP server MUST require that the correct EAP lower-layer
attribute be present in the channel binding data for
application authentication.

o Channel binding MUST be used for all application authentication.
The EAP server MUST either require that the correct EAP lower-layer
attribute or another attribute indicating the purpose of the authentication
be present in the channel binding data for application authentication.


o Channel binding SHOULD be used for all network access authentication,
and when channel binding data is present, the EAP server MUST
require that it contain the correct EAP lower-layer attribute
to explicitly identify the reason for authentication.

o Any new usage of EAP MUST use channel bindings including the
EAP lower-layer attribute to prevent confusion with network
access usage.

Thanks,
--David


-----Original Message-----
From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com<http://cisco.com=
>]
Sent: Tuesday, June 18, 2013 1:47 PM
To: Black, David
Cc: stefan.winter@restena.lu<mailto:stefan.winter@restena.lu>; General Area=
 Review Team; abfab@ietf.org<mailto:abfab@ietf.org>;
ietf@ietf.org<mailto:ietf@ietf.org>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03


I think we could state this a bit better as something like:

"In environments where EAP is used for applications authentication and netw=
ork
access authentication all EAP servers MUST understand channel bindings and
require that application bindings MUST be present in application
authentication and that application bindings MUST be absent in network
authentication.   All network access EAP peer implementations SHOULD suppor=
t
channel binding to explicitly identify the reason for authentication.  Any =
new
usage of EAP MUST support channel bindings to prevent confusion with networ=
k
access usage. "

That text is an improvement, and it's headed in the same direction as Sam's
comment - "application bindings MUST be present in application authenticati=
on"
is a "MUST use" requirement, not just a "MUST implement" requirement.

OTOH, I'm not clear on what "application bindings" means, as that term's no=
t
in the current draft.  Specifically, I'm a bit unclear on "application bind=
ings
MUST be absent in network authentication" - does that mean that channel
binding must be absent, or that channel binding is optional, but if channel
binding is present, it MUST NOT be an "application binding", whatever that
is?


[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

Does this help?

Thanks,

Joe




--_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <AA2F65A4081D814C84E2017D57A884DA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Thanks for the text, &nbsp;some revision to address&nbsp;<br>
<div>
<div>On Jun 18, 2013, at 12:34 PM, &quot;Black, David&quot; &lt;<a href=3D"=
mailto:david.black@emc.com">david.black@emc.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<blockquote type=3D"cite">[Joe] Good points, the text can be more specific:=
<br>
<br>
&quot;In environments where EAP is used for purposes other than network acc=
ess<br>
authentication all EAP servers MUST enforce channel bindings. &nbsp;For app=
lication<br>
authentication, the EAP server MUST require that the correct EAP lower-laye=
r<br>
attribute be present in the channel binding data. &nbsp;&nbsp;For network a=
ccess<br>
authentication, the EAP server MUST require that if channel bindings are<br=
>
present they MUST contain the correct EAP lower-layer attribute. &nbsp;&nbs=
p;All network<br>
access EAP peer implementations SHOULD use channel bindings including the E=
AP<br>
lower-layer attribute to explicitly identify the reason for authentication.=
<br>
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r<br>
attribute to prevent confusion with network access usage. &quot;<br>
</blockquote>
<br>
This is looking good, modulo Sam's comment on EAP lower-layer vs. something=
<br>
else that I'll leave to you and he to sort out. &nbsp;I have a suggested re=
write,<br>
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and<b=
r>
to reformat into a structured bullet list of requirements (this is not<br>
intended to change any requirements from what you wrote):<br>
<br>
&quot;In environments where EAP is used for purposes other than network acc=
ess<br>
authentication:<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o All EAP s=
ervers and all application access EAP peers MUST<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>support channel bindin=
gs. &nbsp;All network access EAP peers<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>SHOULD support channel=
 bindings.<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o Channel b=
inding MUST be used for all application authentication.<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>The EAP server MUST re=
quire that the correct EAP lower-layer<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>attribute be present i=
n the channel binding data for<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>application authentica=
tion.</blockquote>
<div>
<blockquote type=3D"cite"></blockquote>
<font color=3D"#0f61c8"><br>
</font>
<blockquote type=3D"cite"></blockquote>
<span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span>o Channe=
l binding MUST be used for all application authentication.<br>
<blockquote type=3D"cite"></blockquote>
<span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span><span cl=
ass=3D"Apple-tab-span" style=3D"white-space: pre; "></span>The EAP server M=
UST either require that the correct EAP lower-layer<br>
<blockquote type=3D"cite"></blockquote>
<span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span><span cl=
ass=3D"Apple-tab-span" style=3D"white-space: pre; "></span>attribute or ano=
ther attribute indicating the purpose of the authentication</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>be pre=
sent in the channel binding data for&nbsp;application authentication.</div>
<br>
<blockquote type=3D"cite"><br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o Channel b=
inding SHOULD be used for all network access authentication,<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>and when channel bindi=
ng data is present, the EAP server MUST<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>require that it contai=
n the correct EAP lower-layer attribute<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>to explicitly identify=
 the reason for authentication.<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>o Any new u=
sage of EAP MUST use channel bindings including the<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>EAP lower-layer attrib=
ute to prevent confusion with network<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><span class=
=3D"Apple-tab-span" style=3D"white-space:pre"></span>access usage.<br>
<br>
Thanks,<br>
--David<br>
<br>
<br>
<blockquote type=3D"cite">-----Original Message-----<br>
From: Joseph Salowey (jsalowey) [mailto:jsalowey@<a href=3D"http://cisco.co=
m">cisco.com</a>]<br>
Sent: Tuesday, June 18, 2013 1:47 PM<br>
To: Black, David<br>
Cc: <a href=3D"mailto:stefan.winter@restena.lu">stefan.winter@restena.lu</a=
>; General Area Review Team;
<a href=3D"mailto:abfab@ietf.org">abfab@ietf.org</a>;<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03=
<br>
<br>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><br>
I think we could state this a bit better as something like:<br>
<br>
&quot;In environments where EAP is used for applications authentication and=
 network<br>
access authentication all EAP servers MUST understand channel bindings and<=
br>
require that application bindings MUST be present in application<br>
authentication and that application bindings MUST be absent in network<br>
authentication. &nbsp;&nbsp;All network access EAP peer implementations SHO=
ULD support<br>
channel binding to explicitly identify the reason for authentication. &nbsp=
;Any new<br>
usage of EAP MUST support channel bindings to prevent confusion with networ=
k<br>
access usage. &quot;<br>
</blockquote>
<br>
That text is an improvement, and it's headed in the same direction as Sam's=
<br>
comment - &quot;application bindings MUST be present in application authent=
ication&quot;<br>
is a &quot;MUST use&quot; requirement, not just a &quot;MUST implement&quot=
; requirement.<br>
<br>
OTOH, I'm not clear on what &quot;application bindings&quot; means, as that=
 term's not<br>
in the current draft. &nbsp;Specifically, I'm a bit unclear on &quot;applic=
ation bindings<br>
MUST be absent in network authentication&quot; - does that mean that channe=
l<br>
binding must be absent, or that channel binding is optional, but if channel=
<br>
binding is present, it MUST NOT be an &quot;application binding&quot;, what=
ever that<br>
</blockquote>
is?<br>
<blockquote type=3D"cite"><br>
</blockquote>
<br>
[Joe] Good points, the text can be more specific:<br>
<br>
&quot;In environments where EAP is used for purposes other than network acc=
ess<br>
authentication all EAP servers MUST enforce channel bindings. &nbsp;For app=
lication<br>
authentication, the EAP server MUST require that the correct EAP lower-laye=
r<br>
attribute be present in the channel binding data. &nbsp;&nbsp;For network a=
ccess<br>
authentication, the EAP server MUST require that if channel bindings are<br=
>
present they MUST contain the correct EAP lower-layer attribute. &nbsp;&nbs=
p;All network<br>
access EAP peer implementations SHOULD use channel bindings including the E=
AP<br>
lower-layer attribute to explicitly identify the reason for authentication.=
<br>
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r<br>
attribute to prevent confusion with network access usage. &quot;<br>
<br>
Does this help?<br>
<br>
Thanks,<br>
<br>
Joe<br>
<br>
</blockquote>
<br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_A95B4818FD85874D8F16607F1AC7C628D03C96xmbrcdx09ciscocom_--

From hartmans@painless-security.com  Thu Jun 20 02:56:35 2013
Return-Path: <hartmans@painless-security.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 288CA11E8116; Thu, 20 Jun 2013 02:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IlneuKxmBuI6; Thu, 20 Jun 2013 02:56:29 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4802221F9FFD; Thu, 20 Jun 2013 02:56:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 70C6C20127; Thu, 20 Jun 2013 05:52:31 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPqBf-X0ASKW; Thu, 20 Jun 2013 05:52:31 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 20 Jun 2013 05:52:31 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 75C24807E8; Thu, 20 Jun 2013 05:56:12 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
Date: Thu, 20 Jun 2013 05:56:12 -0400
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com> (Joseph Salowey's message of "Wed, 19 Jun 2013 23:23:03 +0000")
Message-ID: <tsla9mlt8ar.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "abfab@ietf.org" <abfab@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 09:56:35 -0000

I'm fine with this text.
Either with eap-lower-layer as a MUST or the more complex version.

From david.black@emc.com  Thu Jun 20 05:32:39 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC1E21F9C02; Thu, 20 Jun 2013 05:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZZZcakcQMArg; Thu, 20 Jun 2013 05:32:34 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9929F21F9BFF; Thu, 20 Jun 2013 05:32:34 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5KCWW9l005691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jun 2013 08:32:33 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 20 Jun 2013 08:32:13 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r5KCW1eU006337; Thu, 20 Jun 2013 08:32:12 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub33.corp.emc.com ([::1]) with mapi; Thu, 20 Jun 2013 08:32:02 -0400
From: "Black, David" <david.black@emc.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Date: Thu, 20 Jun 2013 08:32:00 -0400
Thread-Topic: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgAYb7oMABB0QQAAClxl4P//t2GAgAA80uCAAbNjgP//eC/w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71298265674@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <tsl38sfbiyd.fsf@mit.edu> <A95B4818FD85874D8F16607F1AC7C628CF9E35@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712982652A5@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628CFA26E@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71298265300@MX15A.corp.emc.com> <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628D03C96@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 12:32:40 -0000

--_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think this is ok, but my email client isn't distinguishing the new vs. ol=
d text.

If it's just changes to produce this new bullet, I have a small edit:

o Channel binding MUST be used for all application authentication.
The EAP server MUST either require that the correct EAP lower-layer
attribute or another attribute indicating the purpose of the authentication
be present in the channel binding data for application authentication.

"MUST either require that" --> "MUST require that either"

Thanks,
--David

From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
Sent: Wednesday, June 19, 2013 7:23 PM
To: Black, David
Cc: stefan.winter@restena.lu; General Area Review Team; abfab@ietf.org; iet=
f@ietf.org
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03

Thanks for the text,  some revision to address
On Jun 18, 2013, at 12:34 PM, "Black, David" <david.black@emc.com<mailto:da=
vid.black@emc.com>> wrote:


[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

This is looking good, modulo Sam's comment on EAP lower-layer vs. something
else that I'll leave to you and he to sort out.  I have a suggested rewrite=
,
mostly to clarify MUST vs. SHOULD requirements for support vs. usage, and
to reformat into a structured bullet list of requirements (this is not
intended to change any requirements from what you wrote):

"In environments where EAP is used for purposes other than network access
authentication:

o All EAP servers and all application access EAP peers MUST
support channel bindings.  All network access EAP peers
SHOULD support channel bindings.

o Channel binding MUST be used for all application authentication.
The EAP server MUST require that the correct EAP lower-layer
attribute be present in the channel binding data for
application authentication.


o Channel binding MUST be used for all application authentication.

The EAP server MUST either require that the correct EAP lower-layer

attribute or another attribute indicating the purpose of the authentication
be present in the channel binding data for application authentication.



o Channel binding SHOULD be used for all network access authentication,
and when channel binding data is present, the EAP server MUST
require that it contain the correct EAP lower-layer attribute
to explicitly identify the reason for authentication.

o Any new usage of EAP MUST use channel bindings including the
EAP lower-layer attribute to prevent confusion with network
access usage.

Thanks,
--David



-----Original Message-----
From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com<http://cisco.com=
>]
Sent: Tuesday, June 18, 2013 1:47 PM
To: Black, David
Cc: stefan.winter@restena.lu<mailto:stefan.winter@restena.lu>; General Area=
 Review Team; abfab@ietf.org<mailto:abfab@ietf.org>;
ietf@ietf.org<mailto:ietf@ietf.org>
Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicability-03



I think we could state this a bit better as something like:

"In environments where EAP is used for applications authentication and netw=
ork
access authentication all EAP servers MUST understand channel bindings and
require that application bindings MUST be present in application
authentication and that application bindings MUST be absent in network
authentication.   All network access EAP peer implementations SHOULD suppor=
t
channel binding to explicitly identify the reason for authentication.  Any =
new
usage of EAP MUST support channel bindings to prevent confusion with networ=
k
access usage. "

That text is an improvement, and it's headed in the same direction as Sam's
comment - "application bindings MUST be present in application authenticati=
on"
is a "MUST use" requirement, not just a "MUST implement" requirement.

OTOH, I'm not clear on what "application bindings" means, as that term's no=
t
in the current draft.  Specifically, I'm a bit unclear on "application bind=
ings
MUST be absent in network authentication" - does that mean that channel
binding must be absent, or that channel binding is optional, but if channel
binding is present, it MUST NOT be an "application binding", whatever that
is?



[Joe] Good points, the text can be more specific:

"In environments where EAP is used for purposes other than network access
authentication all EAP servers MUST enforce channel bindings.  For applicat=
ion
authentication, the EAP server MUST require that the correct EAP lower-laye=
r
attribute be present in the channel binding data.   For network access
authentication, the EAP server MUST require that if channel bindings are
present they MUST contain the correct EAP lower-layer attribute.   All netw=
ork
access EAP peer implementations SHOULD use channel bindings including the E=
AP
lower-layer attribute to explicitly identify the reason for authentication.
Any new usage of EAP MUST use channel bindings including the EAP lower-laye=
r
attribute to prevent confusion with network access usage. "

Does this help?

Thanks,

Joe



--_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: space;-webkit=
-line-break: after-white-space'><div class=3DWordSection1><p class=3DMsoNor=
mal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>=
I think this is ok, but my email client isn&#8217;t distinguishing the new =
vs. old text.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New";color:black'>If it&#8217;s just changes to produce this new bullet=
, I have a small edit:<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New";color:black'>o Channel binding MUST be used for all appli=
cation authentication.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'm=
argin-left:.5in'><span style=3D'font-size:10.0pt;font-family:"Courier New";=
color:black'>The EAP server MUST either require that the correct EAP lower-=
layer<br>attribute or another attribute indicating the purpose of the authe=
ntication<o:p></o:p></span></p><p class=3DMsoNormal style=3D'text-indent:.5=
in'><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>=
be present in the channel binding data for&nbsp;application authentication.=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>&#8220;MUST either require that&#8221; --&gt; &#8220;MUST require =
that either&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p><=
/span></p><div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'>Thanks,<br>--David</span><span style=
=3D'font-size:11.0pt;font-family:"Courier New";color:black'><o:p></o:p></sp=
an></p></div></div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><div style=
=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><di=
v><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;=
font-family:"Tahoma","sans-serif"'> Joseph Salowey (jsalowey) [mailto:jsalo=
wey@cisco.com] <br><b>Sent:</b> Wednesday, June 19, 2013 7:23 PM<br><b>To:<=
/b> Black, David<br><b>Cc:</b> stefan.winter@restena.lu; General Area Revie=
w Team; abfab@ietf.org; ietf@ietf.org<br><b>Subject:</b> Re: [abfab] Gen-AR=
T review of draft-ietf-abfab-eapapplicability-03<o:p></o:p></span></p></div=
></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thank=
s for the text, &nbsp;some revision to address&nbsp;<o:p></o:p></p><div><di=
v><p class=3DMsoNormal>On Jun 18, 2013, at 12:34 PM, &quot;Black, David&quo=
t; &lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&gt; w=
rote:<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><bloc=
kquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>=
[Joe] Good points, the text can be more specific:<br><br>&quot;In environme=
nts where EAP is used for purposes other than network access<br>authenticat=
ion all EAP servers MUST enforce channel bindings. &nbsp;For application<br=
>authentication, the EAP server MUST require that the correct EAP lower-lay=
er<br>attribute be present in the channel binding data. &nbsp;&nbsp;For net=
work access<br>authentication, the EAP server MUST require that if channel =
bindings are<br>present they MUST contain the correct EAP lower-layer attri=
bute. &nbsp;&nbsp;All network<br>access EAP peer implementations SHOULD use=
 channel bindings including the EAP<br>lower-layer attribute to explicitly =
identify the reason for authentication.<br>Any new usage of EAP MUST use ch=
annel bindings including the EAP lower-layer<br>attribute to prevent confus=
ion with network access usage. &quot;<o:p></o:p></p></blockquote><p class=
=3DMsoNormal><br>This is looking good, modulo Sam's comment on EAP lower-la=
yer vs. something<br>else that I'll leave to you and he to sort out. &nbsp;=
I have a suggested rewrite,<br>mostly to clarify MUST vs. SHOULD requiremen=
ts for support vs. usage, and<br>to reformat into a structured bullet list =
of requirements (this is not<br>intended to change any requirements from wh=
at you wrote):<br><br>&quot;In environments where EAP is used for purposes =
other than network access<br>authentication:<br><br>o All EAP servers and a=
ll application access EAP peers MUST<br>support channel bindings. &nbsp;All=
 network access EAP peers<br>SHOULD support channel bindings.<br><br>o Chan=
nel binding MUST be used for all application authentication.<br>The EAP ser=
ver MUST require that the correct EAP lower-layer<br>attribute be present i=
n the channel binding data for<br>application authentication.<o:p></o:p></p=
><div><p class=3DMsoNormal><span style=3D'color:#0F61C8'><br><br></span><o:=
p></o:p></p><p class=3DMsoNormal>o Channel binding MUST be used for all app=
lication authentication.<br><br><o:p></o:p></p><p class=3DMsoNormal>The EAP=
 server MUST either require that the correct EAP lower-layer<br><br><o:p></=
o:p></p><p class=3DMsoNormal>attribute or another attribute indicating the =
purpose of the authentication<o:p></o:p></p></div><div><p class=3DMsoNormal=
>be present in the channel binding data for&nbsp;application authentication=
.<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><p class=
=3DMsoNormal><br>o Channel binding SHOULD be used for all network access au=
thentication,<br>and when channel binding data is present, the EAP server M=
UST<br>require that it contain the correct EAP lower-layer attribute<br>to =
explicitly identify the reason for authentication.<br><br>o Any new usage o=
f EAP MUST use channel bindings including the<br>EAP lower-layer attribute =
to prevent confusion with network<br>access usage.<br><br>Thanks,<br>--Davi=
d<br><br><br><br><o:p></o:p></p><p class=3DMsoNormal>-----Original Message-=
----<br>From: Joseph Salowey (jsalowey) [mailto:jsalowey@<a href=3D"http://=
cisco.com">cisco.com</a>]<br>Sent: Tuesday, June 18, 2013 1:47 PM<br>To: Bl=
ack, David<br>Cc: <a href=3D"mailto:stefan.winter@restena.lu">stefan.winter=
@restena.lu</a>; General Area Review Team; <a href=3D"mailto:abfab@ietf.org=
">abfab@ietf.org</a>;<br><a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>=
<br>Subject: Re: [abfab] Gen-ART review of draft-ietf-abfab-eapapplicabilit=
y-03<br><br><br><o:p></o:p></p><blockquote style=3D'margin-top:5.0pt;margin=
-bottom:5.0pt'><p class=3DMsoNormal><br>I think we could state this a bit b=
etter as something like:<br><br>&quot;In environments where EAP is used for=
 applications authentication and network<br>access authentication all EAP s=
ervers MUST understand channel bindings and<br>require that application bin=
dings MUST be present in application<br>authentication and that application=
 bindings MUST be absent in network<br>authentication. &nbsp;&nbsp;All netw=
ork access EAP peer implementations SHOULD support<br>channel binding to ex=
plicitly identify the reason for authentication. &nbsp;Any new<br>usage of =
EAP MUST support channel bindings to prevent confusion with network<br>acce=
ss usage. &quot;<o:p></o:p></p></blockquote><p class=3DMsoNormal><br>That t=
ext is an improvement, and it's headed in the same direction as Sam's<br>co=
mment - &quot;application bindings MUST be present in application authentic=
ation&quot;<br>is a &quot;MUST use&quot; requirement, not just a &quot;MUST=
 implement&quot; requirement.<br><br>OTOH, I'm not clear on what &quot;appl=
ication bindings&quot; means, as that term's not<br>in the current draft. &=
nbsp;Specifically, I'm a bit unclear on &quot;application bindings<br>MUST =
be absent in network authentication&quot; - does that mean that channel<br>=
binding must be absent, or that channel binding is optional, but if channel=
<br>binding is present, it MUST NOT be an &quot;application binding&quot;, =
whatever that<o:p></o:p></p><p class=3DMsoNormal>is?<br><br><o:p></o:p></p>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'mar=
gin-bottom:12.0pt'><br>[Joe] Good points, the text can be more specific:<br=
><br>&quot;In environments where EAP is used for purposes other than networ=
k access<br>authentication all EAP servers MUST enforce channel bindings. &=
nbsp;For application<br>authentication, the EAP server MUST require that th=
e correct EAP lower-layer<br>attribute be present in the channel binding da=
ta. &nbsp;&nbsp;For network access<br>authentication, the EAP server MUST r=
equire that if channel bindings are<br>present they MUST contain the correc=
t EAP lower-layer attribute. &nbsp;&nbsp;All network<br>access EAP peer imp=
lementations SHOULD use channel bindings including the EAP<br>lower-layer a=
ttribute to explicitly identify the reason for authentication.<br>Any new u=
sage of EAP MUST use channel bindings including the EAP lower-layer<br>attr=
ibute to prevent confusion with network access usage. &quot;<br><br>Does th=
is help?<br><br>Thanks,<br><br>Joe<o:p></o:p></p><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div=
></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE71298265674MX15Acorpemccom_--

From peter@akayla.com  Thu Jun 20 14:56:59 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B5B21F9E3B for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 14:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7KDUdl3EZwVK for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 14:56:54 -0700 (PDT)
Received: from p3plsmtpa11-04.prod.phx3.secureserver.net (p3plsmtpa11-04.prod.phx3.secureserver.net [68.178.252.105]) by ietfa.amsl.com (Postfix) with ESMTP id 275B321F9E19 for <gen-art@ietf.org>; Thu, 20 Jun 2013 14:56:46 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-04.prod.phx3.secureserver.net with  id qlwl1l0011huGat01lwll2; Thu, 20 Jun 2013 14:56:46 -0700
From: "Peter Yee" <peter@akayla.com>
To: <gen-art@ietf.org>
Date: Thu, 20 Jun 2013 14:56:47 -0700
Message-ID: <019c01ce6e01$105176c0$30f46440$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_019D_01CE6DC6.63F29EC0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5t/J3LduZO2b8ERraGB4g8wVPMnw==
Content-Language: en-us
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-06-20
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 21:56:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_019D_01CE6DC6.63F29EC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

The following reviewers have assignments:

 

Reviewer          LC end       Draft

---------------------------------------------------------------------

Alexey Melnikov   2013-07-03  draft-ietf-multimob-pmipv6-ropt-06

 

Ben Campbell      2013-07-16  draft-yusef-dispatch-ccmp-indication-04

 

Brian Carpenter   2013-07-16  draft-ivov-xmpp-cusax-06

 

Francis Dupont    2013-07-01
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05

 

Joel Halpern      2013-07-01  draft-ietf-straw-b2bua-taxonomy-02

 

Peter Yee         2013-07-17  draft-jabley-dnsext-eui48-eui64-rrtypes-05

 

I have made the assignments in the review tool:

http://art.tools.ietf.org/tools/art/genart/

 

And the assignments are captured in the spreadsheets:

http://wiki.tools.ietf.org/dav/genart/gen-art.html

http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

 

 

The standard template is included below.

 

Thanks,

 

Peter

 

-------------------------------------------------------------------

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

 

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document:

Reviewer:

Review Date:

IETF LC End Date:

IESG Telechat date: (if known)

 

Summary:

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

_______________________________________________

Gen-art mailing list

Gen-art@ietf.org

https://www.ietf.org/mailman/listinfo/gen-art

 


------=_NextPart_000_019D_01CE6DC6.63F29EC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@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:0in;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The following reviewers have =
assignments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Reviewer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LC =
end&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Draft<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
--<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Alexey Melnikov&nbsp;&nbsp; =
2013-07-03&nbsp; =
draft-ietf-multimob-pmipv6-ropt-06<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Ben =
Campbell&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-07-16&nbsp; =
draft-yusef-dispatch-ccmp-indication-04<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Brian Carpenter&nbsp;&nbsp; =
2013-07-16&nbsp; draft-ivov-xmpp-cusax-06<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Francis Dupont&nbsp;&nbsp;&nbsp; =
2013-07-01&nbsp; =
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05<o:p></o:p></span></p><p=
 class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Joel Halpern&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;2013-07-01&nbsp; =
draft-ietf-straw-b2bua-taxonomy-02<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Peter =
Yee&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-07-17 =
&nbsp;draft-jabley-dnsext-eui48-eui64-rrtypes-05<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>I have made the assignments in the =
review tool:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>http://art.tools.ietf.org/tools/art/genart/<o:p></o:p></span></p><p=
 class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>And the assignments are captured in =
the spreadsheets:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>http://wiki.tools.ietf.org/dav/genart/gen-art.html<o:p></o:p></span=
></p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The standard template is included =
below.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Thanks,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Peter<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<o:=
p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Please =
resolve these comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Document:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Reviewer:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Review =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IETF LC End =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IESG Telechat date: (if =
known)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Summary:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>_______________________________________________<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art mailing list<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art@ietf.org<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>https://www.ietf.org/mailman/listinfo/gen-art<o:p></o:p></span></p>=
<p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_019D_01CE6DC6.63F29EC0--


From peter@akayla.com  Thu Jun 20 15:06:39 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC1CB11E80E4 for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 15:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jI37F0zKdmDI for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 15:06:34 -0700 (PDT)
Received: from p3plsmtpa06-09.prod.phx3.secureserver.net (p3plsmtpa06-09.prod.phx3.secureserver.net [173.201.192.110]) by ietfa.amsl.com (Postfix) with ESMTP id DBA1D21F9AF8 for <gen-art@ietf.org>; Thu, 20 Jun 2013 15:06:33 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-09.prod.phx3.secureserver.net with  id qm6Y1l0041huGat01m6YAq; Thu, 20 Jun 2013 15:06:33 -0700
From: "Peter Yee" <peter@akayla.com>
To: <gen-art@ietf.org>
Date: Thu, 20 Jun 2013 15:06:35 -0700
Message-ID: <01ad01ce6e02$6e41f790$4ac5e6b0$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AE_01CE6DC7.C1E4A630"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5uATQQ/z2SFPK8TSq13d+FaTO03w==
Content-Language: en-us
Subject: [Gen-art] Assignments for the 2013-06-27 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 22:06:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01AE_01CE6DC7.C1E4A630
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

The following reviewers have assignments:

 

Reviewer               LC end     Draft

----------------------------------------------------------------------------
--------

Alexey Melnikov        2013-06-07   draft-ietf-pce-gmpls-aps-req-08 **

 

Ben Campbell           2013-06-25   draft-thornburgh-adobe-rtmfp-07 **

 

Brian Carpenter        2013-06-11   draft-ietf-avtcore-avp-codecs-02 **

 

Francis Dupont         2013-05-14   draft-housley-rfc2050bis-01 **

 

Meral Shirazipour      2013-05-31   draft-ietf-xrblock-rtcp-xr-jb-12 *

 

Martin Thomson         2013-06-19
draft-ietf-nvo3-overlay-problem-statement-03 **

 

Peter McCann           2012-10-22   draft-ietf-storm-iser-14 *

 

Peter McCann           2013-05-03   draft-ietf-geopriv-relative-location-05
*

 

Peter McCann           2013-06-03   draft-ietf-xrblock-rtcp-xr-discard-14 *

 

Roni Even              2013-06-04
draft-ietf-mmusic-sdp-miscellaneous-caps-06 *

 

Roni Even              2013-06-24   draft-ietf-pkix-est-07 **

 

Suresh Krishnan        2013-06-21   draft-ietf-ipsecme-ad-vpn-problem-07 **

 

Vijay Gurbani          2013-06-06   draft-ietf-l3vpn-virtual-hub-06 **

 

Wassim Haddad          2013-05-07   draft-sparks-genarea-imaparch-07 *

 

* Earlier draft reviewed

** Already reviewed

 

 

 

I have made the assignments in the review tool:

 <http://art.tools.ietf.org/tools/art/genart/>
http://art.tools.ietf.org/tools/art/genart/

 

And the assignments are captured in the spreadsheets:

 <http://wiki.tools.ietf.org/dav/genart/gen-art.html>
http://wiki.tools.ietf.org/dav/genart/gen-art.html

 <http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html>
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

 

For your convenience, the review boilerplate template is included below.

 

Note that reviews should ideally be posted to the gen-art mailing list by
COB on Tuesday:

 <http://wiki.tools.ietf.org/area/gen/trac/wiki/>
http://wiki.tools.ietf.org/area/gen/trac/wiki/

 

Peter

 

-------------------------------------------------------------------

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at <
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please wait for direction from your document shepherd or AD before posting a
new version of the draft.

 

Document:

Reviewer:

Review Date:

IETF LC End Date:

IESG Telechat date: (if known)

 

Summary:

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

_______________________________________________

Gen-art mailing list

 <mailto:Gen-art@ietf.org> Gen-art@ietf.org

 <https://www.ietf.org/mailman/listinfo/gen-art>
https://www.ietf.org/mailman/listinfo/gen-art


------=_NextPart_000_01AE_01CE6DC7.C1E4A630
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@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:0in;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The following reviewers have =
assignments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Reviewer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; LC end&nbsp;&nbsp;&nbsp;&nbsp; =
Draft<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
-----------------<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Alexey =
Melnikov&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-07 =
&nbsp;&nbsp;draft-ietf-pce-gmpls-aps-req-08 **<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Ben =
Campbell&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2013-06-25&nbsp; &nbsp;draft-thornburgh-adobe-rtmfp-07 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Brian =
Carpenter&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-11 =
&nbsp;&nbsp;draft-ietf-avtcore-avp-codecs-02 **<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Francis =
Dupont&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-05-14 =
&nbsp;&nbsp;draft-housley-rfc2050bis-01 **<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Meral =
Shirazipour&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-05-31 =
&nbsp;&nbsp;draft-ietf-xrblock-rtcp-xr-jb-12 *<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Martin =
Thomson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-19 =
&nbsp;&nbsp;draft-ietf-nvo3-overlay-problem-statement-03 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Peter =
McCann&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2012-10-22 &nbsp;&nbsp;draft-ietf-storm-iser-14 =
*<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Peter =
McCann&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2013-05-03 &nbsp;&nbsp;draft-ietf-geopriv-relative-location-05 =
*<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Peter =
McCann&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2013-06-03&nbsp; &nbsp;draft-ietf-xrblock-rtcp-xr-discard-14 =
*<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Roni =
Even&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; 2013-06-04 =
&nbsp;&nbsp;draft-ietf-mmusic-sdp-miscellaneous-caps-06 =
*<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Roni =
Even&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; 2013-06-24 &nbsp;&nbsp;draft-ietf-pkix-est-07 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Suresh =
Krishnan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-21 =
&nbsp;&nbsp;draft-ietf-ipsecme-ad-vpn-problem-07 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Vijay =
Gurbani&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-06 =
&nbsp;&nbsp;draft-ietf-l3vpn-virtual-hub-06 **<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Wassim =
Haddad&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-05-07 =
&nbsp;&nbsp;draft-sparks-genarea-imaparch-07 *<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>* Earlier draft =
reviewed<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>** Already =
reviewed<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I have =
made the assignments in the review tool:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"http://art.tools.ietf.org/tools/art/genart/"><span =
style=3D'color:windowtext;text-decoration:none'>http://art.tools.ietf.org=
/tools/art/genart/</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>And the assignments are captured in =
the spreadsheets:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/dav/genart/gen-art.html"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/dav/genart/gen-art.html</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html"><=
span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/dav/genart/gen-art-by-reviewer.html</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>For your convenience, the review =
boilerplate template is included below.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Note that reviews should ideally be =
posted to the gen-art mailing list by COB on =
Tuesday:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/area/gen/trac/wiki/</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Peter<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt; <a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/area/gen/trac/wiki/GenArtfaq</span></a>&gt;.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Please wait for direction from your =
document shepherd or AD before posting a new version of the =
draft.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Document:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Reviewer:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Review =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IETF LC End =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IESG Telechat date: (if =
known)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Summary:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>_______________________________________________<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art mailing list<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"mailto:Gen-art@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>Gen-art@ietf.org</span></=
a><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"https://www.ietf.org/mailman/listinfo/gen-art"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/gen-art</span></a><o:p></o:p></span></p></div></body></html>
------=_NextPart_000_01AE_01CE6DC7.C1E4A630--


From ben@nostrum.com  Thu Jun 20 16:06:34 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 232FE21F9C55; Thu, 20 Jun 2013 16:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1cdAQEpDNkeR; Thu, 20 Jun 2013 16:06:33 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EBA9421F9B00; Thu, 20 Jun 2013 16:06:32 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5KN6VBg023628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Jun 2013 18:06:31 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 20 Jun 2013 18:06:31 -0500
Message-Id: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
To: draft-thornburgh-adobe-rtmfp.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 23:06:34 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-thornburgh-adobe-rtmfp-07
Reviewer: Ben Campbell
Review Date:  2013-06-20
IETF LC End Date: 2013-06-25

Summary: This draft is almost ready for publication as an informational =
RFC. However, I have some concerns about the purpose and intended status =
of the document that I think should be considered prior to publication.


Note: This is an informational draft that describes what I understand to =
be an existing protocol as implemented by commercial products. =
Therefore, this review does not attempt to evaluate the protocol itself. =
I assume the protocol is what it is, and it is not up to the IETF to =
agree or disagree with it.

*** Major issues:

-- Why does this need to be published as an IETF stream RFC?  If I =
understand correctly, this documents an existing protocol as implemented =
by commercial products. I agree with Martin's comment that there is =
value in publishing this sort of thing, but I applaud the Adobe and the =
author for publishing it so other implementations can interoperate with =
their products. But that could have done that in an independent stream =
document, or even in an Adobe published document. (Perhaps even in a =
prettier format ;-)  )  If we publish this as an IETF stream document, =
then I think it needs stronger clarification that it is not an IETF =
consensus doc than just its informational status.

Along those lines:

	-- Is this document the authoritative specification? (I suspect =
not.) Who owns change control? I assume that to be Adobe and/or the =
authors. What expectation do readers of this draft have that it =
represents the current version of RTMFP at any point in time?

	-- Under what circumstances would one desire to implement this? =
I can infer that from the introduction, but it would be nice to see some =
sort of applicability statement making it explicitly clear that this is =
not an IETF protocol, and that one would implement it in order to =
interoperate with certain Adobe products. I know that some of this may =
be implied by the fact that this is informational rather than standards =
track. But I don't expect readers who are not IETF insiders to =
understand that subtlety without some explicit words to that effect. In =
particular, it would be good to clarify the difference between this and =
the many "not quite accepted as standards track by some working group" =
nature of a number of our informational RFCs that describe protocols.

That all being said, this is overall a well written document. The rest =
of my comments are mostly pedantic nits.

*** Minor issues:

-- section 1.2:=20

I find the use of "MUST ONLY" confusing. I gather it means "you are =
_allowed_ to do X only under certain conditions" rather than "you are =
_required_ to do X under certain conditions." If correct, I think the =
words "MAY ONLY" would be more clear. If not, then I think the construct =
would be better handled using existing 2119 language.

-- section 3.2:

Do I understand correctly that all endpoints are expected to be able to =
present certificates? Do you find that common in the field? I realize =
the nature of the certs will depend on the security profiles.

-- sections 3.2 and 5

Do I assume correctly that endpoints need a common crypto profile to =
communicate? Is there a repository where one might find crypto profile =
documentation? Is there a commonly implemented one to which this draft =
could refer?

-- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."

Why not MUST? Will things not break if two endpoints do have the same =
identity?

-- "Authenticity MAY comprise verifying an issuer signature chain in a =
public key infrastructure"

Is that really normative, or just an observation of fact?

-- " Canonical Endpoint Discriminators for distinct identities SHOULD be =
distinct."

What if they are not? Do things break? It might be worth making this a =
MUST, or adding some additional guidance about what might happen if the =
SHOULD is violated.

-- "A comparison function MAY comprise performing a lexicographic =
ordering..."

Is that really normative, or just an example of something one might do?

-- "A test SHOULD comprise testing whether the certificates are =
identical."

What if it doesn't? Also, what constitutes "identical"? All fields match =
values? Bitwise match?  Is it simply including the same identity or =
identities? Maybe an identity function provided by the crypto profile?

-- 3.5, last paragraph:

Can you offer guidance on reasonable buffer size and number ranges?

-- 3.5.1.1.1, 3rd paragraph:

What are the consequences of having a tag with less than 8 bytes of =
length? Is the SHOULD reasonable here?

-- 3.5.1.1.1 throughout, and following sections:

Does the upper case AND have special meaning?

-- 3.5.1.4, Deployment Note:

How would a redirector know which endpoints might do this? Or should it =
never initiate a session?

-- 3.5.2:

Do I infer correctly that two endpoints need not share the same =
congestion control algorithm to communicate?

-- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next =
User Data chunk instead of a User Data chunk"

I'm not sure why this needs to be normative, as I assume its just normal =
behavior. But if it does need to be normative, why not a MUST?  Can the =
far endpoint reasonably handle things if the SHOULD is violated?


*** Nits/editorial comments:

-- General: There's quite a bit of inconsistent use of third-person vs =
second-person language.

-- 3.1: It would be nice to see the overview earlier in the draft. I =
found it difficult to read through all the data format stuff prior to =
section 3 putting them into context.

-- 3.5.1.4, Deployment Note:

s/which/that

-- 3.5.1.6, last paragraph:

Which diagram? (An explicit cross-ref would help.)

-- 3.5.2:

What is meant by "aggressive" in this context? Aggressive in avoiding =
congestion, or aggressive in sending data?

-- 3.6.2.3.1 and subsequent sections:

Does the all-caps "FIRST" have special meaning?









From barryleiba.mailing.lists@gmail.com  Thu Jun 20 19:14:43 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA78D21E80F8; Thu, 20 Jun 2013 19:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.004
X-Spam-Level: 
X-Spam-Status: No, score=-102.004 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBu2jDkl7r0F; Thu, 20 Jun 2013 19:14:43 -0700 (PDT)
Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 0B66621E80EB; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id 14so5766451vea.15 for <multiple recipients>; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gh3oLRJY2BAYin8SjXHc465XL5E//azZEX0XudaAQ50=; b=bLtPA7q483X2xHgkbRJHLWs3fDhPg9RI1QuKwGcdP9K3xxsMTQFh0XWTx//VPA1SWa GAbOkc6W64HeOiUmEWq99hSCnhT7Ekz6diJ0eQhZUo4/DqMlVw2xS2RHqIhkjKhFJtRT 1jgec0Tg4HsZPqSZL10nzcYI+/dbbRwY5VA2AY34P8HdlKn86c+rZrMrQbsZC55R+c4/ rOJl1miEkN1AhgMZX+OXbYhECxVWYIv5+amUy5/coWGPbQir4qmBMdmVC+e4PPNc5lTq rG8B5JvWzyFT4abyopZLn+HsER6o5OdwtsOCWmiDRUfG1gxkY6eY2AKmeNilILQI7QfP eDbg==
MIME-Version: 1.0
X-Received: by 10.220.101.69 with SMTP id b5mr4329884vco.55.1371780882405; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.234.105 with HTTP; Thu, 20 Jun 2013 19:14:42 -0700 (PDT)
In-Reply-To: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
Date: Thu, 20 Jun 2013 22:14:42 -0400
X-Google-Sender-Auth: SJobIzffGqcppGVo2ReD8PZsv7c
Message-ID: <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=047d7b3a7e9234b39804dfa0a0a6
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 02:14:43 -0000

--047d7b3a7e9234b39804dfa0a0a6
Content-Type: text/plain; charset=ISO-8859-1

>
> -- Why does this need to be published as an IETF stream RFC?  If I
> understand correctly, this documents an existing protocol as implemented by
> commercial products. I agree with Martin's comment that there is value in
> publishing this sort of thing, but I applaud the Adobe and the author for
> publishing it so other implementations can interoperate with their
> products. But that could have done that in an independent stream document,
> or even in an Adobe published document. (Perhaps even in a prettier format
> ;-)  )  If we publish this as an IETF stream document, then I think it
> needs stronger clarification that it is not an IETF consensus doc than just
> its informational status.


 FWIW, the IESG has discussed this in the context of other documents, and
is looking at boilerplate that does not say that the document is a "product
of the IETF", and makes it clear that the content is not a matter of IETF
consensus.  If that sort of boilerplate was used, do you think that would
be sufficient?

Barry

--047d7b3a7e9234b39804dfa0a0a6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">-- Why does this need to be published as an =
IETF stream RFC? =A0If I understand correctly, this documents an existing p=
rotocol as implemented by commercial products. I agree with Martin&#39;s co=
mment that there is value in publishing this sort of thing, but I applaud t=
he Adobe and the author for publishing it so other implementations can inte=
roperate with their products. But that could have done that in an independe=
nt stream document, or even in an Adobe published document. (Perhaps even i=
n a prettier format ;-) =A0) =A0If we publish this as an IETF stream docume=
nt, then I think it needs stronger clarification that it is not an IETF con=
sensus doc than just its informational status.</blockquote>
<div><br></div><div>=A0FWIW, the IESG has discussed this in the context of =
other documents, and is looking at boilerplate that does not say that the d=
ocument is a &quot;product of the IETF&quot;, and makes it clear that the c=
ontent is not a matter of IETF consensus. =A0If that sort of boilerplate wa=
s used, do you think that would be sufficient?</div>
<div><br></div><div>Barry<span></span></div><div><br></div>

--047d7b3a7e9234b39804dfa0a0a6--

From john-ietf@jck.com  Thu Jun 20 20:12:32 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1152F21E80DF; Thu, 20 Jun 2013 20:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E+2TEg9MNYTp; Thu, 20 Jun 2013 20:12:16 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8819D21E80EB; Thu, 20 Jun 2013 20:12:16 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uprli-0005q2-Us; Thu, 20 Jun 2013 23:12:10 -0400
Date: Thu, 20 Jun 2013 23:12:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Ben Campbell <ben@nostrum.com>
Message-ID: <BB60A472FABE3AE51CEFBE8C@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, draft-thornburgh-adobe-rtmfp.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 03:12:32 -0000

--On Thursday, June 20, 2013 22:14 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>  FWIW, the IESG has discussed this in the context of other
> documents, and is looking at boilerplate that does not say
> that the document is a "product of the IETF", and makes it
> clear that the content is not a matter of IETF consensus.  If
> that sort of boilerplate was used, do you think that would be
> sufficient?

FWIW, many IETF Stream Info documents definitely are "matters of
IETF consensus", even more so when those documents are the
consequence of a WG request to publish.   IMO, if a document
really isn't an IETf product in any way and has no relationship
to IETF consensus, it would be far more reasonable for ADs to
simply decline to sponsor it --leaving the document to the
Independent Submission Editor or outside the RFC Series-- rather
than trying to diddle around with boilerplate... especially
since we know that people rarely pay attention to stock
boilerplate.

The option of sponsoring individual submission informational
documents is one that the community granted the IESG in order to
give you folks a reasonable way to deal with circumstances that
were more or less unusual.  You don't need to use it.

   john

p.s. I started a much more detailed response to Ben, but I think
the essence of it is above.  IMO, a discussion that amounts to
whether or not an AD used bad judgment by choosing to sponsor an
individual Informational submission (or whether ADs should have
that power at all) should not become part of evaluating a
particular document's appropriateness.


From ben@nostrum.com  Thu Jun 20 20:54:28 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F98D21F9C9A; Thu, 20 Jun 2013 20:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVE+w5fPVwVy; Thu, 20 Jun 2013 20:54:27 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1DC21F9CA2; Thu, 20 Jun 2013 20:54:26 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5L3sMBT054389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Jun 2013 22:54:23 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
Date: Thu, 20 Jun 2013 22:54:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B13E844-9B03-4398-8F38-2BE876C420D3@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 03:54:28 -0000

On Jun 20, 2013, at 9:14 PM, Barry Leiba <barryleiba@computer.org> =
wrote:

> -- Why does this need to be published as an IETF stream RFC?  If I =
understand correctly, this documents an existing protocol as implemented =
by commercial products. I agree with Martin's comment that there is =
value in publishing this sort of thing, but I applaud the Adobe and the =
author for publishing it so other implementations can interoperate with =
their products. But that could have done that in an independent stream =
document, or even in an Adobe published document. (Perhaps even in a =
prettier format ;-)  )  If we publish this as an IETF stream document, =
then I think it needs stronger clarification that it is not an IETF =
consensus doc than just its informational status.
>=20
>  FWIW, the IESG has discussed this in the context of other documents, =
and is looking at boilerplate that does not say that the document is a =
"product of the IETF", and makes it clear that the content is not a =
matter of IETF consensus.  If that sort of boilerplate was used, do you =
think that would be sufficient?
>=20

I think that would help, depending on the specific language. My concerns =
about change control, authoritative specs, etc might still apply =
depending on the boilerplate details.

Thanks!

Ben.



From ben@nostrum.com  Thu Jun 20 20:58:43 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F30B021E80FE; Thu, 20 Jun 2013 20:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wl4TTxIpQGuE; Thu, 20 Jun 2013 20:58:42 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E5D6E21E80FD; Thu, 20 Jun 2013 20:58:41 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5L3wcYg054943 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Jun 2013 22:58:38 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <BB60A472FABE3AE51CEFBE8C@JcK-HP8200.jck.com>
Date: Thu, 20 Jun 2013 22:58:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <50EEE929-781D-4181-ABC6-F05783FD55B9@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <CAC4RtVApoWxr-fBWvLnUUS=UxpBk_7+X07f4m85o_1nej=84EQ@mail.gmail.com> <BB60A472FABE3AE51CEFBE8C@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, draft-thornburgh-adobe-rtmfp.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 03:58:43 -0000

On Jun 20, 2013, at 10:12 PM, John C Klensin <john-ietf@jck.com> wrote:

> p.s. I started a much more detailed response to Ben, but I think
> the essence of it is above.  IMO, a discussion that amounts to
> whether or not an AD used bad judgment by choosing to sponsor an
> individual Informational submission (or whether ADs should have
> that power at all) should not become part of evaluating a
> particular document's appropriateness.

I certainly didn't mean this to be a discussion of AD judgement. I =
suspect this would not be the first time the IETF has published an =
informational RFC that describes a non-IETF protocol, so there's =
probably precedent for doing so. It might be worth discussing whether =
that's a good precedent.

I also recognize that the authors have done a _lot_ of work on this =
draft, so this entire discussion is probably a bit unfair to them. I =
actually do hope it gets published somewhere.

Thanks!

Ben.=

From brian.e.carpenter@gmail.com  Thu Jun 20 21:37:26 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 620B021E80FE for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 21:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63lLh7oA2Tyh for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 21:37:26 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id EC2E421E80FD for <gen-art@ietf.org>; Thu, 20 Jun 2013 21:37:25 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj3so7241224pad.14 for <gen-art@ietf.org>; Thu, 20 Jun 2013 21:37:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=jqo/o0UQlw8Eru1Y8r1D+vJbgiTjDt2MQusmk2ab4ig=; b=FcJUxkz8n1NWJ+LIxmJhRygRYfSneNUplCtuSKFGIXA96AdJBebcRpBxLQrZ5a1mOS 3kabv0/coQhcfCxaFYL1gyWUHXFDVFgcS0Ga6hQIAi2et439jkGuQPU32MHxiMiREdB5 bkeUV4r7PYDbCfrtfCrKZFVY9cyWK5wZmZ8RDHCdLUlsRUUu43b9QFgjsuKmvHxIFy8u DiNMQaooxFre7+N0+l3AYpvlAf11FJvxIqdipV7FSBea2gVh/+Khg1SNdzUbj+2yZVzQ xiP2QFi3Hd9Plw1dLH15/jMJ7pZ9rHiEcotn/z+9gdAH/3XywfEfbH7hUgXnGyjvxLY8 Om/w==
X-Received: by 10.66.102.6 with SMTP id fk6mr14789430pab.184.1371789445550; Thu, 20 Jun 2013 21:37:25 -0700 (PDT)
Received: from [192.168.178.20] (36.200.69.111.dynamic.snap.net.nz. [111.69.200.36]) by mx.google.com with ESMTPSA id v7sm3094525pbq.32.2013.06.20.21.37.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Jun 2013 21:37:24 -0700 (PDT)
Message-ID: <51C3D88D.5090500@gmail.com>
Date: Fri, 21 Jun 2013 16:37:33 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-avtcore-avp-codecs.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-avtcore-avp-codecs-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 04:37:26 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at <
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd or AD before posting a
new version of the draft.

Document: draft-ietf-avtcore-avp-codecs-02.txt
Reviewer: Brian Carpenter
Review Date: 2013-06-03
IETF LC End Date: 2013-06-11
IESG Telechat date: 2013-06-27

Summary:  Ready
--------

Comments:
---------

This removes a bit of cruft from an established standard, and that seems
like a good thing to do.

Nit:
----

According to normal practice, the abstract should also specifically mention RFC 3551:

"This document updates the RTP/AVP profile (RFC 3551)..."

From meral.shirazipour@ericsson.com  Thu Jun 20 22:54:17 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0042E21E8094 for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 22:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maM47gcjw-Fn for <gen-art@ietfa.amsl.com>; Thu, 20 Jun 2013 22:54:11 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9E85121E8088 for <gen-art@ietf.org>; Thu, 20 Jun 2013 22:54:11 -0700 (PDT)
X-AuditID: c618062d-b7f936d000004481-8d-51c3ea823c7f
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 61.73.17537.28AE3C15; Fri, 21 Jun 2013 07:54:10 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0328.009; Fri, 21 Jun 2013 01:54:09 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-alto-server-discovery.all@tools.ietf.org" <draft-ietf-alto-server-discovery.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-alto-server-discovery-08
Thread-Index: Ac5uQ5Jcdukpu2poTq+oriTNhtof4A==
Date: Fri, 21 Jun 2013 05:54:09 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A133F1E@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A133F1Eeusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyuXRPrG7Tq8OBBh0L9C1OfvjEbnH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSuj689HxoLzLhX79/QwNjAes+li5OSQEDCR OPFnASuELSZx4d56NhBbSOAoo8SGRs8uRi4gezmjxO2efnaQBJuAhcT238/BGkQEZjFKPFsD ZgsLeEg8O3meuYuRAyjuK3Fsvj1EiZ7E7T83mUFsFgFViZubLrCA2LwC3hInLiwE28UItPf7 qTVMIDazgLjErSfzmSDuEZBYsuc8M4QtKvHy8T+oO5UlljzZzwJRny/Rcv0DG8RMQYmTM5+w TGAUmoVk1CwkZbOQlEHEdSQW7P7EBmFrSyxb+JoZxj5z4DETsvgCRvZVjBylxalluelGBpsY gbFwTIJNdwfjnpeWhxilOViUxHlfntoVKCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoGx8smh pTmKDfwvOad9WNs2PZRX/2Nq4QPl+bm+/zNOeBzmmljHsWv1uZn+W/XuV5r8sq74WxgXYJZ0 mMNVuY6hWmznfcdU9azS5Iab21bUFpc9jDVeXy5rv3KR2uR1VhUiczZ+eyYovbJ/+/HPWUmH H8heMtA6mv3kdsBkpQpxsXUz1ONf1PkrsRRnJBpqMRcVJwIARDDu+FMCAAA=
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-alto-server-discovery-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 05:54:17 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A133F1Eeusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq  .

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-alto-server-discovery-08
Reviewer: Meral Shirazipour
Review Date: 2013-06-20
IETF LC End Date: 2013-06-20
IESG Telechat date: NA


Summary:
This draft is almost ready to be published as Standards Track RFC but I do =
have some comments.

Nits/editorial comments:
-[Page 4], 2nd line before last, "funcional"--typo-->"functional"
-[Page 5], Section 2, Point 2, "neccessary"--typo-->"necessary"
-[Page 5], 2nd paragraph before last, "whishes"--typo-->"wishes"
-[Page 5], last paragraph, "neccessarily"--typo-->"necessarily"
-[Page 6], Section 3.1.1.
"If DHCP-based discovery succeeds the software SHOULD inform the user that =
the user input has been ignored and replaced by information retrieved from =
the network."
Suggestion to put "," after "If DHCP-based discovery succeeds".
-[Page 8], Section 4, line 3, "mobilility"--typo-->"mobility"
-[Page 8], Section 4, paragraph 2, "familly"--typo-->"family"
-[Page 8], Section 4, paragraph 2, "familiy"--typo-->"family"
-[Page 9], last line, "corrsponding"--typo-->"corresponding"
-[Page 11], paragraph 3, "anormalities"--typo-->"abnormalities"
-[page 12]
"The security aspects of obtaining the domain name that is used for input t=
o the U-NAPTR process is described in respective documents, such as [RFC598=
6]."
Refers to more than one documents but only lists RFC5986. It would be bette=
r to either list the other documents or say "described in [RFC5986]."
-[Page 13], Section 7.2, Ref. [I-D.ietf-alto-protocol] points to older vers=
ion.
-[Page 13], Section 7.2, Ref. [I-D.kist-alto-3pdisc] points to older versio=
n.
-General, please consider spelling out acronyms when first used. Also using=
 a common way (first letters capital or not):
"network address translation (NAT)" versus "Virtual Private Network (VPN)"

Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A133F1Eeusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> &nbsp;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-alto-server-discovery-08<o:p></=
o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-06-20<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-06-20<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Standa=
rds Track RFC but I do have some comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], 2nd line before last, &quot;funcional&quo=
t;--typo--&gt;&quot;functional&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2, Point 2, &quot;neccessary&quot=
;--typo--&gt;&quot;necessary&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], 2nd paragraph before last, &quot;whishes&=
quot;--typo--&gt;&quot;wishes&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], last paragraph, &quot;neccessarily&quot;-=
-typo--&gt;&quot;necessarily&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 6], Section 3.1.1. <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;If DHCP-based discovery succeeds the software =
SHOULD inform the user that the user input has been ignored and replaced by=
 information retrieved from the network.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Suggestion to put &quot;,&quot; after &quot;If DHCP-=
based discovery succeeds&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 8], Section 4, line 3, &quot;mobilility&quot;=
--typo--&gt;&quot;mobility&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 8], Section 4, paragraph 2, &quot;familly&quo=
t;--typo--&gt;&quot;family&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 8], Section 4, paragraph 2, &quot;familiy&quo=
t;--typo--&gt;&quot;family&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 9], last line, &quot;corrsponding&quot;--typo=
--&gt;&quot;corresponding&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 11], paragraph 3, &quot;anormalities&quot;--t=
ypo--&gt;&quot;abnormalities&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[page 12]<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;The security aspects of obtaining the domain n=
ame that is used for input to the U-NAPTR process is described in respectiv=
e documents, such as [RFC5986].&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Refers to more than one documents but only lists RFC=
5986. It would be better to either list the other documents or say &quot;de=
scribed in [RFC5986].&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 13], Section 7.2, Ref. [I-D.ietf-alto-protoco=
l] points to older version.<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 13], Section 7.2, Ref. [I-D.kist-alto-3pdisc]=
 points to older version.<o:p></o:p></p>
<p class=3D"MsoNormal">-General, please consider spelling out acronyms when=
 first used. Also using a common way (first letters capital or not):<o:p></=
o:p></p>
<p class=3D"MsoNormal">&quot;network address translation (NAT)&quot; versus=
 &quot;Virtual Private Network (VPN)&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A133F1Eeusaamb107ericsso_--

From jmh@joelhalpern.com  Fri Jun 21 07:46:55 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B4121E8126 for <gen-art@ietfa.amsl.com>; Fri, 21 Jun 2013 07:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.444
X-Spam-Level: 
X-Spam-Status: No, score=-102.444 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6J3AgmQe7pj for <gen-art@ietfa.amsl.com>; Fri, 21 Jun 2013 07:46:50 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 89C9B21E8124 for <gen-art@ietf.org>; Fri, 21 Jun 2013 07:46:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 447AD1BCE4BC; Fri, 21 Jun 2013 07:46:47 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-231.clppva.east.verizon.net [70.106.134.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id B2AAA1BCE4B7; Fri, 21 Jun 2013 07:46:46 -0700 (PDT)
Message-ID: <51C46746.1080802@joelhalpern.com>
Date: Fri, 21 Jun 2013 10:46:30 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Yee <peter@akayla.com>
References: <019c01ce6e01$105176c0$30f46440$@akayla.com>
In-Reply-To: <019c01ce6e01$105176c0$30f46440$@akayla.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  review: draft-ietf-straw-b2bua-taxonomy-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 14:46:55 -0000

I am the assigned Gen-ART reviewer for this draft. For background on 
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments 
you may receive.

Document: draft-ietf-straw-b2bua-taxonomy-02
     A Taxonomy of Session Initiation Protocol (SIP)
         Back-to-Back User Agents
Reviewer: Joel M. Halpern
Review Date: 21-June-2013
IETF LC End Date: 01-July-2013
IESG Telechat date: N/A

Summary: This document is ready for publication as an Informational RFC.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A

From mthornbu@adobe.com  Fri Jun 21 14:35:55 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A26DD21F9E07; Fri, 21 Jun 2013 14:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbmM3J8yx4Mk; Fri, 21 Jun 2013 14:35:50 -0700 (PDT)
Received: from exprod6og127.obsmtp.com (exprod6og127.obsmtp.com [64.18.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id B497921F9DFE; Fri, 21 Jun 2013 14:35:37 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob127.postini.com ([64.18.5.12]) with SMTP ID DSNKUcTHH7OHa+vqd0cXdk4JBM+aak5t8y6y@postini.com; Fri, 21 Jun 2013 14:35:38 PDT
Received: from inner-relay-2.corp.adobe.com (mail-321.sea.adobe.com [153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5LLZOAI027283; Fri, 21 Jun 2013 14:35:25 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5LLZOw7015904; Fri, 21 Jun 2013 14:35:24 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Fri, 21 Jun 2013 14:35:23 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>
Date: Fri, 21 Jun 2013 14:35:19 -0700
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5uCtbZuRIVMk7LS0i+/E+T5vgcMwAoFJaA
Message-ID: <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
In-Reply-To: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 21 Jun 2013 17:30:21 -0700
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 21:35:55 -0000

hi Ben. thanks for your review. comments/replies inline.

> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Thursday, June 20, 2013 4:07 PM
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-thornburgh-adobe-rtmfp-07
> Reviewer: Ben Campbell
> Review Date:  2013-06-20
> IETF LC End Date: 2013-06-25
>=20
> Summary: This draft is almost ready for publication as an informational R=
FC. However, I have some
> concerns about the purpose and intended status of the document that I thi=
nk should be considered prior
> to publication.
>=20
>=20
> Note: This is an informational draft that describes what I understand to =
be an existing protocol as
> implemented by commercial products. Therefore, this review does not attem=
pt to evaluate the protocol
> itself. I assume the protocol is what it is, and it is not up to the IETF=
 to agree or disagree with
> it.
>=20
> *** Major issues:
>=20
> -- Why does this need to be published as an IETF stream RFC?  If I unders=
tand correctly, this
> documents an existing protocol as implemented by commercial products. I a=
gree with Martin's comment
> that there is value in publishing this sort of thing, but I applaud the A=
dobe and the author for
> publishing it so other implementations can interoperate with their produc=
ts. But that could have done
> that in an independent stream document, or even in an Adobe published doc=
ument. (Perhaps even in a
> prettier format ;-)  )  If we publish this as an IETF stream document, th=
en I think it needs stronger
> clarification that it is not an IETF consensus doc than just its informat=
ional status.

this memo documents an existing network transport protocol that is widely d=
eployed and in widespread use in the Internet.  we felt that the IETF commu=
nity (and in particular the participants in the Transport and Services Area=
) is the most appropriate community with which to share this work: 1) membe=
rs of this community have the necessary and relevant expertise not only to =
understand the protocol, but to make use of it potentially in new applicati=
ons beyond Flash; 2) it is a transport protocol similar in many ways to TCP=
 and SCTP and widely deployed and used; 3) Adobe is interested in pursuing =
standardization of this protocol (with all that entails) if there is commun=
ity interest, and the IETF is definitely the right place for that.

we are very grateful that Martin Stiemerling chose to sponsor this document=
.

with regard to comments in later messages in this thread, i'd be happy to i=
nclude some (IESG-supplied) boilerplate in the document to clarify that it =
is not the product of an IETF WG.  however, note that both the title and fi=
rst sentence of the Introduction indicate that this is "Adobe's blahblahbla=
h", consistent with other vendor-protocol RFCs and consistent with IESG edi=
torial insistence (as told to me by a former TSV AD).  see RFC 4332 and RFC=
 6802 for two examples of vendor-specific/supplied protocols.  see also the=
 IESG note in RFC 4332 as an example disclaimer that could be added.

> Along those lines:
>=20
> 	-- Is this document the authoritative specification? (I suspect not.) Wh=
o owns change control? I
> assume that to be Adobe and/or the authors. What expectation do readers o=
f this draft have that it
> represents the current version of RTMFP at any point in time?

this memo is the authoritative specification for Adobe's RTMFP.  Adobe owns=
 change control.  i believe the second and third paragraphs of the Introduc=
tion indicate to a reader that this draft represents RTMFP as deployed in t=
he named Adobe products at the time of writing.

> 	-- Under what circumstances would one desire to implement this? I can in=
fer that from the
> introduction, but it would be nice to see some sort of applicability stat=
ement making it explicitly
> clear that this is not an IETF protocol, and that one would implement it =
in order to interoperate with
> certain Adobe products. I know that some of this may be implied by the fa=
ct that this is informational
> rather than standards track. But I don't expect readers who are not IETF =
insiders to understand that
> subtlety without some explicit words to that effect. In particular, it wo=
uld be good to clarify the
> difference between this and the many "not quite accepted as standards tra=
ck by some working group"
> nature of a number of our informational RFCs that describe protocols.

i will expand on applicability beyond what i specify in the first paragraph=
 of the Introduction, in general terms such as the kinds of functionality w=
e use this protocol for in Flash. note that interoperation with certain Ado=
be products, such as Flash Player, requires additional information such as =
the Flash-specific Cryptography Profile and syntax/semantics of mapping Fla=
sh's "Real Time Messaging Protocol (RTMP)" messages onto RTMFP flows.  thes=
e Flash-specific profiles and mappings are application-layer for RTMFP, ana=
logous to HTTP over TCP.

> That all being said, this is overall a well written document. The rest of=
 my comments are mostly
> pedantic nits.
>=20
> *** Minor issues:
>=20
> -- section 1.2:
>=20
> I find the use of "MUST ONLY" confusing. I gather it means "you are _allo=
wed_ to do X only under
> certain conditions" rather than "you are _required_ to do X under certain=
 conditions." If correct, I
> think the words "MAY ONLY" would be more clear. If not, then I think the =
construct would be better
> handled using existing 2119 language.

you're not the first person to be confused by that construct. i will change=
 instances of "MUST ONLY" to "is allowed only if" (or similar) and remove t=
he definition for "MUST ONLY" from Section 1.2.

> -- section 3.2:
>=20
> Do I understand correctly that all endpoints are expected to be able to p=
resent certificates? Do you
> find that common in the field? I realize the nature of the certs will dep=
end on the security profiles.

yes, all endpoints have certificates. in the RTMFP-for-Flash world, these c=
ertificates are not X.509 certs, and are anonymous and ephemeral.

> -- sections 3.2 and 5
>=20
> Do I assume correctly that endpoints need a common crypto profile to comm=
unicate? Is there a
> repository where one might find crypto profile documentation? Is there a =
commonly implemented one to
> which this draft could refer?

yes, endpoints need a common cryptography profile to interoperate.  there i=
s no repository for crypto profile documentation at this time. currently, t=
here is one defined cryptography profile (the one used for Flash communicat=
ion) that is not publicly documented, because i do not yet have permission =
to publish it.  i (meaning me personally) hope that a memo documenting the =
crypto/application profile for Flash communication (as being a widely deplo=
yed and used profile for RTMFP) would also be published someday as an I-D a=
nd hopefully an Informational RFC.

> -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."
>=20
> Why not MUST? Will things not break if two endpoints do have the same ide=
ntity?

this should be "It is RECOMMENDED that multiple endpoints not have the same=
 identity."  if two endpoints have the same identity, then they will be ind=
istinguishable.  this will not break RTMFP, but might confuse an applicatio=
n.  that being said, there could potentially be reasons to have different e=
ndpoints with indistinguishable identities and that potential should not be=
 normatively prohibited.

> -- "Authenticity MAY comprise verifying an issuer signature chain in a pu=
blic key infrastructure"
>=20
> Is that really normative, or just an observation of fact?

that "MAY" should be "can".

> -- " Canonical Endpoint Discriminators for distinct identities SHOULD be =
distinct."
>=20
> What if they are not? Do things break? It might be worth making this a MU=
ST, or adding some additional
> guidance about what might happen if the SHOULD is violated.

i will add a note that if the canonical EPD is the same for two distinct id=
entities, then the "duplicate session" logic in section 3.5.1.1.1 (paragrap=
h 6 step 1) might abort a new opening session to the second identity, which=
 might not be desired.

> -- "A comparison function MAY comprise performing a lexicographic orderin=
g..."
>=20
> Is that really normative, or just an example of something one might do?

that "MAY" should be "can".

> -- "A test SHOULD comprise testing whether the certificates are identical=
."
>=20
> What if it doesn't? Also, what constitutes "identical"? All fields match =
values? Bitwise match?  Is it
> simply including the same identity or identities? Maybe an identity funct=
ion provided by the crypto
> profile?

again, that SHOULD should be reworded to RECOMMENDED.  i will change "ident=
ical" to "bitwise identical".

> -- 3.5, last paragraph:
>=20
> Can you offer guidance on reasonable buffer size and number ranges?

i assume you mean "3.4, last paragraph" (referring to packet reassembly buf=
fers).  i will add some guidance and a "for example".  the guidance will de=
pend on how that RTMFP will be used and the expected amount of resources av=
ailable to it.

> -- 3.5.1.1.1, 3rd paragraph:
>=20
> What are the consequences of having a tag with less than 8 bytes of lengt=
h? Is the SHOULD reasonable
> here?

both of those SHOULDs should be RECOMMENDEDs.

> -- 3.5.1.1.1 throughout, and following sections:
>=20
> Does the upper case AND have special meaning?

upper case is the closest to bold face available in this format.  the inten=
tion is to emphasize (since there are multiple conditionals) that all condi=
tionals are required to hold.

> -- 3.5.1.4, Deployment Note:
>=20
> How would a redirector know which endpoints might do this? Or should it n=
ever initiate a session?

this is guidance for designing and deploying an RTMFP system.  the redirect=
or wouldn't know -- the designer should design the system such that the des=
cribed circumstance doesn't happen (for example, by having the redirector n=
ever initiate a session).  this is properly a SHOULD NOT since doing so can=
 cause undesired behavior (as described).  it is not desirable to give a no=
rmative prohibition or recommendation against a redirector initiating any s=
essions.  i feel this paragraph gives the narrowest normative limitation an=
d an explanation for that limitation.

> -- 3.5.2:
>=20
> Do I infer correctly that two endpoints need not share the same congestio=
n control algorithm to
> communicate?

correct.  the timestamp echo facility, ack behavior (as described for flow =
receivers), and limitations on aggressiveness in 3.5.2/.* impose the normat=
ive envelope in which any congestion control algorithms should interoperate=
.

> -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next U=
ser Data chunk instead of a
> User Data chunk"
>=20
> I'm not sure why this needs to be normative, as I assume its just normal =
behavior. But if it does need
> to be normative, why not a MUST?  Can the far endpoint reasonably handle =
things if the SHOULD is
> violated?

this should be a RECOMMENDED.  the far end will work just fine if Next User=
 Data is never used.

> *** Nits/editorial comments:
>=20
> -- General: There's quite a bit of inconsistent use of third-person vs se=
cond-person language.

i will try to clean that up.

> -- 3.1: It would be nice to see the overview earlier in the draft. I foun=
d it difficult to read
> through all the data format stuff prior to section 3 putting them into co=
ntext.

others have commented that they'd prefer sections 2 and 3 to be swapped. i =
resisted that as this order ("here are the pieces" and then "here's how the=
y fit together") is my preferred way of explaining stuff.  also swapping th=
ose sections would be a huge editorial change which might have significant =
cross-reference and forward/back reference implications and could introduce=
 hard-to-detect errors into the spec.  however, i think i can move the over=
view (or a summary thereof) to earlier in the spec (probably in Section 1).

> -- 3.5.1.4, Deployment Note:
>=20
> s/which/that

good catch.

> -- 3.5.1.6, last paragraph:
>=20
> Which diagram? (An explicit cross-ref would help.)

oops. that paragraph used to be the postamble of the figure, so it obviousl=
y meant "this figure".  i'll change "the figure" to "Figure 17".

> -- 3.5.2:
>=20
> What is meant by "aggressive" in this context? Aggressive in avoiding con=
gestion, or aggressive in
> sending data?

aggressive in sending data. i'll make that clarification.

> -- 3.6.2.3.1 and subsequent sections:
>=20
> Does the all-caps "FIRST" have special meaning?

it is all-caps for typographical emphasis.

thank you!

-michael thornburgh

From barryleiba.mailing.lists@gmail.com  Sat Jun 22 07:34:44 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA00B21F9F7C; Sat, 22 Jun 2013 07:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.021
X-Spam-Level: 
X-Spam-Status: No, score=-102.021 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZK20FbIIacK; Sat, 22 Jun 2013 07:34:44 -0700 (PDT)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 084E021F9F71; Sat, 22 Jun 2013 07:34:43 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id jw11so7320602veb.4 for <multiple recipients>; Sat, 22 Jun 2013 07:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=KRBFsJgI0SVHjXQyMS+fLmbHHjiWkZjdXQoD6DpCEts=; b=xis+vxJTfp7iun148PVi/h6ScY4y9Ko/OQvTqgtTDAawJzp5Ir9VMac/ehtf6BkKkW 57W7SUqIfuscX7pi2eIJDgw4i5TSZhNCbjYaxyHWlmZtnweT2PivS6gQrYMf472yO+/q SeoFw0lDm9ClJCiKqBUlv/CpXpXxQ6QzbiKGGOjh/sHkgpe0zDyH+E6HVWNvKy8ZcY0z 3PiF69s9XRBODo+Wh/0d4qX9QgZK10zWQOwQHYdD+q4/5xXhldt73oEyyFaF3chbspyF ZadbWhU3ZpatDgSk9eP3xpTGcpjKXWNsUDd3HXpQvwhFPZqpKopurK+OI81LDE9/mynq UCEg==
MIME-Version: 1.0
X-Received: by 10.58.80.38 with SMTP id o6mr8164214vex.69.1371911682406; Sat, 22 Jun 2013 07:34:42 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.234.105 with HTTP; Sat, 22 Jun 2013 07:34:42 -0700 (PDT)
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
Date: Sat, 22 Jun 2013 10:34:42 -0400
X-Google-Sender-Auth: XKrVgptU8dNXkmrFjo_aM0nWUR0
Message-ID: <CAC4RtVAgH85b32jSfMqXqNYEgwUFy-fSXW9agtNzrM79muPKbw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Michael Thornburgh <mthornbu@adobe.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jun 2013 14:34:45 -0000

> you're not the first person to be confused by that construct. i will change instances of
> "MUST ONLY" to "is allowed only if" (or similar) and remove the definition for "MUST
> ONLY" from Section 1.2.

I think this is an excellent idea.  RFC 6919 aside (ahem), it's rarely
a good idea to try to define new 2119-ish key words.

Speaking of which (my comments after a bunch of quotes)...

>> -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."
>>
>> Why not MUST? Will things not break if two endpoints do have the same identity?
>
> this should be "It is RECOMMENDED that multiple endpoints not have the same
> identity."  if two endpoints have the same identity, then they will be indistinguishable.
> this will not break RTMFP, but might confuse an application.  that being said, there
> could potentially be reasons to have different endpoints with indistinguishable identities
> and that potential should not be normatively prohibited.
...
>> -- "A test SHOULD comprise testing whether the certificates are identical."
>>
>> What if it doesn't?
>
> again, that SHOULD should be reworded to RECOMMENDED.
...
>> -- 3.5.1.1.1, 3rd paragraph:
>>
>> What are the consequences of having a tag with less than 8 bytes of length?
>> Is the SHOULD reasonable here?
>
> both of those SHOULDs should be RECOMMENDEDs.
...
>> -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next
>> User Data chunk instead of a User Data chunk"
>>
>> I'm not sure why this needs to be normative, as I assume its just normal
>> behavior. But if it does need to be normative, why not a MUST?  Can the far
>> endpoint reasonably handle things if the SHOULD is violated?
>
> this should be a RECOMMENDED.  the far end will work just fine if Next User
> Data is never used.

In RFC 2119, "SHOULD" and "RECOMMENDED" are synonymous (they're just
covering different parts of speech; they fit differently into
sentences).  Changing "SHOULD" to "RECOMMENDED" (and, of course,
rewording the sentences accordingly) doesn't affect Ben's comments on
the points.

"MUST" means that the protocol will not work properly unless you do
this.  You just have to, without fail.

"SHOULD" (and "RECOMMENDED") is really only a *little* lighter: it
still means that the protocol requires that you do this, but that
there might be good reasons not to -- you have to fully understand
what will happen if you don't do this before you can consider not
doing it.

To my mind (and I consider this when I do IESG Evaluation on documents
with SHOULD), whenever a document uses SHOULD (or RECOMMENDED) it
needs to (one might say "SHOULD") make it very clear what will happen
if you don't do this, so that implementors can have that necessary
understanding.  Perhaps the protocol will fail in some unusual
situations.  Perhaps it will break compatibility with older clients.
Perhaps it will still work, but will adversely affect performance.

But without an explanation, there's no way for implementors to meet
the terms in RFC 2119:

   3. SHOULD   This word, or the adjective "RECOMMENDED", mean that
   there may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

If something is simply a suggested value or response, the text should
say it that way.  If it's a suggestion that really is a best-practice
recommendation that comes from a lot of experience with the protocol,
the text should say that, without the 2119 key words.

For the first item, in Section 3.2, for example, you say:

> this should be "It is RECOMMENDED that multiple endpoints not have the same
> identity."  if two endpoints have the same identity, then they will be indistinguishable.
> this will not break RTMFP, but might confuse an application.  that being said, there
> could potentially be reasons to have different endpoints with indistinguishable identities
> and that potential should not be normatively prohibited.

That might well be a valid "SHOULD".  Don't change it to "RECOMMENDED"
(or do, if you like), but put in the explanation that you have here.
It would be especially helpful if you can also include an example of a
reason, and/or say something about the consequences of the confusion
it will cause.

For the cases of 3.5.1.1.1 and 3.6.2.3.2, it seems that you don't want
2119 key words there at all: these look like recommendations (not in
the 2119 sense) that are based on what's been deployed already, and it
would simply be good to make that clear: "implementation experience
suggests [x]".

Barry

From ron.even.tlv@gmail.com  Sat Jun 22 08:00:50 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5371D21E8096; Sat, 22 Jun 2013 08:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UwNEO1RGmsHx; Sat, 22 Jun 2013 08:00:49 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id BBB1021E809D; Sat, 22 Jun 2013 08:00:48 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id y10so1353262wgg.0 for <multiple recipients>; Sat, 22 Jun 2013 08:00:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=O7jBQJr9+Dr8ETOW8TflQqn+bG3ZHNrcmFkdn6pbaSE=; b=iBQBwGGIZSj5PYb1OQkxvzpHEeHl5NjnzyKuDDhqojU0GiNtRE+IKvmXwGZEsIdsn7 EkWBxkz8Q6jdD328w1FQl/OtIYhW1pZJQS2PnLsqbsqvbl9XOibb1lN6FdIdr055waFa V2tmJvDnHudwckOp7BF+yjfoD1ZhztnC2JAAor67YFqHHtRwOvIIKpTOsaHqe+8k1oCS Rn+zqlnhCLCCvAzhs2vf8lCihWVhdyPjxtee8b6Qn9bMKWjz1tYGStdhUeiZzNQl7kof 2VWrSllY/ed9azlEs67OqmP3SOQ1JpYw0I/DKxuhhU7M7W8U25HCBrdZsK4ozFYlcKTO RZAg==
X-Received: by 10.194.21.138 with SMTP id v10mr4099076wje.16.1371913247865; Sat, 22 Jun 2013 08:00:47 -0700 (PDT)
Received: from RoniE ([109.67.214.161]) by mx.google.com with ESMTPSA id r9sm4502588wik.1.2013.06.22.08.00.45 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 22 Jun 2013 08:00:47 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-pkix-est.all@tools.ietf.org>
Date: Sat, 22 Jun 2013 17:59:23 +0300
Message-ID: <075901ce6f59$170f3c50$452db4f0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_075A_01CE6F72.3C5D37A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5vWRUE/TjBkahtSoWxzN6PYKJhyw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-pkix-est-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jun 2013 15:00:50 -0000

This is a multipart message in MIME format.

------=_NextPart_000_075A_01CE6F72.3C5D37A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-pkix-est-07

Reviewer: Roni Even

Review Date:2013-6-22

IETF LC End Date: 2013-6-24

IESG Telechat date: 2013-6-27

 

Summary: This draft is ready for publication as Standard track RFC.

 

This is not a comment, I read the draft and not being an expert in this area
I found it clear for me to read. The document structure made it easier to
read.

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.  In section 4.5.2 "to use the the secp384r1 elliptic curve" repeated
"the"

 


------=_NextPart_000_075A_01CE6F72.3C5D37A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:510795705;
	mso-list-type:hybrid;
	mso-list-template-ids:1559919828 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-pkix-est-07</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;6&#8211;22<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-6&#8211;24<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2013-6&#8211;27<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as Standard track RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>This is =
not a comment, I read the draft and not being an expert in this area I =
found it clear for me to read. The document structure made it easier to =
read.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>In section 4.5.2 =
&#8220;<span style=3D'font-family:"Courier New"'>to use the the =
secp384r1 elliptic curve&#8221; repeated =
&#8220;the&#8221;</span><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_075A_01CE6F72.3C5D37A0--


From brian.e.carpenter@gmail.com  Sun Jun 23 19:01:51 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B97921F9007 for <gen-art@ietfa.amsl.com>; Sun, 23 Jun 2013 19:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYYs42VzyG4Q for <gen-art@ietfa.amsl.com>; Sun, 23 Jun 2013 19:01:50 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id CE50921F8FB3 for <gen-art@ietf.org>; Sun, 23 Jun 2013 19:01:50 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id rl6so10284015pac.29 for <gen-art@ietf.org>; Sun, 23 Jun 2013 19:01:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; bh=rnQrnAcUXItuBkVIU4SDDmxbySArMNf8loCSgUCxA8k=; b=RQZhr7bTuoYkAk/B6T99zBF26mp/fhrsNNRP0emVLPPWp903eBbyDgGJ5HWAp64QBL p5Lx22gZFDTtTpT6NDGaXdAYpoafTJ4IikI47BjjboOnjt8yHwOtavof6sceJyiyM6cK y/pPncNtyOxchwHDHiznkKbEqy36LlfRra7wzQdDUUm5KGsd5lTPxZWOzKfJ+9a3/Cw/ vJg8JOozSsoUZWoOHBuhZAVIwljHbGBAmW8MYK91dA1dgHFJUEnVdrPWQ0cEa575UJxs jRaxhUAz+DMgXhmzXhqnYuOzJaPDMxzzuwsu8NxGcgPhKzxsTLWtFGJJTzKRtxQ9q7S/ D7vg==
X-Received: by 10.66.26.179 with SMTP id m19mr26316184pag.4.1372039310557; Sun, 23 Jun 2013 19:01:50 -0700 (PDT)
Received: from [192.168.178.22] (91.198.69.111.dynamic.snap.net.nz. [111.69.198.91]) by mx.google.com with ESMTPSA id dc3sm15643292pbc.9.2013.06.23.19.01.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Jun 2013 19:01:49 -0700 (PDT)
Message-ID: <51C7A88A.9080102@gmail.com>
Date: Mon, 24 Jun 2013 14:01:46 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ivov-xmpp-cusax.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [Gen-art] Gen-ART LC review of draft-ivov-xmpp-cusax-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 02:01:51 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ivov-xmpp-cusax-06.txt
Reviewer: Brian Carpenter
Review Date: 2013-06-24
IETF LC End Date: 2013-07-16
IESG Telechat date:

Summary:  Almost ready
--------

Comment:
--------

I have some issues, but I don't know whether to classify any of them as
major.

Issues:
-------

In Introduction:

"  As a result, a number of adopters have found themselves needing
   features that are not offered by any single-protocol solution, but
   that separately exist in SIP and XMPP implementations.  The idea of
   seamlessly using both protocols together would hence often appeal to
   service providers. "

A few paragraphs later, you discuss the case of an end user who would like
to use SIP and XMPP together with *different* service providers. I would suggest
ending this sentence with "appeal to service providers and users."

"  Finally, this document makes a further simplifying assumption by
   discussing only the use of a single client, not use of and
   coordination among multiple endpoints controlled by the same user
   (e.g., user agents running simultaneously on a laptop computer,
   tablet, and mobile phone)."

Hmm. Isn't that the normal case today, and your simplifying assumption
the exception? It's certainly extremely annoying to have different
contacts lists on different devices, for example. This seems like a
big gap in the model, with no hints on how it might be filled. (As big
as the gap between POP3 and IMAP, in some ways.)

In Client Bootstrap:

"  While it should be possible for CUSAX users to manually configure
   their separate SIP and XMPP accounts, service providers offering
   CUSAX services to users of dual-stack SIP/XMPP clients ought to
   provide means of online provisioning,..."

1. I would anyway expect my CUSAX client to come with a configuration
wizard, including a path to the online provisioning if available.

2. Is there any reason why SIP service providers and XMPP service
providers shouldn't individually provide on-line provisioning? You're
describing something close to a captive-customer scenario, rather than
encouraging an open approach to provisioning. The CUSAX client would
in any case have to deal with any inconsistencies in provisioning.

In Server-Side Setup:

"  In order for CUSAX to function properly, XMPP service administrators
   should make sure that at least one of the vCard [RFC6350] "tel"
   fields for each contact is properly populated with a SIP URI or a
   phone number when an XMPP protocol for vCard storage is used (e.g.,..."

How can they do that, given that users are normally responsible for
maintaining their contacts lists?

In Summary of Suggested Practices:

"  1.   By default, prefer SIP for audio and video, and XMPP for
        messaging and presence."

At the beginning of the Operation section, this seems to be stated as
a rule, not as a default (" Audio/video features however, are disabled
in the XMPP stack..."). Which is it?

In Security Considerations:

"  ... a CUSAX client might
   successfully negotiate Transport Layer Security (TLS) [RFC5246] when
   connecting to the XMPP aspect of the service but not when connecting
   to the SIP aspect.  Such mismatches could introduce the possibility
   of downgrade attacks."

I'd say *would* introduce the possibility. It would seem possible for a
bad actor to pick up authentication data from the insecure service and
exploit it to attack the secured service. Therefore,

"  User agent developers and service providers
   ought to ensure that such mismatches are avoided as much as possible."

seems a bit weak. Shouldn't the client also be *required* to alert the user
that the session as a whole is not secured?


From psaintan@cisco.com  Sun Jun 23 19:27:33 2013
Return-Path: <psaintan@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0098C11E8101 for <gen-art@ietfa.amsl.com>; Sun, 23 Jun 2013 19:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9OrdVb9zZS36 for <gen-art@ietfa.amsl.com>; Sun, 23 Jun 2013 19:27:28 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E7F4B21F9EBE for <gen-art@ietf.org>; Sun, 23 Jun 2013 19:27:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6497; q=dns/txt; s=iport; t=1372040848; x=1373250448; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=rc2pEFHXXo5SYrZ8VlCBrgKZQ4KJ5X3w2ha18y/9JZE=; b=YrgTNMstliTXp0A9KGOQF5jEI92agyyDb5Z1Y8LMLoA4Fn0cYPntCGCE ehKzqlH/wfe3+W1kFu1F4T5e7yYGZjuczzPpToVZ3072fmFLigQLfYoe+ E1jmgx9JGPgStKO9e9alQyPVLcUM0V50nn/bthPTGqkiQ7cEKqRk0T383 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAF+tx1GtJXG+/2dsb2JhbABbgwkxSb83fhZ0giMBAQEDATouEQULAgEIFA4UECERJQIEDgUIE4dhAwkGDK98DYhSjGiBO3kCMQeDAmEDk3GBa4MQineFJIMQgWk/
X-IronPort-AV: E=Sophos;i="4.87,925,1363132800"; d="scan'208";a="223456794"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-9.cisco.com with ESMTP; 24 Jun 2013 02:27:27 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r5O2RR2D024179 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 24 Jun 2013 02:27:27 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Sun, 23 Jun 2013 21:27:26 -0500
From: "Peter Saint-Andre (psaintan)" <psaintan@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: Gen-ART LC review of draft-ivov-xmpp-cusax-06.txt
Thread-Index: AQHOcH7ZG6KAf3dD/Eeyxk6ZXuJfyZlEd46A
Date: Mon, 24 Jun 2013 02:27:25 +0000
Message-ID: <1670FE635C32C34AAD005D960F1C501115C6F5EF@xmb-aln-x11.cisco.com>
References: <51C7A88A.9080102@gmail.com>
In-Reply-To: <51C7A88A.9080102@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.89.2.172]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2309D952FC6F8141BAD521482323F2FE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ivov-xmpp-cusax.all@tools.ietf.org" <draft-ivov-xmpp-cusax.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ivov-xmpp-cusax-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 02:27:33 -0000

Hi Brian, thanks for the review.

On Jun 23, 2013, at 8:01 PM, Brian E Carpenter <brian.e.carpenter@gmail.com=
>
 wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ivov-xmpp-cusax-06.txt
> Reviewer: Brian Carpenter
> Review Date: 2013-06-24
> IETF LC End Date: 2013-07-16
> IESG Telechat date:
>=20
> Summary:  Almost ready
> --------
>=20
> Comment:
> --------
>=20
> I have some issues, but I don't know whether to classify any of them as
> major.
>=20
> Issues:
> -------
>=20
> In Introduction:
>=20
> "  As a result, a number of adopters have found themselves needing
>   features that are not offered by any single-protocol solution, but
>   that separately exist in SIP and XMPP implementations.  The idea of
>   seamlessly using both protocols together would hence often appeal to
>   service providers. "
>=20
> A few paragraphs later, you discuss the case of an end user who would lik=
e
> to use SIP and XMPP together with *different* service providers.

Although that's out of scope for this document. We might address that scena=
rio in a future document.

>  I would suggest
> ending this sentence with "appeal to service providers and users."

Good point.
>=20
> "  Finally, this document makes a further simplifying assumption by
>   discussing only the use of a single client, not use of and
>   coordination among multiple endpoints controlled by the same user
>   (e.g., user agents running simultaneously on a laptop computer,
>   tablet, and mobile phone)."
>=20
> Hmm. Isn't that the normal case today, and your simplifying assumption
> the exception? It's certainly extremely annoying to have different
> contacts lists on different devices, for example. This seems like a
> big gap in the model, with no hints on how it might be filled. (As big
> as the gap between POP3 and IMAP, in some ways.)

At least in XMPP, you'd have the same contact list on all of those devices.=
 But we can word this more carefully.

>=20
> In Client Bootstrap:
>=20
> "  While it should be possible for CUSAX users to manually configure
>   their separate SIP and XMPP accounts, service providers offering
>   CUSAX services to users of dual-stack SIP/XMPP clients ought to
>   provide means of online provisioning,..."
>=20
> 1. I would anyway expect my CUSAX client to come with a configuration
> wizard, including a path to the online provisioning if available.

True.
>=20
> 2. Is there any reason why SIP service providers and XMPP service
> providers shouldn't individually provide on-line provisioning?

No.

(Something like the technology proposed at the aggsrv BoF in Orlando might =
help, too, but that's just a gleam in the eye at this point.)

>  You're
> describing something close to a captive-customer scenario,

We are indeed assuming that a dual-stack user agent would interact with a c=
ombined service (i.e., CUSAX on the client side and CUSAX on the server sid=
e).  I am not sure that a customer of such a service is a captive.

> rather than
> encouraging an open approach to provisioning.

As far as I can see, no open provisioning protocol is available yet. The af=
orementioned aggsrv approach might fit the bill. It's too early to say, but=
 we can at least mention the possibility that such a technology might be de=
veloped in the future.

> The CUSAX client would
> in any case have to deal with any inconsistencies in provisioning.

I'm not sure what actionable advice we can provide here, but I'll discuss w=
ith with my co-authors.
>=20
> In Server-Side Setup:
>=20
> "  In order for CUSAX to function properly, XMPP service administrators
>   should make sure that at least one of the vCard [RFC6350] "tel"
>   fields for each contact is properly populated with a SIP URI or a
>   phone number when an XMPP protocol for vCard storage is used (e.g.,..."
>=20
> How can they do that, given that users are normally responsible for
> maintaining their contacts lists?

When a user uploads their vCard (or, say, modifies it in a web interface), =
the server could apply automated checks or make the "tel" field mandatory.
>=20
> In Summary of Suggested Practices:
>=20
> "  1.   By default, prefer SIP for audio and video, and XMPP for
>        messaging and presence."
>=20
> At the beginning of the Operation section, this seems to be stated as
> a rule, not as a default (" Audio/video features however, are disabled
> in the XMPP stack..."). Which is it?

I'm not seeing a huge difference here -- the XMPP stack in the CUSAX user a=
gent might have audio/video capabilities, but typically those would be disa=
bled (disabled by default, but the user might be allowed to turn them on fo=
r certain kinds of contacts, etc.).

I suggest this change in the Operation section.

OLD
   Audio/video features however, are
   disabled in the XMPP stack, so any form of communication based on
   these features (e.g. direct calls, conferences, desktop streaming,
   etc.) will happen over SIP.

NEW
   Audio/video features however, would typically be
   disabled in the XMPP stack, so any form of communication based on
   these features (e.g. direct calls, conferences, desktop streaming,
   etc.) would happen over SIP.

>=20
> In Security Considerations:
>=20
> "  ... a CUSAX client might
>   successfully negotiate Transport Layer Security (TLS) [RFC5246] when
>   connecting to the XMPP aspect of the service but not when connecting
>   to the SIP aspect.  Such mismatches could introduce the possibility
>   of downgrade attacks."
>=20
> I'd say *would* introduce the possibility.

Yes, that's more accurate.

>  It would seem possible for a
> bad actor to pick up authentication data from the insecure service and
> exploit it to attack the secured service. Therefore,
>=20
> "  User agent developers and service providers
>   ought to ensure that such mismatches are avoided as much as possible."
>=20
> seems a bit weak. Shouldn't the client also be *required* to alert the us=
er
> that the session as a whole is not secured?
>=20

IMHO that would be advisable. Good catch.

Peter

--
Peter Saint-Andre
http://iwe.cisco.com/web/psaintan



From stpeter@stpeter.im  Mon Jun 24 07:30:32 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67E721E812B for <gen-art@ietfa.amsl.com>; Mon, 24 Jun 2013 07:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DyYfxT8nxL5g for <gen-art@ietfa.amsl.com>; Mon, 24 Jun 2013 07:30:21 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 4BFB421F9AE0 for <gen-art@ietf.org>; Mon, 24 Jun 2013 07:30:21 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 30E97412E2; Mon, 24 Jun 2013 08:30:33 -0600 (MDT)
Message-ID: <51C857FA.2050304@stpeter.im>
Date: Mon, 24 Jun 2013 08:30:18 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Peter Saint-Andre (psaintan)" <psaintan@cisco.com>
References: <51C7A88A.9080102@gmail.com> <1670FE635C32C34AAD005D960F1C501115C6F5EF@xmb-aln-x11.cisco.com>
In-Reply-To: <1670FE635C32C34AAD005D960F1C501115C6F5EF@xmb-aln-x11.cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ivov-xmpp-cusax.all@tools.ietf.org" <draft-ivov-xmpp-cusax.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ivov-xmpp-cusax-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 14:30:34 -0000

On 6/23/13 8:27 PM, Peter Saint-Andre (psaintan) wrote:
> Hi Brian, thanks for the review.

Here is a provisional diff that addresses your feedback:

https://github.com/emcho/cusax/commit/1c5e9d681748685360cc6677ea2e369b352e66db#draft-ivov-xmpp-cusax-07.xml

> 
> On Jun 23, 2013, at 8:01 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>  wrote:
> 
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ivov-xmpp-cusax-06.txt
>> Reviewer: Brian Carpenter
>> Review Date: 2013-06-24
>> IETF LC End Date: 2013-07-16
>> IESG Telechat date:
>>
>> Summary:  Almost ready
>> --------
>>
>> Comment:
>> --------
>>
>> I have some issues, but I don't know whether to classify any of them as
>> major.
>>
>> Issues:
>> -------
>>
>> In Introduction:
>>
>> "  As a result, a number of adopters have found themselves needing
>>   features that are not offered by any single-protocol solution, but
>>   that separately exist in SIP and XMPP implementations.  The idea of
>>   seamlessly using both protocols together would hence often appeal to
>>   service providers. "
>>
>> A few paragraphs later, you discuss the case of an end user who would like
>> to use SIP and XMPP together with *different* service providers.
> 
> Although that's out of scope for this document. We might address that scenario in a future document.
> 
>>  I would suggest
>> ending this sentence with "appeal to service providers and users."
> 
> Good point.
>>
>> "  Finally, this document makes a further simplifying assumption by
>>   discussing only the use of a single client, not use of and
>>   coordination among multiple endpoints controlled by the same user
>>   (e.g., user agents running simultaneously on a laptop computer,
>>   tablet, and mobile phone)."
>>
>> Hmm. Isn't that the normal case today, and your simplifying assumption
>> the exception? It's certainly extremely annoying to have different
>> contacts lists on different devices, for example. This seems like a
>> big gap in the model, with no hints on how it might be filled. (As big
>> as the gap between POP3 and IMAP, in some ways.)
> 
> At least in XMPP, you'd have the same contact list on all of those devices. But we can word this more carefully.
> 
>>
>> In Client Bootstrap:
>>
>> "  While it should be possible for CUSAX users to manually configure
>>   their separate SIP and XMPP accounts, service providers offering
>>   CUSAX services to users of dual-stack SIP/XMPP clients ought to
>>   provide means of online provisioning,..."
>>
>> 1. I would anyway expect my CUSAX client to come with a configuration
>> wizard, including a path to the online provisioning if available.
> 
> True.
>>
>> 2. Is there any reason why SIP service providers and XMPP service
>> providers shouldn't individually provide on-line provisioning?
> 
> No.
> 
> (Something like the technology proposed at the aggsrv BoF in Orlando might help, too, but that's just a gleam in the eye at this point.)
> 
>>  You're
>> describing something close to a captive-customer scenario,
> 
> We are indeed assuming that a dual-stack user agent would interact with a combined service (i.e., CUSAX on the client side and CUSAX on the server side).  I am not sure that a customer of such a service is a captive.
> 
>> rather than
>> encouraging an open approach to provisioning.
> 
> As far as I can see, no open provisioning protocol is available yet. The aforementioned aggsrv approach might fit the bill. It's too early to say, but we can at least mention the possibility that such a technology might be developed in the future.
> 
>> The CUSAX client would
>> in any case have to deal with any inconsistencies in provisioning.
> 
> I'm not sure what actionable advice we can provide here, but I'll discuss with with my co-authors.
>>
>> In Server-Side Setup:
>>
>> "  In order for CUSAX to function properly, XMPP service administrators
>>   should make sure that at least one of the vCard [RFC6350] "tel"
>>   fields for each contact is properly populated with a SIP URI or a
>>   phone number when an XMPP protocol for vCard storage is used (e.g.,..."
>>
>> How can they do that, given that users are normally responsible for
>> maintaining their contacts lists?
> 
> When a user uploads their vCard (or, say, modifies it in a web interface), the server could apply automated checks or make the "tel" field mandatory.
>>
>> In Summary of Suggested Practices:
>>
>> "  1.   By default, prefer SIP for audio and video, and XMPP for
>>        messaging and presence."
>>
>> At the beginning of the Operation section, this seems to be stated as
>> a rule, not as a default (" Audio/video features however, are disabled
>> in the XMPP stack..."). Which is it?
> 
> I'm not seeing a huge difference here -- the XMPP stack in the CUSAX user agent might have audio/video capabilities, but typically those would be disabled (disabled by default, but the user might be allowed to turn them on for certain kinds of contacts, etc.).
> 
> I suggest this change in the Operation section.
> 
> OLD
>    Audio/video features however, are
>    disabled in the XMPP stack, so any form of communication based on
>    these features (e.g. direct calls, conferences, desktop streaming,
>    etc.) will happen over SIP.
> 
> NEW
>    Audio/video features however, would typically be
>    disabled in the XMPP stack, so any form of communication based on
>    these features (e.g. direct calls, conferences, desktop streaming,
>    etc.) would happen over SIP.
> 
>>
>> In Security Considerations:
>>
>> "  ... a CUSAX client might
>>   successfully negotiate Transport Layer Security (TLS) [RFC5246] when
>>   connecting to the XMPP aspect of the service but not when connecting
>>   to the SIP aspect.  Such mismatches could introduce the possibility
>>   of downgrade attacks."
>>
>> I'd say *would* introduce the possibility.
> 
> Yes, that's more accurate.
> 
>>  It would seem possible for a
>> bad actor to pick up authentication data from the insecure service and
>> exploit it to attack the secured service. Therefore,
>>
>> "  User agent developers and service providers
>>   ought to ensure that such mismatches are avoided as much as possible."
>>
>> seems a bit weak. Shouldn't the client also be *required* to alert the user
>> that the session as a whole is not secured?
>>
> 
> IMHO that would be advisable. Good catch.
> 
> Peter
> 

From magnus.westerlund@ericsson.com  Mon Jun 24 07:51:41 2013
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0893811E8164; Mon, 24 Jun 2013 07:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.717
X-Spam-Level: 
X-Spam-Status: No, score=-103.717 tagged_above=-999 required=5 tests=[AWL=-2.318, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwneeBgJJct5; Mon, 24 Jun 2013 07:51:34 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD8521E8165; Mon, 24 Jun 2013 07:51:20 -0700 (PDT)
X-AuditID: c1b4fb38-b7fa16d0000027dd-96-51c85ce73591
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id DC.30.10205.7EC58C15; Mon, 24 Jun 2013 16:51:19 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Jun 2013 16:51:19 +0200
Message-ID: <51C85D02.1050907@ericsson.com>
Date: Mon, 24 Jun 2013 16:51:46 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1370477514.4596.9052.camel@mightyatom>
In-Reply-To: <1370477514.4596.9052.camel@mightyatom>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPLMWRmVeSWpSXmKPExsUyM+Jvre7zmBOBBtt2CVtc/HKE3eL4gR3s FldffWaxmLr8MYsDi8fXk+0sHkuW/GTy+HL5M1sAcxSXTUpqTmZZapG+XQJXxq/z09gLVqRX fGhLbGBcEdjFyMkhIWAi0Tp/CyuELSZx4d56ti5GLg4hgTOMEstnLWGCcJYzSqxqfcQGUsUr oC3x714PUIKDg0VAVeLY7giQMJuAhcTNH41gJaICwRJHtm9mgSgXlDg58wmYLSKgJrH56wNG EJtZoJtR4v1aXhBbWMBHYsuE1WA1QgLGEo+/vgc7iBPouLutXVDHSUpsedHODtGrJzHlagvU HHmJ5q2zmSF6tSUamjpYJzAKzUKyehaSlllIWhYwMq9i5ChOLU7KTTcy2MQIDOSDW35b7GC8 /NfmEKM0B4uSOO+nU7sChQTSE0tSs1NTC1KL4otKc1KLDzEycXBKNTC2x3IqGjfbNhd2Llu3 UfiWw863WwJmfZ5gNv9Z9SOZ5Zyt/JE+HW6va5bc5rJ/XW75VFXY+vGLfCkVIaEfu98+nGK1 S3zFrfxuX4vVs68Ghs06Ih7+qlSUZQofp7FF8Lqvwuk3nzd/+qqxxM/BqXtyGp+1h5G3tNFj 3vT7p5Vr7qZqLbVjb1JiKc5INNRiLipOBABeXH+6MgIAAA==
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 14:51:41 -0000

Elwyn,

Follow up on some of the nits that is not simply to implement or where I
disagree or want to provide feedback.

This email covers all issues up to and including Section 11. That is as
far as I have managed to process them yet. I will now handle over the
rest of this list to my co-authors.

On 2013-06-06 02:11, Elwyn Davies wrote:
> 
> s2.3, para 5:
>> The server should also regularly send every 5
>>     minutes the current media range in a PLAY_NOTIFY request.
> Shouldn't this be configurable?

As discussed in Section 13.5.2 the reasons for the picked time is the
following:

      The recommendation for sending updates every 5 minutes is due to
      any clock skew issues.  In 5 minutes the clock skew should not
      become too significant as this is not used for media playback and
      synchronization, only for determining which content is available
      to the user.

Yes, it can be configurable, and in fact 5 min is only the recommended
interval. So, if an implementation that have a good reason for something
else can do that. Do you have a reason why you think this should be
configurable?

But, if it should be rewritten, I think the acceptable range for within
to adjust it should be specified, like between 1 min and 2 hours.

> 
> s2.3, last para:
>> If the client waits too long
>>     before resuming the pause point, the content may no longer be
>>     available.  In this case the pause point will be adjusted to the end
>>     of the available media.
> I know this is a subjective choice, but I would have thought adjusting 
> to the beginning of the available media would be what the user expects.
> Later: Having read s13.4.1, I think this conflicts with (or is unclear) 
> compared with s13.4.1, para 2 which states that the pause point will be
> the oldest retained time - that is what I would have expected.

Yes, "end" in the above sentence is not quite right. My proposal is the
following:

In this case the pause point will be adjusted to the closest point in
the available media.


> 
> 
> s3.1, para 3:  Clearly there won't be any smaller type paras in the 
> ASCII version.. is there a PDF version that actually has smaller type?  
> The one I get from the repository doesn't seem to have any smaller type 
> paras.

I removed the "small type" as this is a remains from when the draft was
produced using LaTex and a PDF version was produced.

> 
> s4.4: An external reference to the relevant Society of Motion Picture 
> and Television Engineers standard (probably SMPTE 12M) ought to be 
> included to define things like "SMPTE 30 drop".  [Aside: 29.97 frames 
> per second?? Must be something to do with Never Twice the Same Color.  
> Oh, well,  a little research job for whan I am really bored.]

Yes, it is ST 12M-1 2008 that appears to be the relevant reference. Yes,
SMPTE 30 drop is a NTSC thing.

> 
> s4.9.1: There seems to be some confusion in this section between the
> values from the Seek-Style header and the values from the
> Media-Properties random access property.  The section says the values
> are from Seek-Style but they are actually from the random access
> property.  Presumably there was some intention to interelate the media
> capabilities and the play event policies?  Further this section has
> Random Access, Conditional Random Access, Return to Start and No
> Seeking.  This doesn't match exactly with either Seek-Style (RAP, CoRAP,
> First-Prior and Next) or Media-Properties (Random-Access, Beginning-Only
> and No-Seeking).

Yes, this was confused. Actual the Media-Properties headers values are a
distinct set. Then if doing random access then the Seek-Style policies
applies. This I propose to clarify by writing Section 4.9.1 as:

4.9.1.  Random Access and Seeking

   Random Access is the ability to specify and get media delivered from
   any point inside the content, an operation called seeking.  The
   Media-Properties header will indicate the general capability for a
   media resource to perform random access.  If random access is
   possible the actual behavior policy when seeking can be controlled
   using the Seek-Style header (Section 18.45).

   Random-Access:  The media is seekable to any out of a large number of
      points within the media.  Due to media encoding limitations, a
      particular point may not be reachable, but seeking to a point
      close by is enabled.  A floating point number of seconds may be
      provided to express the worst case distance between random access
      points.

   Beginning-Only:  Seeking is only possible to the beginning of the
      content.

   No-seeking:  Seeking is not possible at all.

> 
> s4.9.x: It would be desirable to use the parameter names in the same 
> form as they appear in s18 (e.g., Random-Access instead of Random 
> Access, No-Seeking instead of No seeking) both in the definitions 
> (s4.9.1 - s4.9.4) and the mapping (s4.9.5).

Yes, that is has been addressed.

> 
> 
> ss4.4/4.5/4.6: If I read the ABNF in s20.2.1 correctly, the unqualified 
> values "smpte", "npt" and "clock" are valid  in the Range parameter.  
> What is the meaning of such an unqualified value?

You are correct about that the basic definition in ABNF allows for
empty. The reason for this is the following stated in Section 18.38:

    It MAY be
   included in GET_PARAMETER requests from the client to the server with
   only a Range format and no value to request the current media
   position, whether the session is in Play or Ready state in the
   included format.



> 
> s5:  It would be sensible to note that the ABNF fragments in s5 and the 
> following sections match with the full syntax productions in s20.

I have added a note, but they are in fact equivalent, but not identical.
Thus I make it clear that that this is for information and the formal is
in section 20.2.2.


> 
> Table 3:  Proxy-Authorization (Section 18.34) doesn't appear in any of 
> the various header categorization tables [I must have better things to 
> do than checking they were all there :-( ].  I think it belongs here.

Sorry, for not having found this myself before. You noticing it missing,
was actually a larger inconsistency issue. It was missing in the ABNF also.

I have spent quite some time now to ensure that the ABNF, the tables in
Section 6-8 and the header description now align as they should
regarding category.


> s8.1.1, code 505:  HTTP code 505 is explicitly '*HTTP* version not 
> supported' - should there really be a separate code for 'RTSP version 
> not supported'?

Yes, but the import of HTTP response codes are their meaning not there
exact definition. Thus 505 is RTSP version not supported as listed in
table. That is also what section 17.5.6 defines it as.

> 
> s9: Is it deliberately left vague as to whether other message types 
> might have message bodies?

This is unnecessary vague. In attempt to clarify this I have proposed
the following rewrite of that paragraph:

The SET_PARAMETER and GET_PARAMETER request and response, and DESCRIBE
response is by this specification defined that they MAY have a message
body and its purpose. All 4xx and 5xx responses MAY also have a message
body to carry additional response information. A message body MAY occur
on any RTSP 2.0 request or response, but the content of the message body
MAY be ignored. Extensions to this specification can specify the purpose
and content of message bodies, including requireing their inclusion.

> 
> s10.2, para 6 and following note:  I can't see that the note following 
> para 6 can be justified: since the restriction on multiple connections 
> from a client to a server is only a SHOULD, an interoperable server MUST 
> be capable of handling multiple connections from a client unless the 
> server can explicitly send back a TOO MANY CONNECTIONS status.

See separate email

> 
> s10.6: RFC 3986 has capability for dealing with IP versions beyond 6... 
> should these be carried over into RTSP?  The IANA registry says they are.

I am uncertain what you want here? Yes, the URI format allows for future
definitions of literal IP address versions. However, RTSP does contain
explicit IPv4 and IPv6 address fields that aren't URIs. Thus, future IP
versions will require some extension definition to function.



> s10.7, para 3: Anti-synchronization measures such as are RECOMMENDED 
> here are usually MANDATORY. (Also applies to wait timer in last para of 
> this section).

Yes, I agree that they usually are. I personally have no issues making
them required. I think the Recommended formulation is really one of
these cases, do this or something even better or you will hang yourself
to be a bit blunt.

But, if I understand you, you think this paragraph should read:

An RTSP server or proxy in an overload situation must select the value
of the Retry-After header carefully and bearing in mind its current load
situation. It is REQUIRED to increase the timeout period in proportion
to the current load on the server, i.e., an increasing workload should
result in an increased length of the indicated unavailability. It is
REQUIRED to not send the same value in the Retry-After header to all
requesting proxies and clients, but to add a variation to the mean value
of the Retry-After header.

Objections to this?

> 
> s10.7, last para: Should the doubling of the wait timer have an upper limit?

Yes, I added an upper limit of 30 minutes. This is way beyond what any
human will accept, only robots will keep on going at this timeout value.
And I think that is large enough to avoid any issues.

I also propose to clarify the range for the variations and added the
classical 0.5 to 1.5 times the deterministic value.

Text proposal.

That timer MUST be doubled for each additional failure to connect or
receive response until the value exceeds 30 minutes when the timers
deterministic value may be set to 30 minutes. It is RECOMMENDED to not
set the same value in the timer for each scheduling, but instead to add
a variation to the mean value, resulting in picking a random value
within the range of 0.5 to 1.5 of the mean value.

> 
> s11, para 4: According to s22.1.3, play.basic, play.scale and play.speed
> are 'defined' in this draft.  The nearest thing to a definition of
> play.basic that I can find is the last sentence of para 4 in this
> section.  I am not convinced that I could produce an interoperable
> implementation of a server with this feature-tag with the one sentence
> 'definition'.  References to where play.xxx are defined would be useful
> (play.scale in s18.44, play.speed in s18.48).
> 

Hmmm, the other feature-tags than play.basic are pretty straightforward
and well contained. play-basic is really a minimal RTSP server
implementation according to the whole spec for media playback.

This can probably be more clearly expressed somewhere, but it can't
really be enumerated. Then we are back to the issue we had with RFC 2326
minimal implementation list that was incomplete and lacked a lot of
things really necessary.

This issue still haven't resulted in any changes to our source.


> s11, Supported (and Proxy-Supported) bullets: 
> OLD:
>          This results in the
>          receiver is learning the requester's feature support.
> NEW:
>          This results in the
>          receiver learning the requester's feature support 
>          relevant to the specified resource.
> [Note: I added 'specified resource' here and then thought about whether
> this made any sense.  It probably needs to be clearer what set of
> features are included in the Supported list for both requester and
> responder.  Are they restricted to those relevant to the specified
> resource that might of course be the whole server, proxy - or client?? -
> in which case there isn't an issue, but it might be a specific
> presentation - what happens then?  Affects s13.1, para 3 also.]

Actually, I don't think it is specific to the media resource. The issue
with making it specific to a media resource is that a RTSP client needs
to be able to look into the future and supply an answer for a media
resource it may not yet know sufficient to provide a tailored response
for. I think it is simpler and better to provide general capabilities in
the supported header and then later determine how well they apply for
the media resource itself.

We do have Media-Properties header to provide more details for what
specific media transformations a server can do when the support play.scale.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From suresh.krishnan@ericsson.com  Mon Jun 24 12:15:32 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74F8921E8170 for <gen-art@ietfa.amsl.com>; Mon, 24 Jun 2013 12:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HjxSej9nijFm for <gen-art@ietfa.amsl.com>; Mon, 24 Jun 2013 12:15:20 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2164021E8159 for <gen-art@ietf.org>; Mon, 24 Jun 2013 12:15:19 -0700 (PDT)
X-AuditID: c618062d-b7f936d000004481-54-51c89ac6f06d
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 94.07.17537.7CA98C15; Mon, 24 Jun 2013 21:15:19 +0200 (CEST)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC005.ericsson.se (147.117.188.87) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 24 Jun 2013 15:15:18 -0400
Received: from [164.48.125.47] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 24 Jun 2013 15:15:17 -0400
Message-ID: <51C89A1D.10404@ericsson.com>
Date: Mon, 24 Jun 2013 15:12:29 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: <draft-ietf-ipsecme-ad-vpn-problem.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFJMWRmVeSWpSXmKPExsUyuXRPuO7xWScCDb7+FLXo+HCdzeLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGoc/b2QsO81RsP3ScpYFxElcXIyeHhICJ xKore5ghbDGJC/fWs3UxcnEICRxllDh5v5kRwtnDKHH28CJ2CGcro8T6HfdYQVp4BTQlDq3f wgJiswioShy8vAbMZgMau2HnZyYQW1QgTOLDsiVMEPWCEidnPgGrERHIljj3fQHQHA4OYQEf iW3nAiGukJTY8qKdHcRmFtCTmHK1hRHClpfY/nYO2KVCQGu3rvnOOoFRYBaSqbOQtMxC0rKA kXkVI0dpcWpZbrqRwSZGYPgdk2DT3cG456XlIUZpDhYlcd6Xp3YFCgmkJ5akZqemFqQWxReV 5qQWH2Jk4uCUamBk+5Dxs31H2d0dG3znK9V3tL510Pm32aSI3fDCyZ3LHK5lGy/yX9wlqWTU bxxv9Ox77JvDKbOP/fncx3lygcDzXqnzC3OULYsmld3o27u0pPyJ+4q9DKoL/2n85NIRmsz/ tfq0u9XuQq/vOcfSH3BstZoRs9ng+kWHpo7/XBsCvXqLuhVY3+kpsRRnJBpqMRcVJwIAi8ew 6Q0CAAA=
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-ipsecme-ad-vpn-problem-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 19:15:32 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-ipsecme-ad-vpn-problem-07.txt
Reviewer: Suresh Krishnan
Review Date: 2013/06/24
IESG Telechat date: 2013/06/27

Summary: This draft is almost ready for publication as an Informational
RFC but I do have a few comments that the authors may want to consider.

Minor
=====

* Section 2.3

The following sentence is a bit confusing. How does a mobile user
connect to a new gateway without reinitiating a connection? Can you
please clarify or reword.

"The mobile user ought to be able to discover and then connect to the
current most efficient gateway without having to reinitiate the connection."

* Section 4.1. Requirement 5

Shouldn't there be a requirement here that states what kind of damage is
allowed and prohibited in case a hub node is compromised?

* Section 4.1. Requirement 12

It is unclear what this requirement means. Is the requirement for the
solution to integrate with multicast routing protocols to come up with a
different (and optimized) multicast ADVPN topology or to simply allow
the advpn to carry (flattened out) multicast traffic?

* Section 4.1. Requirement 14

Are there any special requirements that L3VPN poses on top of what is
required for carrying generic IP traffic? If so, can you elaborate here.

Thanks
Suresh



From jari.arkko@piuha.net  Tue Jun 25 03:20:02 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 757E421F9EF5 for <gen-art@ietfa.amsl.com>; Tue, 25 Jun 2013 03:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qUKXndfGTnw for <gen-art@ietfa.amsl.com>; Tue, 25 Jun 2013 03:19:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB0D21E8086 for <gen-art@ietf.org>; Tue, 25 Jun 2013 03:19:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EA72A2CC56; Tue, 25 Jun 2013 13:19:55 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NtXzsAfguXqD; Tue, 25 Jun 2013 13:19:55 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4A5222CC48; Tue, 25 Jun 2013 13:19:55 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3875E1@ESESSMB209.ericsson.se>
Date: Tue, 25 Jun 2013 13:19:54 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C87B8A1-13A2-4194-A6BD-560BE7B9F950@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B1C386F68@ESESSMB209.ericsson.se> <C15918F2FCDA0243A7C919DA7C4BE9940D13003A@xmb-aln-x01.cisco.com> <7594FB04B1934943A5C02806D1A2204B1C3875E1@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "Ali C. Begen \(abegen\)" <abegen@cisco.com>, "draft-ietf-avtcore-6222bis.all@tools.ietf.org" <draft-ietf-avtcore-6222bis.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-ietf-avtcore-6222bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 10:20:03 -0000

Christer, Ali - thank you for the review and the changes. I plan to =
ballot a No-Objection for this draft.

Jari


From jari.arkko@piuha.net  Tue Jun 25 03:24:43 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24B011E80E0; Tue, 25 Jun 2013 03:24:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ir+3P-DSHblI; Tue, 25 Jun 2013 03:24:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8716C21F9D4B; Tue, 25 Jun 2013 03:24:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D05172CC56; Tue, 25 Jun 2013 13:24:32 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJ3-HPecDH-A; Tue, 25 Jun 2013 13:24:32 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DD5802CC48; Tue, 25 Jun 2013 13:24:31 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <031901ce61a9$04af7ce0$0e0e76a0$@gmail.com>
Date: Tue, 25 Jun 2013 13:24:31 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1E1A8BF-088A-47A6-B4FE-A973586C7B0B@piuha.net>
References: <000301ce5c98$278d0220$76a70660$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com> <027001ce60b1$ba2ecbf0$2e8c63d0$@gmail.com> <D09DAE6B636851459F7575D146EFB54B2406EA58@008-AM1MPN1-025.mgdnok.nokia.com> <031901ce61a9$04af7ce0$0e0e76a0$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: Simo.Veikkolainen@nokia.com, ietf@ietf.org, gen-art@ietf.org, draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 10:24:43 -0000

Roni, Simo - thank you for the review and for addressing the issue. I =
plan to ballot a No-Objection for this draft.

Jari


From elwynd@folly.org.uk  Tue Jun 25 05:49:27 2013
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8579D21F9E82; Tue, 25 Jun 2013 05:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.952
X-Spam-Level: 
X-Spam-Status: No, score=-0.952 tagged_above=-999 required=5 tests=[AWL=-0.949, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktiq-NqsFxPg; Tue, 25 Jun 2013 05:49:23 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 092B621F96EB; Tue, 25 Jun 2013 05:49:23 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1UrSgP-0006o3-2u; Tue, 25 Jun 2013 13:49:17 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <51C85D02.1050907@ericsson.com>
References: <1370477514.4596.9052.camel@mightyatom> <51C85D02.1050907@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Organization: Folly Consulting
Date: Tue, 25 Jun 2013 13:47:46 +0100
Message-Id: <1372164466.4524.9526.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 12:49:27 -0000

Hi, Magnus.

Thanks for the (continuing) responses.

Some comments in line.

I look forward to the updated document!

/Elwyn

On Mon, 2013-06-24 at 16:51 +0200, Magnus Westerlund wrote:
> Elwyn,
>=20
> Follow up on some of the nits that is not simply to implement or where I
> disagree or want to provide feedback.
>=20
> This email covers all issues up to and including Section 11. That is as
> far as I have managed to process them yet. I will now handle over the
> rest of this list to my co-authors.
>=20
> On 2013-06-06 02:11, Elwyn Davies wrote:
> >=20
> > s2.3, para 5:
> >> The server should also regularly send every 5
> >>     minutes the current media range in a PLAY_NOTIFY request.
> > Shouldn't this be configurable?
>=20
> As discussed in Section 13.5.2 the reasons for the picked time is the
> following:
>=20
>       The recommendation for sending updates every 5 minutes is due to
>       any clock skew issues.  In 5 minutes the clock skew should not
>       become too significant as this is not used for media playback and
>       synchronization, only for determining which content is available
>       to the user.
>=20
> Yes, it can be configurable, and in fact 5 min is only the recommended
> interval. So, if an implementation that have a good reason for something
> else can do that. Do you have a reason why you think this should be
> configurable?
Standard review reaction to an apparently sensible but arbitrary fixed
parameter! =20
>=20
> But, if it should be rewritten, I think the acceptable range for within
> to adjust it should be specified, like between 1 min and 2 hours.

Suggest:
- adding 'approximately' ('send approximately every') and a ref to
s13.5.2 to s2.3.=20
- change s13.5.2:
OLD:
   In addition it is
   RECOMMENDED that the server sends these notifications every 5 minutes
   for time-progressing content to ensure the long-term stability of the
   client estimation and allowing for clock skew detection by the
   client.=20
NEW:
   In addition it is
   RECOMMENDED that the server sends these notifications approximately=20
   every 5 minutes
   for time-progressing content to ensure the long-term stability of the
   client estimation and allowing for clock skew detection by the
   client.  The time between notifications should be greater than 1 minute=20
   and less than 2 hours.

>=20
> >=20
> > s2.3, last para:
> >> If the client waits too long
> >>     before resuming the pause point, the content may no longer be
> >>     available.  In this case the pause point will be adjusted to the e=
nd
> >>     of the available media.
> > I know this is a subjective choice, but I would have thought adjusting=20
> > to the beginning of the available media would be what the user expects.
> > Later: Having read s13.4.1, I think this conflicts with (or is unclear)=
=20
> > compared with s13.4.1, para 2 which states that the pause point will be
> > the oldest retained time - that is what I would have expected.
>=20
> Yes, "end" in the above sentence is not quite right. My proposal is the
> following:
>=20
> In this case the pause point will be adjusted to the closest point in
> the available media.
>=20
Seems like a good choice.
>=20
> >=20
> >=20
> > s3.1, para 3:  Clearly there won't be any smaller type paras in the=20
> > ASCII version.. is there a PDF version that actually has smaller type? =
=20
> > The one I get from the repository doesn't seem to have any smaller type=
=20
> > paras.
>=20
> I removed the "small type" as this is a remains from when the draft was
> produced using LaTex and a PDF version was produced.

Fine.

>=20
> >=20
> > s4.4: An external reference to the relevant Society of Motion Picture=20
> > and Television Engineers standard (probably SMPTE 12M) ought to be=20
> > included to define things like "SMPTE 30 drop".  [Aside: 29.97 frames=20
> > per second?? Must be something to do with Never Twice the Same Color. =20
> > Oh, well,  a little research job for whan I am really bored.]
>=20
> Yes, it is ST 12M-1 2008 that appears to be the relevant reference. Yes,
> SMPTE 30 drop is a NTSC thing.

:-)

>=20
> >=20
> > s4.9.1: There seems to be some confusion in this section between the
> > values from the Seek-Style header and the values from the
> > Media-Properties random access property.  The section says the values
> > are from Seek-Style but they are actually from the random access
> > property.  Presumably there was some intention to interelate the media
> > capabilities and the play event policies?  Further this section has
> > Random Access, Conditional Random Access, Return to Start and No
> > Seeking.  This doesn't match exactly with either Seek-Style (RAP, CoRAP=
,
> > First-Prior and Next) or Media-Properties (Random-Access, Beginning-Onl=
y
> > and No-Seeking).
>=20
> Yes, this was confused. Actual the Media-Properties headers values are a
> distinct set. Then if doing random access then the Seek-Style policies
> applies. This I propose to clarify by writing Section 4.9.1 as:
>=20
> 4.9.1.  Random Access and Seeking
>=20
>    Random Access is the ability to specify and get media delivered=20
>    from any point inside the content, an operation called seeking.  The
     ^^^^^^^^^^^^^^^^^^^^^
Try: starting from any time instant within

>    Media-Properties header will indicate the general capability for a
>    media resource to perform random access.  If random access is
>    possible the actual behavior policy when seeking can be controlled
>    using the Seek-Style header (Section 18.45).
>=20
>    Random-Access:  The media is seekable to any out of a large number of
>       points within the media.  Due to media encoding limitations, a
>       particular point may not be reachable, but seeking to a point
>       close by is enabled.  A floating point number of seconds may be
>       provided to express the worst case distance between random access
>       points.
>=20
>    Beginning-Only:  Seeking is only possible to the beginning of the
>       content.
>=20
>    No-seeking:  Seeking is not possible at all.
>=20

Generally fine - small suggestion above.

>=20
> > s4.9.x: It would be desirable to use the parameter names in the same=20
> > form as they appear in s18 (e.g., Random-Access instead of Random=20
> > Access, No-Seeking instead of No seeking) both in the definitions=20
> > (s4.9.1 - s4.9.4) and the mapping (s4.9.5).
>=20
> Yes, that is has been addressed.
>=20
OK

> >=20
> >=20
> > ss4.4/4.5/4.6: If I read the ABNF in s20.2.1 correctly, the unqualified=
=20
> > values "smpte", "npt" and "clock" are valid  in the Range parameter. =20
> > What is the meaning of such an unqualified value?
>=20
> You are correct about that the basic definition in ABNF allows for
> empty. The reason for this is the following stated in Section 18.38:
>=20
>     It MAY be
>    included in GET_PARAMETER requests from the client to the server with
>    only a Range format and no value to request the current media
>    position, whether the session is in Play or Ready state in the
>    included format.
>=20
Two points:
- A suggestion: Make ss4.4/4.5/4.6 into subsections of a new s4.4.  Add
a bit of text in the new s4.4 saying that the range specifiers are used
in the RANGE header and pointing to s18.38 for the unqualified use.
(consistent with s2.7 which gives usage).
- An issue I hadn't spotted: I haven't checked but are the unqualified
values allowed in the SDP extension case (s20.3)?
>=20
>=20
> >=20
> > s5:  It would be sensible to note that the ABNF fragments in s5 and the=
=20
> > following sections match with the full syntax productions in s20.
>=20
> I have added a note, but they are in fact equivalent, but not identical.
> Thus I make it clear that that this is for information and the formal is
> in section 20.2.2.

OK

>=20
>=20
> >=20
> > Table 3:  Proxy-Authorization (Section 18.34) doesn't appear in any of=20
> > the various header categorization tables [I must have better things to=20
> > do than checking they were all there :-( ].  I think it belongs here.
>=20
> Sorry, for not having found this myself before. You noticing it missing,
> was actually a larger inconsistency issue. It was missing in the ABNF als=
o.

(I think I noted that later).

>=20
> I have spent quite some time now to ensure that the ABNF, the tables in
> Section 6-8 and the header description now align as they should
> regarding category.

Yes.. tedious job as I found out! Good!

>=20
>=20
> > s8.1.1, code 505:  HTTP code 505 is explicitly '*HTTP* version not=20
> > supported' - should there really be a separate code for 'RTSP version=20
> > not supported'?
>=20
> Yes, but the import of HTTP response codes are their meaning not there
> exact definition. Thus 505 is RTSP version not supported as listed in
> table. That is also what section 17.5.6 defines it as.

I won't push this one.

>=20
> >=20
> > s9: Is it deliberately left vague as to whether other message types=20
> > might have message bodies?
>=20
> This is unnecessary vague. In attempt to clarify this I have proposed
> the following rewrite of that paragraph:
>=20
> The SET_PARAMETER and GET_PARAMETER request and response, and DESCRIBE
> response is by this specification defined that they MAY have a message
> body and its purpose. All 4xx and 5xx responses MAY also have a message
> body to carry additional response information. A message body MAY occur
> on any RTSP 2.0 request or response, but the content of the message body
> MAY be ignored. Extensions to this specification can specify the purpose
> and content of message bodies, including requireing their inclusion.

Seems sensible. Editorial update:
The SET_PARAMETER and GET_PARAMETER requests and responses, and the
DESCRIBE response as defined by this specification MAY have a message
body; the purpose of the message body is defined in each case. All 4xx
and 5xx responses MAY also have a message body to carry additional
response information. Generally a message body MAY be attached to any
RTSP 2.0 request or response, but the content of the message body
MAY be ignored by the receiver. Extensions to this specification can
specify the purpose and content of message bodies, including requiring
their inclusion.
>=20
>=20
> >=20
> > s10.2, para 6 and following note:  I can't see that the note following=20
> > para 6 can be justified: since the restriction on multiple connections=20
> > from a client to a server is only a SHOULD, an interoperable server MUS=
T=20
> > be capable of handling multiple connections from a client unless the=20
> > server can explicitly send back a TOO MANY CONNECTIONS status.
>=20
> See separate email

Should I have had this already?

>=20
> >=20
> > s10.6: RFC 3986 has capability for dealing with IP versions beyond 6...=
=20
> > should these be carried over into RTSP?  The IANA registry says they ar=
e.
>=20
> I am uncertain what you want here? Yes, the URI format allows for future
> definitions of literal IP address versions. However, RTSP does contain
> explicit IPv4 and IPv6 address fields that aren't URIs. Thus, future IP
> versions will require some extension definition to function.

Perhaps an excess of zeal on my behalf.  Perhaps a (non-normative) note
saying what you just wrote: 'Although the general URI format envisages=20
potential future new versions of the literal IP address, usage of any
such new version would require other modifications to the RTSP
specofication (e.g., ...[any relevant section(s)]).'=20
>=20
>=20
>=20
> > s10.7, para 3: Anti-synchronization measures such as are RECOMMENDED=20
> > here are usually MANDATORY. (Also applies to wait timer in last para of=
=20
> > this section).
>=20
> Yes, I agree that they usually are. I personally have no issues making
> them required. I think the Recommended formulation is really one of
> these cases, do this or something even better or you will hang yourself
> to be a bit blunt.
>=20
> But, if I understand you, you think this paragraph should read:
>=20
> An RTSP server or proxy in an overload situation must select the value
> of the Retry-After header carefully and bearing in mind its current load
> situation. It is REQUIRED to increase the timeout period in proportion
> to the current load on the server, i.e., an increasing workload should
> result in an increased length of the indicated unavailability. It is
> REQUIRED to not send the same value in the Retry-After header to all
> requesting proxies and clients, but to add a variation to the mean value
> of the Retry-After header.
>=20
> Objections to this?

I was only really concerned about the variation.  I would leave the 'how
much to increase' as a RECOMMENDED, but say there MUST be variation in
the retry values sent to different clients if theye are sent at all.

>=20
> >=20
> > s10.7, last para: Should the doubling of the wait timer have an upper l=
imit?
>=20
> Yes, I added an upper limit of 30 minutes. This is way beyond what any
> human will accept, only robots will keep on going at this timeout value.
> And I think that is large enough to avoid any issues.

Agreed

>=20
> I also propose to clarify the range for the variations and added the
> classical 0.5 to 1.5 times the deterministic value.
>=20
> Text proposal.
>=20
> That timer MUST be doubled for each additional failure to connect or
> receive response until the value exceeds 30 minutes when the timers
> deterministic value may be set to 30 minutes. It is RECOMMENDED to not
  ^^^^^^^^^^^^^
  base?
> set the same value in the timer for each scheduling, but instead to add
> a variation to the mean value, resulting in picking a random value
> within the range of 0.5 to 1.5 of the mean value.
>=20
> >=20
> > s11, para 4: According to s22.1.3, play.basic, play.scale and play.spee=
d
> > are 'defined' in this draft.  The nearest thing to a definition of
> > play.basic that I can find is the last sentence of para 4 in this
> > section.  I am not convinced that I could produce an interoperable
> > implementation of a server with this feature-tag with the one sentence
> > 'definition'.  References to where play.xxx are defined would be useful
> > (play.scale in s18.44, play.speed in s18.48).
> >=20
>=20
> Hmmm, the other feature-tags than play.basic are pretty straightforward
> and well contained. play-basic is really a minimal RTSP server
> implementation according to the whole spec for media playback.
>=20
> This can probably be more clearly expressed somewhere, but it can't
> really be enumerated. Then we are back to the issue we had with RFC 2326
> minimal implementation list that was incomplete and lacked a lot of
> things really necessary.
>=20
> This issue still haven't resulted in any changes to our source.

Ah!  I see I have (re-)opened a can of worms!  One thought for providing
the proverbial larger can into which the worms can be stuffed back:

Define 'play.basic' as the default that you get back if none of the
others apply.  How's that for weasel words!
>=20
>=20
> > s11, Supported (and Proxy-Supported) bullets:=20
> > OLD:
> >          This results in the
> >          receiver is learning the requester's feature support.
> > NEW:
> >          This results in the
> >          receiver learning the requester's feature support=20
> >          relevant to the specified resource.
> > [Note: I added 'specified resource' here and then thought about whether
> > this made any sense.  It probably needs to be clearer what set of
> > features are included in the Supported list for both requester and
> > responder.  Are they restricted to those relevant to the specified
> > resource that might of course be the whole server, proxy - or client?? =
-
> > in which case there isn't an issue, but it might be a specific
> > presentation - what happens then?  Affects s13.1, para 3 also.]
>=20
> Actually, I don't think it is specific to the media resource. The issue
> with making it specific to a media resource is that a RTSP client needs
> to be able to look into the future and supply an answer for a media
> resource it may not yet know sufficient to provide a tailored response
> for. I think it is simpler and better to provide general capabilities in
> the supported header and then later determine how well they apply for
> the media resource itself.

So maybe make it clear that feature support returned is just what the
responder can do generally and is not specific to the URI provided.

Either that or make the request valid only for non-specific URIs (i.e.
at the server/client level) if that is possible (not sure how that would
work for server asking client if that is allowed).
>=20
> We do have Media-Properties header to provide more details for what
> specific media transformations a server can do when the support play.scal=
e.

Right.


/Elwyn

>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mthornbu@adobe.com  Tue Jun 25 12:03:17 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9322411E8127; Tue, 25 Jun 2013 12:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.19
X-Spam-Level: 
X-Spam-Status: No, score=-6.19 tagged_above=-999 required=5 tests=[AWL=0.409,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNx59Z5YSi6g; Tue, 25 Jun 2013 12:03:12 -0700 (PDT)
Received: from exprod6og125.obsmtp.com (exprod6og125.obsmtp.com [64.18.1.218]) by ietfa.amsl.com (Postfix) with ESMTP id A76FA21E80CE; Tue, 25 Jun 2013 12:02:49 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob125.postini.com ([64.18.5.12]) with SMTP ID DSNKUcnpWPQKiupo8VqxN3hqCsTKJn7aDI5B@postini.com; Tue, 25 Jun 2013 12:02:55 PDT
Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5PIxSD8010923; Tue, 25 Jun 2013 11:59:28 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5PJ2mw7003179; Tue, 25 Jun 2013 12:02:48 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Tue, 25 Jun 2013 12:02:48 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: IETF-Discussion list <ietf@ietf.org>, "<gen-art@ietf.org> Team" <gen-art@ietf.org>, Ben Campbell <ben@nostrum.com>
Date: Tue, 25 Jun 2013 12:02:45 -0700
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5uCtbZuRIVMk7LS0i+/E+T5vgcMwAoFJaAAMp4DhA=
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AAC6F@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 19:03:17 -0000

hi Ben, all.

i have uploaded a new revision -08 of this draft that addresses comments ra=
ised during the IETF Last Call, which has now concluded.

Ben: i believe the "second-person" voice in this memo is used exclusively f=
or detailing algorithms that are to be performed. i believe the imperative =
"do it like this" voice is appropriate to that use, so i did not change it.=
  i also feel that the change in voice helps indicate that the implementati=
on is being addressed/instructed.

thank you for helping to improve the quality of this document.

-michael thornburgh


> From: Michael Thornburgh
> Sent: Friday, June 21, 2013 2:35 PM
>=20
> hi Ben. thanks for your review. comments/replies inline.
>=20
> > From: Ben Campbell [mailto:ben@nostrum.com]
> > Sent: Thursday, June 20, 2013 4:07 PM
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document:  draft-thornburgh-adobe-rtmfp-07
> > Reviewer: Ben Campbell
> > Review Date:  2013-06-20
> > IETF LC End Date: 2013-06-25
> >
> > Summary: This draft is almost ready for publication as an informational=
 RFC. However, I have some
> > concerns about the purpose and intended status of the document that I t=
hink should be considered
> prior
> > to publication.
> >
> >
> > Note: This is an informational draft that describes what I understand t=
o be an existing protocol as
> > implemented by commercial products. Therefore, this review does not att=
empt to evaluate the protocol
> > itself. I assume the protocol is what it is, and it is not up to the IE=
TF to agree or disagree with
> > it.
> >
> > *** Major issues:
> >
> > -- Why does this need to be published as an IETF stream RFC?  If I unde=
rstand correctly, this
> > documents an existing protocol as implemented by commercial products. I=
 agree with Martin's comment
> > that there is value in publishing this sort of thing, but I applaud the=
 Adobe and the author for
> > publishing it so other implementations can interoperate with their prod=
ucts. But that could have
> done
> > that in an independent stream document, or even in an Adobe published d=
ocument. (Perhaps even in a
> > prettier format ;-)  )  If we publish this as an IETF stream document, =
then I think it needs
> stronger
> > clarification that it is not an IETF consensus doc than just its inform=
ational status.
>=20
> this memo documents an existing network transport protocol that is widely=
 deployed and in widespread
> use in the Internet.  we felt that the IETF community (and in particular =
the participants in the
> Transport and Services Area) is the most appropriate community with which=
 to share this work: 1)
> members of this community have the necessary and relevant expertise not o=
nly to understand the
> protocol, but to make use of it potentially in new applications beyond Fl=
ash; 2) it is a transport
> protocol similar in many ways to TCP and SCTP and widely deployed and use=
d; 3) Adobe is interested in
> pursuing standardization of this protocol (with all that entails) if ther=
e is community interest, and
> the IETF is definitely the right place for that.
>=20
> we are very grateful that Martin Stiemerling chose to sponsor this docume=
nt.
>=20
> with regard to comments in later messages in this thread, i'd be happy to=
 include some (IESG-supplied)
> boilerplate in the document to clarify that it is not the product of an I=
ETF WG.  however, note that
> both the title and first sentence of the Introduction indicate that this =
is "Adobe's blahblahblah",
> consistent with other vendor-protocol RFCs and consistent with IESG edito=
rial insistence (as told to
> me by a former TSV AD).  see RFC 4332 and RFC 6802 for two examples of ve=
ndor-specific/supplied
> protocols.  see also the IESG note in RFC 4332 as an example disclaimer t=
hat could be added.
>=20
> > Along those lines:
> >
> > 	-- Is this document the authoritative specification? (I suspect not.) =
Who owns change control? I
> > assume that to be Adobe and/or the authors. What expectation do readers=
 of this draft have that it
> > represents the current version of RTMFP at any point in time?
>=20
> this memo is the authoritative specification for Adobe's RTMFP.  Adobe ow=
ns change control.  i believe
> the second and third paragraphs of the Introduction indicate to a reader =
that this draft represents
> RTMFP as deployed in the named Adobe products at the time of writing.
>=20
> > 	-- Under what circumstances would one desire to implement this? I can =
infer that from the
> > introduction, but it would be nice to see some sort of applicability st=
atement making it explicitly
> > clear that this is not an IETF protocol, and that one would implement i=
t in order to interoperate
> with
> > certain Adobe products. I know that some of this may be implied by the =
fact that this is
> informational
> > rather than standards track. But I don't expect readers who are not IET=
F insiders to understand that
> > subtlety without some explicit words to that effect. In particular, it =
would be good to clarify the
> > difference between this and the many "not quite accepted as standards t=
rack by some working group"
> > nature of a number of our informational RFCs that describe protocols.
>=20
> i will expand on applicability beyond what i specify in the first paragra=
ph of the Introduction, in
> general terms such as the kinds of functionality we use this protocol for=
 in Flash. note that
> interoperation with certain Adobe products, such as Flash Player, require=
s additional information such
> as the Flash-specific Cryptography Profile and syntax/semantics of mappin=
g Flash's "Real Time
> Messaging Protocol (RTMP)" messages onto RTMFP flows.  these Flash-specif=
ic profiles and mappings are
> application-layer for RTMFP, analogous to HTTP over TCP.
>=20
> > That all being said, this is overall a well written document. The rest =
of my comments are mostly
> > pedantic nits.
> >
> > *** Minor issues:
> >
> > -- section 1.2:
> >
> > I find the use of "MUST ONLY" confusing. I gather it means "you are _al=
lowed_ to do X only under
> > certain conditions" rather than "you are _required_ to do X under certa=
in conditions." If correct, I
> > think the words "MAY ONLY" would be more clear. If not, then I think th=
e construct would be better
> > handled using existing 2119 language.
>=20
> you're not the first person to be confused by that construct. i will chan=
ge instances of "MUST ONLY"
> to "is allowed only if" (or similar) and remove the definition for "MUST =
ONLY" from Section 1.2.
>=20
> > -- section 3.2:
> >
> > Do I understand correctly that all endpoints are expected to be able to=
 present certificates? Do you
> > find that common in the field? I realize the nature of the certs will d=
epend on the security
> profiles.
>=20
> yes, all endpoints have certificates. in the RTMFP-for-Flash world, these=
 certificates are not X.509
> certs, and are anonymous and ephemeral.
>=20
> > -- sections 3.2 and 5
> >
> > Do I assume correctly that endpoints need a common crypto profile to co=
mmunicate? Is there a
> > repository where one might find crypto profile documentation? Is there =
a commonly implemented one to
> > which this draft could refer?
>=20
> yes, endpoints need a common cryptography profile to interoperate.  there=
 is no repository for crypto
> profile documentation at this time. currently, there is one defined crypt=
ography profile (the one used
> for Flash communication) that is not publicly documented, because i do no=
t yet have permission to
> publish it.  i (meaning me personally) hope that a memo documenting the c=
rypto/application profile for
> Flash communication (as being a widely deployed and used profile for RTMF=
P) would also be published
> someday as an I-D and hopefully an Informational RFC.
>=20
> > -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity."
> >
> > Why not MUST? Will things not break if two endpoints do have the same i=
dentity?
>=20
> this should be "It is RECOMMENDED that multiple endpoints not have the sa=
me identity."  if two
> endpoints have the same identity, then they will be indistinguishable.  t=
his will not break RTMFP, but
> might confuse an application.  that being said, there could potentially b=
e reasons to have different
> endpoints with indistinguishable identities and that potential should not=
 be normatively prohibited.
>=20
> > -- "Authenticity MAY comprise verifying an issuer signature chain in a =
public key infrastructure"
> >
> > Is that really normative, or just an observation of fact?
>=20
> that "MAY" should be "can".
>=20
> > -- " Canonical Endpoint Discriminators for distinct identities SHOULD b=
e distinct."
> >
> > What if they are not? Do things break? It might be worth making this a =
MUST, or adding some
> additional
> > guidance about what might happen if the SHOULD is violated.
>=20
> i will add a note that if the canonical EPD is the same for two distinct =
identities, then the
> "duplicate session" logic in section 3.5.1.1.1 (paragraph 6 step 1) might=
 abort a new opening session
> to the second identity, which might not be desired.
>=20
> > -- "A comparison function MAY comprise performing a lexicographic order=
ing..."
> >
> > Is that really normative, or just an example of something one might do?
>=20
> that "MAY" should be "can".
>=20
> > -- "A test SHOULD comprise testing whether the certificates are identic=
al."
> >
> > What if it doesn't? Also, what constitutes "identical"? All fields matc=
h values? Bitwise match?  Is
> it
> > simply including the same identity or identities? Maybe an identity fun=
ction provided by the crypto
> > profile?
>=20
> again, that SHOULD should be reworded to RECOMMENDED.  i will change "ide=
ntical" to "bitwise
> identical".
>=20
> > -- 3.5, last paragraph:
> >
> > Can you offer guidance on reasonable buffer size and number ranges?
>=20
> i assume you mean "3.4, last paragraph" (referring to packet reassembly b=
uffers).  i will add some
> guidance and a "for example".  the guidance will depend on how that RTMFP=
 will be used and the
> expected amount of resources available to it.
>=20
> > -- 3.5.1.1.1, 3rd paragraph:
> >
> > What are the consequences of having a tag with less than 8 bytes of len=
gth? Is the SHOULD reasonable
> > here?
>=20
> both of those SHOULDs should be RECOMMENDEDs.
>=20
> > -- 3.5.1.1.1 throughout, and following sections:
> >
> > Does the upper case AND have special meaning?
>=20
> upper case is the closest to bold face available in this format.  the int=
ention is to emphasize (since
> there are multiple conditionals) that all conditionals are required to ho=
ld.
>=20
> > -- 3.5.1.4, Deployment Note:
> >
> > How would a redirector know which endpoints might do this? Or should it=
 never initiate a session?
>=20
> this is guidance for designing and deploying an RTMFP system.  the redire=
ctor wouldn't know -- the
> designer should design the system such that the described circumstance do=
esn't happen (for example, by
> having the redirector never initiate a session).  this is properly a SHOU=
LD NOT since doing so can
> cause undesired behavior (as described).  it is not desirable to give a n=
ormative prohibition or
> recommendation against a redirector initiating any sessions.  i feel this=
 paragraph gives the
> narrowest normative limitation and an explanation for that limitation.
>=20
> > -- 3.5.2:
> >
> > Do I infer correctly that two endpoints need not share the same congest=
ion control algorithm to
> > communicate?
>=20
> correct.  the timestamp echo facility, ack behavior (as described for flo=
w receivers), and limitations
> on aggressiveness in 3.5.2/.* impose the normative envelope in which any =
congestion control algorithms
> should interoperate.
>=20
> > -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a Next=
 User Data chunk instead of a
> > User Data chunk"
> >
> > I'm not sure why this needs to be normative, as I assume its just norma=
l behavior. But if it does
> need
> > to be normative, why not a MUST?  Can the far endpoint reasonably handl=
e things if the SHOULD is
> > violated?
>=20
> this should be a RECOMMENDED.  the far end will work just fine if Next Us=
er Data is never used.
>=20
> > *** Nits/editorial comments:
> >
> > -- General: There's quite a bit of inconsistent use of third-person vs =
second-person language.
>=20
> i will try to clean that up.
>=20
> > -- 3.1: It would be nice to see the overview earlier in the draft. I fo=
und it difficult to read
> > through all the data format stuff prior to section 3 putting them into =
context.
>=20
> others have commented that they'd prefer sections 2 and 3 to be swapped. =
i resisted that as this order
> ("here are the pieces" and then "here's how they fit together") is my pre=
ferred way of explaining
> stuff.  also swapping those sections would be a huge editorial change whi=
ch might have significant
> cross-reference and forward/back reference implications and could introdu=
ce hard-to-detect errors into
> the spec.  however, i think i can move the overview (or a summary thereof=
) to earlier in the spec
> (probably in Section 1).
>=20
> > -- 3.5.1.4, Deployment Note:
> >
> > s/which/that
>=20
> good catch.
>=20
> > -- 3.5.1.6, last paragraph:
> >
> > Which diagram? (An explicit cross-ref would help.)
>=20
> oops. that paragraph used to be the postamble of the figure, so it obviou=
sly meant "this figure".
> i'll change "the figure" to "Figure 17".
>=20
> > -- 3.5.2:
> >
> > What is meant by "aggressive" in this context? Aggressive in avoiding c=
ongestion, or aggressive in
> > sending data?
>=20
> aggressive in sending data. i'll make that clarification.
>=20
> > -- 3.6.2.3.1 and subsequent sections:
> >
> > Does the all-caps "FIRST" have special meaning?
>=20
> it is all-caps for typographical emphasis.
>=20
> thank you!
>=20
> -michael thornburgh

From brian.e.carpenter@gmail.com  Tue Jun 25 13:03:48 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A8421E80DC for <gen-art@ietfa.amsl.com>; Tue, 25 Jun 2013 13:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kGDNRBCGWsHw for <gen-art@ietfa.amsl.com>; Tue, 25 Jun 2013 13:03:47 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id DE56C21E80DA for <gen-art@ietf.org>; Tue, 25 Jun 2013 13:03:47 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kq13so13044906pab.25 for <gen-art@ietf.org>; Tue, 25 Jun 2013 13:03:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MpgJHrXosD0BZ8mSY72MIi7Loz2nFvQn7U+B+Xgz1NY=; b=09kkCgUphIpFWsyIf2RpB6Oz+yk/yytbXndZG8PM02Q6TGcgcfrbtCSpGcgaVBcUDp aW766RM+tuStlIeJQXubwXK2O+PM61jJ1C3MJQG/lzfULdXfTYs/LV1sHUcuWQMy2LY9 FpOsp918vJbLblIaoxu1cChme2SSl28BtkFZ0nk1lJhGTlVaimQK/gGbyeZmRZR6KG5y BmtpwvPv8ATP4mQIRrrWCOSUVPBe3cdz8vuH5/3jsg1xnBOhlc05eD65Hbd7XVrwh4Lk RH24cCLyVn5tOvDdH+Xb4hqTeXoGo/4TRLqKnvyD0AaeSo5+TYxXRwl8TKDo/vSquoUQ QWJw==
X-Received: by 10.66.141.175 with SMTP id rp15mr1264017pab.214.1372190626388;  Tue, 25 Jun 2013 13:03:46 -0700 (PDT)
Received: from [192.168.178.22] (15.198.69.111.dynamic.snap.net.nz. [111.69.198.15]) by mx.google.com with ESMTPSA id tt7sm24571915pbc.34.2013.06.25.13.03.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 13:03:45 -0700 (PDT)
Message-ID: <51C9F79F.2060509@gmail.com>
Date: Wed, 26 Jun 2013 08:03:43 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <51C7A88A.9080102@gmail.com> <1670FE635C32C34AAD005D960F1C501115C6F5EF@xmb-aln-x11.cisco.com> <51C857FA.2050304@stpeter.im>
In-Reply-To: <51C857FA.2050304@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "draft-ivov-xmpp-cusax.all@tools.ietf.org" <draft-ivov-xmpp-cusax.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ivov-xmpp-cusax-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 20:03:48 -0000

Hi Peter,

Thanks, that all seems fine in the light of your comments. I would
expect to review this as "Ready" when it reaches the IESG agenda.

Regards
   Brian

On 25/06/2013 02:30, Peter Saint-Andre wrote:
> On 6/23/13 8:27 PM, Peter Saint-Andre (psaintan) wrote:
>> Hi Brian, thanks for the review.
> 
> Here is a provisional diff that addresses your feedback:
> 
> https://github.com/emcho/cusax/commit/1c5e9d681748685360cc6677ea2e369b352e66db#draft-ivov-xmpp-cusax-07.xml
> 
>> On Jun 23, 2013, at 8:01 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>>  wrote:
>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please resolve these comments along with any other Last Call comments
>>> you may receive.
>>>
>>> Document: draft-ivov-xmpp-cusax-06.txt
>>> Reviewer: Brian Carpenter
>>> Review Date: 2013-06-24
>>> IETF LC End Date: 2013-07-16
>>> IESG Telechat date:
>>>
>>> Summary:  Almost ready
>>> --------
>>>
>>> Comment:
>>> --------
>>>
>>> I have some issues, but I don't know whether to classify any of them as
>>> major.
>>>
>>> Issues:
>>> -------
>>>
>>> In Introduction:
>>>
>>> "  As a result, a number of adopters have found themselves needing
>>>   features that are not offered by any single-protocol solution, but
>>>   that separately exist in SIP and XMPP implementations.  The idea of
>>>   seamlessly using both protocols together would hence often appeal to
>>>   service providers. "
>>>
>>> A few paragraphs later, you discuss the case of an end user who would like
>>> to use SIP and XMPP together with *different* service providers.
>> Although that's out of scope for this document. We might address that scenario in a future document.
>>
>>>  I would suggest
>>> ending this sentence with "appeal to service providers and users."
>> Good point.
>>> "  Finally, this document makes a further simplifying assumption by
>>>   discussing only the use of a single client, not use of and
>>>   coordination among multiple endpoints controlled by the same user
>>>   (e.g., user agents running simultaneously on a laptop computer,
>>>   tablet, and mobile phone)."
>>>
>>> Hmm. Isn't that the normal case today, and your simplifying assumption
>>> the exception? It's certainly extremely annoying to have different
>>> contacts lists on different devices, for example. This seems like a
>>> big gap in the model, with no hints on how it might be filled. (As big
>>> as the gap between POP3 and IMAP, in some ways.)
>> At least in XMPP, you'd have the same contact list on all of those devices. But we can word this more carefully.
>>
>>> In Client Bootstrap:
>>>
>>> "  While it should be possible for CUSAX users to manually configure
>>>   their separate SIP and XMPP accounts, service providers offering
>>>   CUSAX services to users of dual-stack SIP/XMPP clients ought to
>>>   provide means of online provisioning,..."
>>>
>>> 1. I would anyway expect my CUSAX client to come with a configuration
>>> wizard, including a path to the online provisioning if available.
>> True.
>>> 2. Is there any reason why SIP service providers and XMPP service
>>> providers shouldn't individually provide on-line provisioning?
>> No.
>>
>> (Something like the technology proposed at the aggsrv BoF in Orlando might help, too, but that's just a gleam in the eye at this point.)
>>
>>>  You're
>>> describing something close to a captive-customer scenario,
>> We are indeed assuming that a dual-stack user agent would interact with a combined service (i.e., CUSAX on the client side and CUSAX on the server side).  I am not sure that a customer of such a service is a captive.
>>
>>> rather than
>>> encouraging an open approach to provisioning.
>> As far as I can see, no open provisioning protocol is available yet. The aforementioned aggsrv approach might fit the bill. It's too early to say, but we can at least mention the possibility that such a technology might be developed in the future.
>>
>>> The CUSAX client would
>>> in any case have to deal with any inconsistencies in provisioning.
>> I'm not sure what actionable advice we can provide here, but I'll discuss with with my co-authors.
>>> In Server-Side Setup:
>>>
>>> "  In order for CUSAX to function properly, XMPP service administrators
>>>   should make sure that at least one of the vCard [RFC6350] "tel"
>>>   fields for each contact is properly populated with a SIP URI or a
>>>   phone number when an XMPP protocol for vCard storage is used (e.g.,..."
>>>
>>> How can they do that, given that users are normally responsible for
>>> maintaining their contacts lists?
>> When a user uploads their vCard (or, say, modifies it in a web interface), the server could apply automated checks or make the "tel" field mandatory.
>>> In Summary of Suggested Practices:
>>>
>>> "  1.   By default, prefer SIP for audio and video, and XMPP for
>>>        messaging and presence."
>>>
>>> At the beginning of the Operation section, this seems to be stated as
>>> a rule, not as a default (" Audio/video features however, are disabled
>>> in the XMPP stack..."). Which is it?
>> I'm not seeing a huge difference here -- the XMPP stack in the CUSAX user agent might have audio/video capabilities, but typically those would be disabled (disabled by default, but the user might be allowed to turn them on for certain kinds of contacts, etc.).
>>
>> I suggest this change in the Operation section.
>>
>> OLD
>>    Audio/video features however, are
>>    disabled in the XMPP stack, so any form of communication based on
>>    these features (e.g. direct calls, conferences, desktop streaming,
>>    etc.) will happen over SIP.
>>
>> NEW
>>    Audio/video features however, would typically be
>>    disabled in the XMPP stack, so any form of communication based on
>>    these features (e.g. direct calls, conferences, desktop streaming,
>>    etc.) would happen over SIP.
>>
>>> In Security Considerations:
>>>
>>> "  ... a CUSAX client might
>>>   successfully negotiate Transport Layer Security (TLS) [RFC5246] when
>>>   connecting to the XMPP aspect of the service but not when connecting
>>>   to the SIP aspect.  Such mismatches could introduce the possibility
>>>   of downgrade attacks."
>>>
>>> I'd say *would* introduce the possibility.
>> Yes, that's more accurate.
>>
>>>  It would seem possible for a
>>> bad actor to pick up authentication data from the insecure service and
>>> exploit it to attack the secured service. Therefore,
>>>
>>> "  User agent developers and service providers
>>>   ought to ensure that such mismatches are avoided as much as possible."
>>>
>>> seems a bit weak. Shouldn't the client also be *required* to alert the user
>>> that the session as a whole is not secured?
>>>
>> IMHO that would be advisable. Good catch.
>>
>> Peter
>>
> 

From stpeter@stpeter.im  Tue Jun 25 13:20:10 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B89E821E80EB for <gen-art@ietfa.amsl.com>; Tue, 25 Jun 2013 13:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YRQl1e9xdkxT for <gen-art@ietfa.amsl.com>; Tue, 25 Jun 2013 13:20:05 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id DBA3621E80DA for <gen-art@ietf.org>; Tue, 25 Jun 2013 13:20:04 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 141E7412E2; Tue, 25 Jun 2013 14:20:14 -0600 (MDT)
Message-ID: <51C9FB6A.5090802@stpeter.im>
Date: Tue, 25 Jun 2013 14:19:54 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <51C7A88A.9080102@gmail.com> <1670FE635C32C34AAD005D960F1C501115C6F5EF@xmb-aln-x11.cisco.com> <51C857FA.2050304@stpeter.im> <51C9F79F.2060509@gmail.com>
In-Reply-To: <51C9F79F.2060509@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "draft-ivov-xmpp-cusax.all@tools.ietf.org" <draft-ivov-xmpp-cusax.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ivov-xmpp-cusax-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 20:20:10 -0000

Great. I expect that we'll submit a revised I-D before IESG review.

On 6/25/13 2:03 PM, Brian E Carpenter wrote:
> Hi Peter,
> 
> Thanks, that all seems fine in the light of your comments. I would
> expect to review this as "Ready" when it reaches the IESG agenda.
> 
> Regards
>    Brian
> 
> On 25/06/2013 02:30, Peter Saint-Andre wrote:
>> On 6/23/13 8:27 PM, Peter Saint-Andre (psaintan) wrote:
>>> Hi Brian, thanks for the review.
>>
>> Here is a provisional diff that addresses your feedback:
>>
>> https://github.com/emcho/cusax/commit/1c5e9d681748685360cc6677ea2e369b352e66db#draft-ivov-xmpp-cusax-07.xml
>>
>>> On Jun 23, 2013, at 8:01 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>>>  wrote:
>>>
>>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>>> Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>
>>>> Please resolve these comments along with any other Last Call comments
>>>> you may receive.
>>>>
>>>> Document: draft-ivov-xmpp-cusax-06.txt
>>>> Reviewer: Brian Carpenter
>>>> Review Date: 2013-06-24
>>>> IETF LC End Date: 2013-07-16
>>>> IESG Telechat date:
>>>>
>>>> Summary:  Almost ready
>>>> --------
>>>>
>>>> Comment:
>>>> --------
>>>>
>>>> I have some issues, but I don't know whether to classify any of them as
>>>> major.
>>>>
>>>> Issues:
>>>> -------
>>>>
>>>> In Introduction:
>>>>
>>>> "  As a result, a number of adopters have found themselves needing
>>>>   features that are not offered by any single-protocol solution, but
>>>>   that separately exist in SIP and XMPP implementations.  The idea of
>>>>   seamlessly using both protocols together would hence often appeal to
>>>>   service providers. "
>>>>
>>>> A few paragraphs later, you discuss the case of an end user who would like
>>>> to use SIP and XMPP together with *different* service providers.
>>> Although that's out of scope for this document. We might address that scenario in a future document.
>>>
>>>>  I would suggest
>>>> ending this sentence with "appeal to service providers and users."
>>> Good point.
>>>> "  Finally, this document makes a further simplifying assumption by
>>>>   discussing only the use of a single client, not use of and
>>>>   coordination among multiple endpoints controlled by the same user
>>>>   (e.g., user agents running simultaneously on a laptop computer,
>>>>   tablet, and mobile phone)."
>>>>
>>>> Hmm. Isn't that the normal case today, and your simplifying assumption
>>>> the exception? It's certainly extremely annoying to have different
>>>> contacts lists on different devices, for example. This seems like a
>>>> big gap in the model, with no hints on how it might be filled. (As big
>>>> as the gap between POP3 and IMAP, in some ways.)
>>> At least in XMPP, you'd have the same contact list on all of those devices. But we can word this more carefully.
>>>
>>>> In Client Bootstrap:
>>>>
>>>> "  While it should be possible for CUSAX users to manually configure
>>>>   their separate SIP and XMPP accounts, service providers offering
>>>>   CUSAX services to users of dual-stack SIP/XMPP clients ought to
>>>>   provide means of online provisioning,..."
>>>>
>>>> 1. I would anyway expect my CUSAX client to come with a configuration
>>>> wizard, including a path to the online provisioning if available.
>>> True.
>>>> 2. Is there any reason why SIP service providers and XMPP service
>>>> providers shouldn't individually provide on-line provisioning?
>>> No.
>>>
>>> (Something like the technology proposed at the aggsrv BoF in Orlando might help, too, but that's just a gleam in the eye at this point.)
>>>
>>>>  You're
>>>> describing something close to a captive-customer scenario,
>>> We are indeed assuming that a dual-stack user agent would interact with a combined service (i.e., CUSAX on the client side and CUSAX on the server side).  I am not sure that a customer of such a service is a captive.
>>>
>>>> rather than
>>>> encouraging an open approach to provisioning.
>>> As far as I can see, no open provisioning protocol is available yet. The aforementioned aggsrv approach might fit the bill. It's too early to say, but we can at least mention the possibility that such a technology might be developed in the future.
>>>
>>>> The CUSAX client would
>>>> in any case have to deal with any inconsistencies in provisioning.
>>> I'm not sure what actionable advice we can provide here, but I'll discuss with with my co-authors.
>>>> In Server-Side Setup:
>>>>
>>>> "  In order for CUSAX to function properly, XMPP service administrators
>>>>   should make sure that at least one of the vCard [RFC6350] "tel"
>>>>   fields for each contact is properly populated with a SIP URI or a
>>>>   phone number when an XMPP protocol for vCard storage is used (e.g.,..."
>>>>
>>>> How can they do that, given that users are normally responsible for
>>>> maintaining their contacts lists?
>>> When a user uploads their vCard (or, say, modifies it in a web interface), the server could apply automated checks or make the "tel" field mandatory.
>>>> In Summary of Suggested Practices:
>>>>
>>>> "  1.   By default, prefer SIP for audio and video, and XMPP for
>>>>        messaging and presence."
>>>>
>>>> At the beginning of the Operation section, this seems to be stated as
>>>> a rule, not as a default (" Audio/video features however, are disabled
>>>> in the XMPP stack..."). Which is it?
>>> I'm not seeing a huge difference here -- the XMPP stack in the CUSAX user agent might have audio/video capabilities, but typically those would be disabled (disabled by default, but the user might be allowed to turn them on for certain kinds of contacts, etc.).
>>>
>>> I suggest this change in the Operation section.
>>>
>>> OLD
>>>    Audio/video features however, are
>>>    disabled in the XMPP stack, so any form of communication based on
>>>    these features (e.g. direct calls, conferences, desktop streaming,
>>>    etc.) will happen over SIP.
>>>
>>> NEW
>>>    Audio/video features however, would typically be
>>>    disabled in the XMPP stack, so any form of communication based on
>>>    these features (e.g. direct calls, conferences, desktop streaming,
>>>    etc.) would happen over SIP.
>>>
>>>> In Security Considerations:
>>>>
>>>> "  ... a CUSAX client might
>>>>   successfully negotiate Transport Layer Security (TLS) [RFC5246] when
>>>>   connecting to the XMPP aspect of the service but not when connecting
>>>>   to the SIP aspect.  Such mismatches could introduce the possibility
>>>>   of downgrade attacks."
>>>>
>>>> I'd say *would* introduce the possibility.
>>> Yes, that's more accurate.
>>>
>>>>  It would seem possible for a
>>>> bad actor to pick up authentication data from the insecure service and
>>>> exploit it to attack the secured service. Therefore,
>>>>
>>>> "  User agent developers and service providers
>>>>   ought to ensure that such mismatches are avoided as much as possible."
>>>>
>>>> seems a bit weak. Shouldn't the client also be *required* to alert the user
>>>> that the session as a whole is not secured?
>>>>
>>> IMHO that would be advisable. Good catch.
>>>
>>> Peter
>>>
>>


From ben@nostrum.com  Tue Jun 25 16:10:04 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD0911E8185; Tue, 25 Jun 2013 16:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.145
X-Spam-Level: 
X-Spam-Status: No, score=-100.145 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LscOZ3VJv1yV; Tue, 25 Jun 2013 16:10:02 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id CBF2911E8183; Tue, 25 Jun 2013 16:10:01 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5PN9xMD035207 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Jun 2013 18:09:59 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
Date: Tue, 25 Jun 2013 18:09:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 23:10:04 -0000

Thanks for the response! Comments inline:

Thanks!

Ben.


On Jun 21, 2013, at 4:35 PM, Michael Thornburgh <mthornbu@adobe.com> =
wrote:

> hi Ben. thanks for your review. comments/replies inline.
>=20
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, June 20, 2013 4:07 PM
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document:  draft-thornburgh-adobe-rtmfp-07
>> Reviewer: Ben Campbell
>> Review Date:  2013-06-20
>> IETF LC End Date: 2013-06-25
>>=20
>> Summary: This draft is almost ready for publication as an =
informational RFC. However, I have some
>> concerns about the purpose and intended status of the document that I =
think should be considered prior
>> to publication.
>>=20
>>=20
>> Note: This is an informational draft that describes what I understand =
to be an existing protocol as
>> implemented by commercial products. Therefore, this review does not =
attempt to evaluate the protocol
>> itself. I assume the protocol is what it is, and it is not up to the =
IETF to agree or disagree with
>> it.
>>=20
>> *** Major issues:
>>=20
>> -- Why does this need to be published as an IETF stream RFC?  If I =
understand correctly, this
>> documents an existing protocol as implemented by commercial products. =
I agree with Martin's comment
>> that there is value in publishing this sort of thing, but I applaud =
the Adobe and the author for
>> publishing it so other implementations can interoperate with their =
products. But that could have done
>> that in an independent stream document, or even in an Adobe published =
document. (Perhaps even in a
>> prettier format ;-)  )  If we publish this as an IETF stream =
document, then I think it needs stronger
>> clarification that it is not an IETF consensus doc than just its =
informational status.
>=20
> this memo documents an existing network transport protocol that is =
widely deployed and in widespread use in the Internet.  we felt that the =
IETF community (and in particular the participants in the Transport and =
Services Area) is the most appropriate community with which to share =
this work: 1) members of this community have the necessary and relevant =
expertise not only to understand the protocol, but to make use of it =
potentially in new applications beyond Flash; 2) it is a transport =
protocol similar in many ways to TCP and SCTP and widely deployed and =
used; 3) Adobe is interested in pursuing standardization of this =
protocol (with all that entails) if there is community interest, and the =
IETF is definitely the right place for that.
>=20
> we are very grateful that Martin Stiemerling chose to sponsor this =
document.
>=20
> with regard to comments in later messages in this thread, i'd be happy =
to include some (IESG-supplied) boilerplate in the document to clarify =
that it is not the product of an IETF WG.  however, note that both the =
title and first sentence of the Introduction indicate that this is =
"Adobe's blahblahblah", consistent with other vendor-protocol RFCs and =
consistent with IESG editorial insistence (as told to me by a former TSV =
AD).  see RFC 4332 and RFC 6802 for two examples of =
vendor-specific/supplied protocols.  see also the IESG note in RFC 4332 =
as an example disclaimer that could be added.

Some additional text (whether IESG boilerplate or otherwise) that =
clarifies the purpose of the draft would help a lot.


>=20
>> Along those lines:
>>=20
>> 	-- Is this document the authoritative specification? (I suspect =
not.) Who owns change control? I
>> assume that to be Adobe and/or the authors. What expectation do =
readers of this draft have that it
>> represents the current version of RTMFP at any point in time?
>=20
> this memo is the authoritative specification for Adobe's RTMFP.  Adobe =
owns change control.  i believe the second and third paragraphs of the =
Introduction indicate to a reader that this draft represents RTMFP as =
deployed in the named Adobe products at the time of writing.

At the time of writing yes. My concern is how a future implementor can =
be confident that this doc describes RTMFP as used by Adobe at points in =
the future. When you say this is the authoritative specification, does =
that mean that Adobe does not plan to modify the protocol without timely =
publication of an update to this document?

>=20
>> 	-- Under what circumstances would one desire to implement this? =
I can infer that from the
>> introduction, but it would be nice to see some sort of applicability =
statement making it explicitly
>> clear that this is not an IETF protocol, and that one would implement =
it in order to interoperate with
>> certain Adobe products. I know that some of this may be implied by =
the fact that this is informational
>> rather than standards track. But I don't expect readers who are not =
IETF insiders to understand that
>> subtlety without some explicit words to that effect. In particular, =
it would be good to clarify the
>> difference between this and the many "not quite accepted as standards =
track by some working group"
>> nature of a number of our informational RFCs that describe protocols.
>=20
> i will expand on applicability beyond what i specify in the first =
paragraph of the Introduction, in general terms such as the kinds of =
functionality we use this protocol for in Flash. note that =
interoperation with certain Adobe products, such as Flash Player, =
requires additional information such as the Flash-specific Cryptography =
Profile and syntax/semantics of mapping Flash's "Real Time Messaging =
Protocol (RTMP)" messages onto RTMFP flows.  these Flash-specific =
profiles and mappings are application-layer for RTMFP, analogous to HTTP =
over TCP.

Okay

>=20
>> That all being said, this is overall a well written document. The =
rest of my comments are mostly
>> pedantic nits.
>>=20
>> *** Minor issues:
>>=20
>> -- section 1.2:
>>=20
>> I find the use of "MUST ONLY" confusing. I gather it means "you are =
_allowed_ to do X only under
>> certain conditions" rather than "you are _required_ to do X under =
certain conditions." If correct, I
>> think the words "MAY ONLY" would be more clear. If not, then I think =
the construct would be better
>> handled using existing 2119 language.
>=20
> you're not the first person to be confused by that construct. i will =
change instances of "MUST ONLY" to "is allowed only if" (or similar) and =
remove the definition for "MUST ONLY" from Section 1.2.

Works for me.

>=20
>> -- section 3.2:
>>=20
>> Do I understand correctly that all endpoints are expected to be able =
to present certificates? Do you
>> find that common in the field? I realize the nature of the certs will =
depend on the security profiles.
>=20
> yes, all endpoints have certificates. in the RTMFP-for-Flash world, =
these certificates are not X.509 certs, and are anonymous and ephemeral.

Okay.

>=20
>> -- sections 3.2 and 5
>>=20
>> Do I assume correctly that endpoints need a common crypto profile to =
communicate? Is there a
>> repository where one might find crypto profile documentation? Is =
there a commonly implemented one to
>> which this draft could refer?
>=20
> yes, endpoints need a common cryptography profile to interoperate.  =
there is no repository for crypto profile documentation at this time. =
currently, there is one defined cryptography profile (the one used for =
Flash communication) that is not publicly documented, because i do not =
yet have permission to publish it.  i (meaning me personally) hope that =
a memo documenting the crypto/application profile for Flash =
communication (as being a widely deployed and used profile for RTMFP) =
would also be published someday as an I-D and hopefully an Informational =
RFC.

I understand the issue about permission to publish, but does this =
document serve its purpose until you are ready to publish the crypto =
profile? Ideally they would be published together and this document =
would reference that one. Do I infer correctly that there is no way =
someone could create an implementation that interops with Adobe products =
based on the documents available at this time?

>=20
>> -- section 3.2: "Multiple endpoints SHOULD NOT have the same =
identity."
>>=20
>> Why not MUST? Will things not break if two endpoints do have the same =
identity?
>=20
> this should be "It is RECOMMENDED that multiple endpoints not have the =
same identity."  if two endpoints have the same identity, then they will =
be indistinguishable.  this will not break RTMFP, but might confuse an =
application.  that being said, there could potentially be reasons to =
have different endpoints with indistinguishable identities and that =
potential should not be normatively prohibited.

As Barry mentioned, RECOMMENDED is a synonym for SHOULD. Adding some =
text the effect of your additional explanation would solve my concern.

>=20
>> -- "Authenticity MAY comprise verifying an issuer signature chain in =
a public key infrastructure"
>>=20
>> Is that really normative, or just an observation of fact?
>=20
> that "MAY" should be "can".

Okay.

>=20
>> -- " Canonical Endpoint Discriminators for distinct identities SHOULD =
be distinct."
>>=20
>> What if they are not? Do things break? It might be worth making this =
a MUST, or adding some additional
>> guidance about what might happen if the SHOULD is violated.
>=20
> i will add a note that if the canonical EPD is the same for two =
distinct identities, then the "duplicate session" logic in section =
3.5.1.1.1 (paragraph 6 step 1) might abort a new opening session to the =
second identity, which might not be desired.

Okay.

>=20
>> -- "A comparison function MAY comprise performing a lexicographic =
ordering..."
>>=20
>> Is that really normative, or just an example of something one might =
do?
>=20
> that "MAY" should be "can".

Okay.

>=20
>> -- "A test SHOULD comprise testing whether the certificates are =
identical."
>>=20
>> What if it doesn't? Also, what constitutes "identical"? All fields =
match values? Bitwise match?  Is it
>> simply including the same identity or identities? Maybe an identity =
function provided by the crypto
>> profile?
>=20
> again, that SHOULD should be reworded to RECOMMENDED.  i will change =
"identical" to "bitwise identical".

See my earlier comment on SHOULD vs RECOMMENDED. The important thing is =
to clarify the implications of violating the SHOULD.

>=20
>> -- 3.5, last paragraph:
>>=20
>> Can you offer guidance on reasonable buffer size and number ranges?
>=20
> i assume you mean "3.4, last paragraph" (referring to packet =
reassembly buffers).  i will add some guidance and a "for example".  the =
guidance will depend on how that RTMFP will be used and the expected =
amount of resources available to it.

That would probably help. The important thing is to help implementers =
avoid bad decisions on buffer size ranges.

>=20
>> -- 3.5.1.1.1, 3rd paragraph:
>>=20
>> What are the consequences of having a tag with less than 8 bytes of =
length? Is the SHOULD reasonable
>> here?
>=20
> both of those SHOULDs should be RECOMMENDEDs.

See previous comment

>=20
>> -- 3.5.1.1.1 throughout, and following sections:
>>=20
>> Does the upper case AND have special meaning?
>=20
> upper case is the closest to bold face available in this format.  the =
intention is to emphasize (since there are multiple conditionals) that =
all conditionals are required to hold.

Understood. I'm not sure if there is a convention for that--I guess the =
RFC editor will either leave it or advise something else.

>=20
>> -- 3.5.1.4, Deployment Note:
>>=20
>> How would a redirector know which endpoints might do this? Or should =
it never initiate a session?
>=20
> this is guidance for designing and deploying an RTMFP system.  the =
redirector wouldn't know -- the designer should design the system such =
that the described circumstance doesn't happen (for example, by having =
the redirector never initiate a session).  this is properly a SHOULD NOT =
since doing so can cause undesired behavior (as described).  it is not =
desirable to give a normative prohibition or recommendation against a =
redirector initiating any sessions.  i feel this paragraph gives the =
narrowest normative limitation and an explanation for that limitation.


Okay. Some words to that effect would help.

>=20
>> -- 3.5.2:
>>=20
>> Do I infer correctly that two endpoints need not share the same =
congestion control algorithm to
>> communicate?
>=20
> correct.  the timestamp echo facility, ack behavior (as described for =
flow receivers), and limitations on aggressiveness in 3.5.2/.* impose =
the normative envelope in which any congestion control algorithms should =
interoperate.

Okay.

>=20
>> -- 3.6.2.3.2, 2nd paragraph: "...an implementation SHOULD encode a =
Next User Data chunk instead of a
>> User Data chunk"
>>=20
>> I'm not sure why this needs to be normative, as I assume its just =
normal behavior. But if it does need
>> to be normative, why not a MUST?  Can the far endpoint reasonably =
handle things if the SHOULD is
>> violated?
>=20
> this should be a RECOMMENDED.  the far end will work just fine if Next =
User Data is never used.


See previous comments on SHOULD vs RECOMMENDED.

>=20
>> *** Nits/editorial comments:
>>=20
>> -- General: There's quite a bit of inconsistent use of third-person =
vs second-person language.
>=20
> i will try to clean that up.

Okay.

>=20
>> -- 3.1: It would be nice to see the overview earlier in the draft. I =
found it difficult to read
>> through all the data format stuff prior to section 3 putting them =
into context.
>=20
> others have commented that they'd prefer sections 2 and 3 to be =
swapped. i resisted that as this order ("here are the pieces" and then =
"here's how they fit together") is my preferred way of explaining stuff. =
 also swapping those sections would be a huge editorial change which =
might have significant cross-reference and forward/back reference =
implications and could introduce hard-to-detect errors into the spec.  =
however, i think i can move the overview (or a summary thereof) to =
earlier in the spec (probably in Section 1).

Okay.

>=20
>> -- 3.5.1.4, Deployment Note:
>>=20
>> s/which/that
>=20
> good catch.
>=20
>> -- 3.5.1.6, last paragraph:
>>=20
>> Which diagram? (An explicit cross-ref would help.)
>=20
> oops. that paragraph used to be the postamble of the figure, so it =
obviously meant "this figure".  i'll change "the figure" to "Figure 17".

Okay.

>=20
>> -- 3.5.2:
>>=20
>> What is meant by "aggressive" in this context? Aggressive in avoiding =
congestion, or aggressive in
>> sending data?
>=20
> aggressive in sending data. i'll make that clarification.

Okay.

>=20
>> -- 3.6.2.3.1 and subsequent sections:
>>=20
>> Does the all-caps "FIRST" have special meaning?
>=20
> it is all-caps for typographical emphasis.
>=20
> thank you!
>=20
> -michael thornburgh


From jari.arkko@piuha.net  Wed Jun 26 04:16:59 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6466B21F9971 for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 04:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJcck3e5m-A8 for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 04:16:55 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E800A21E8086 for <gen-art@ietf.org>; Wed, 26 Jun 2013 04:16:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 41F5E2CC56; Wed, 26 Jun 2013 14:16:54 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8vS-tiLiI7qP; Wed, 26 Jun 2013 14:16:52 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id DD85D2CC3C; Wed, 26 Jun 2013 14:16:51 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <075901ce6f59$170f3c50$452db4f0$@gmail.com>
Date: Wed, 26 Jun 2013 07:16:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <58FE9891-0F87-44B6-9AB2-914F1F3D664E@piuha.net>
References: <075901ce6f59$170f3c50$452db4f0$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-pkix-est.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-pkix-est-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 11:16:59 -0000

Roni - thank you for your review. I'm balloting No-Objection based on =
your review and my own quick review. Thanks again - these reviews are =
very important.

Jari

On Jun 22, 2013, at 10:59 AM, Roni Even <ron.even.tlv@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-pkix-est-07
> Reviewer: Roni Even
> Review Date:2013=966=9622
> IETF LC End Date: 2013-6=9624
> IESG Telechat date: 2013-6=9627
> =20
> Summary: This draft is ready for publication as Standard track RFC.
> =20
> This is not a comment, I read the draft and not being an expert in =
this area I found it clear for me to read. The document structure made =
it easier to read.
> =20
> Major issues:
> =20
> Minor issues:
> =20
> =20
> Nits/editorial comments:
>=20
> 1.  In section 4.5.2 =93to use the the secp384r1 elliptic curve=94 =
repeated =93the=94
> =20
>=20


From jari.arkko@piuha.net  Wed Jun 26 04:56:31 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 743F221E808C for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 04:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQJgiqqbttlV for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 04:56:26 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 479C821F8FB3 for <gen-art@ietf.org>; Wed, 26 Jun 2013 04:56:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7138D2CC56; Wed, 26 Jun 2013 14:56:24 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48Hr64kQaURn; Wed, 26 Jun 2013 14:56:24 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 622A22CC3C; Wed, 26 Jun 2013 14:56:23 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43B3E9BE@nkgeml501-mbs.china.huawei.com>
Date: Wed, 26 Jun 2013 07:56:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9CE30CBF-4BBD-45AE-9BB7-09D1B7C5283E@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A105266@eusaamb107.ericsson.se> <B8F9A780D330094D99AF023C5877DABA43B3E9BE@nkgeml501-mbs.china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1508)
Cc: "draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-xrblock-rtcp-xr-jb-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 11:56:31 -0000

Meral, thank you very much for your detailed review. And Qin, thank you =
for addressing these comments in -12. I have balloted No-Objection for =
this draft.

Jari


From bill.wu@huawei.com  Wed Jun 26 04:58:42 2013
Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A1621E813F for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 04:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.766
X-Spam-Level: 
X-Spam-Status: No, score=-5.766 tagged_above=-999 required=5 tests=[AWL=0.833,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wiv+BoFWpAHU for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 04:58:37 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4435211E80E3 for <gen-art@ietf.org>; Wed, 26 Jun 2013 04:58:37 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUK51222; Wed, 26 Jun 2013 11:58:36 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 26 Jun 2013 12:57:39 +0100
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 26 Jun 2013 12:58:21 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.43]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.01.0323.007; Wed, 26 Jun 2013 19:58:16 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Gen-art] Gen-ART Last Call review of draft-ietf-xrblock-rtcp-xr-jb-11
Thread-Index: AQHOcmQ1+eoTBUlSwUGTaBZh0aO0yplH5BIw
Date: Wed, 26 Jun 2013 11:58:15 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43B43DEE@nkgeml501-mbs.china.huawei.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A105266@eusaamb107.ericsson.se> <B8F9A780D330094D99AF023C5877DABA43B3E9BE@nkgeml501-mbs.china.huawei.com> <9CE30CBF-4BBD-45AE-9BB7-09D1B7C5283E@piuha.net>
In-Reply-To: <9CE30CBF-4BBD-45AE-9BB7-09D1B7C5283E@piuha.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-xrblock-rtcp-xr-jb-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 11:58:43 -0000

Thanks.

-----Original Message-----
From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
Sent: Wednesday, June 26, 2013 7:56 PM
To: Qin Wu
Cc: Meral Shirazipour; draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org; ge=
n-art@ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-xrblock-rtcp-=
xr-jb-11

Meral, thank you very much for your detailed review. And Qin, thank you for=
 addressing these comments in -12. I have balloted No-Objection for this dr=
aft.

Jari


From meral.shirazipour@ericsson.com  Wed Jun 26 10:24:09 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBFB111E81D9 for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 10:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pva0yCuuNa2D for <gen-art@ietfa.amsl.com>; Wed, 26 Jun 2013 10:23:58 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id E1CE711E81DD for <gen-art@ietf.org>; Wed, 26 Jun 2013 10:23:47 -0700 (PDT)
X-AuditID: c618062d-b7ef96d000003a6d-c1-51cb23a29b98
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id EA.09.14957.2A32BC15; Wed, 26 Jun 2013 19:23:47 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0328.009; Wed, 26 Jun 2013 13:23:46 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call draft-ietf-xrblock-rtcp-xr-jb-12
Thread-Index: Ac5ykdyh7uR7FMa6ROmDNi0oZ4ydmw==
Date: Wed, 26 Jun 2013 17:23:46 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A13B5C8@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A13B5C8eusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXRPiO5i5dOBBj2dPBbzFm1jt7j66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJUx6dQ35oIVyhVTGtazNTCuke9i5OSQEDCR +LnjAjOELSZx4d56NhBbSOAoo8SKNTpdjFxA9nJGiU+XPjKCJNgELCS2/37OCpIQEZjCKNF9 /z9Yt7CAvcTDbydZQWwRAReJVR+3MkPYehIPLy4Fa2YRUJVYfHoymM0r4C3xuv83E4jNCLT5 +6k1YDazgLjErSfzmSAuEpBYsuc81HWiEi8f/2OFsJUlvs95xAJRny8x++xzVoiZghInZz5h mcAoNAvJqFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGDlKi1PLctONDDYx AuPhmASb7g7GPS8tDzFKc7AoifO+PLUrUEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAOje/K6 rxfjNkdK5qVoChRP21ftzfO2+GL4jKltLLVHpoZKpuyNPfc9ubo23ZTvwT7/yaFXY9/82SO1 Q6Pk5jGhBYL3omzjLudm7GRZ/ydOutyi44Tw9r4b0hz2zYx77/+5tnhJ0p4DHDW+mgcua31W /bbeftYKO4EXbzdXJm56qb2p+vRSLbkrSizFGYmGWsxFxYkAB7QeQ1UCAAA=
Subject: [Gen-art] Gen-ART Telechat Call draft-ietf-xrblock-rtcp-xr-jb-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 17:24:10 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A13B5C8eusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq> .

Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.

Document: draft-ietf-xrblock-rtcp-xr-jb-12
Reviewer: Meral Shirazipour
Review Date: 2013-06-26
IETF LC End Date: 2013-05-31
IESG Telechat date: 2013-06-27

Summary: This draft is ready to be published as Proposed Standard.



Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A13B5C8eusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt; .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-xrblock-rtcp-xr-jb-12<o:p></o:p=
></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-06-26<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-05-31<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-06-27<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Prop=
osed Standard.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A13B5C8eusaamb107ericsso_--

From mthornbu@adobe.com  Wed Jun 26 12:01:26 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E999821F896D; Wed, 26 Jun 2013 12:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.065
X-Spam-Level: 
X-Spam-Status: No, score=-5.065 tagged_above=-999 required=5 tests=[AWL=-0.921, BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJFaAjsPYiz1; Wed, 26 Jun 2013 12:01:20 -0700 (PDT)
Received: from exprod6og124.obsmtp.com (exprod6og124.obsmtp.com [64.18.1.242]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7E711E820E; Wed, 26 Jun 2013 12:00:59 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob124.postini.com ([64.18.5.12]) with SMTP ID DSNKUcs6YcNu3WzllMTzhf8lldRnkH3LXeSk@postini.com; Wed, 26 Jun 2013 12:00:59 PDT
Received: from inner-relay-2.corp.adobe.com (inner-relay-2.adobe.com [153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QJ0lAI005391; Wed, 26 Jun 2013 12:00:48 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QJ08w8007320; Wed, 26 Jun 2013 12:00:44 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Wed, 26 Jun 2013 12:00:20 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>
Date: Wed, 26 Jun 2013 12:00:19 -0700
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5x+SBftgN/0Q0LQ5ilW3KpWz9woAAoI3ow
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com>
In-Reply-To: <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 19:01:27 -0000

comments inline.

> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Tuesday, June 25, 2013 4:10 PM
> =09
> Thanks for the response! Comments inline:
>=20
> Thanks!
>=20
> Ben.
>=20
> On Jun 21, 2013, at 4:35 PM, Michael Thornburgh <mthornbu@adobe.com> wrot=
e:
>=20
> > hi Ben. thanks for your review. comments/replies inline.
> >
> >> From: Ben Campbell [mailto:ben@nostrum.com]
> >> Sent: Thursday, June 20, 2013 4:07 PM

[...]

> > with regard to comments in later messages in this thread, i'd be happy =
to include some (IESG-
> supplied) boilerplate in the document to clarify that it is not the produ=
ct of an IETF WG.  however,
> note that both the title and first sentence of the Introduction indicate =
that this is "Adobe's
> blahblahblah", consistent with other vendor-protocol RFCs and consistent =
with IESG editorial
> insistence (as told to me by a former TSV AD).  see RFC 4332 and RFC 6802=
 for two examples of vendor-
> specific/supplied protocols.  see also the IESG note in RFC 4332 as an ex=
ample disclaimer that could
> be added.
>=20
> Some additional text (whether IESG boilerplate or otherwise) that clarifi=
es the purpose of the draft
> would help a lot.

the sponsoring AD has proposed an additional statement that will be inserte=
d by the RFC Editor on publication.  note that draft -08 has additional cla=
rification that this is an Adobe protocol and is not the product of an IETF=
 activity.

> >> Along those lines:
> >>
> >> 	-- Is this document the authoritative specification? (I suspect not.)=
 Who owns change control? I
> >> assume that to be Adobe and/or the authors. What expectation do reader=
s of this draft have that it
> >> represents the current version of RTMFP at any point in time?
> >
> > this memo is the authoritative specification for Adobe's RTMFP.  Adobe =
owns change control.  i
> believe the second and third paragraphs of the Introduction indicate to a=
 reader that this draft
> represents RTMFP as deployed in the named Adobe products at the time of w=
riting.
>=20
> At the time of writing yes. My concern is how a future implementor can be=
 confident that this doc
> describes RTMFP as used by Adobe at points in the future. When you say th=
is is the authoritative
> specification, does that mean that Adobe does not plan to modify the prot=
ocol without timely
> publication of an update to this document?

this is a problem for *any* published protocol.  RTMFP (as documented in th=
is memo) hasn't changed substantially in many years.  i have every expectat=
ion that, should a change be made to the protocol, we would publish an upda=
ted specification.

[...]

> >> -- sections 3.2 and 5
> >>
> >> Do I assume correctly that endpoints need a common crypto profile to c=
ommunicate? Is there a
> >> repository where one might find crypto profile documentation? Is there=
 a commonly implemented one
> to
> >> which this draft could refer?
> >
> > yes, endpoints need a common cryptography profile to interoperate.  the=
re is no repository for
> crypto profile documentation at this time. currently, there is one define=
d cryptography profile (the
> one used for Flash communication) that is not publicly documented, becaus=
e i do not yet have
> permission to publish it.  i (meaning me personally) hope that a memo doc=
umenting the
> crypto/application profile for Flash communication (as being a widely dep=
loyed and used profile for
> RTMFP) would also be published someday as an I-D and hopefully an Informa=
tional RFC.
>=20
> I understand the issue about permission to publish, but does this documen=
t serve its purpose until you
> are ready to publish the crypto profile? Ideally they would be published =
together and this document
> would reference that one. Do I infer correctly that there is no way someo=
ne could create an
> implementation that interops with Adobe products based on the documents a=
vailable at this time?

additional documentation is needed to interoperate (at the application laye=
r) with the Adobe products that implement RTMFP. i hope that the successful=
 publication of this memo will help me in getting the necessary approval to=
 publish the higher layer details of Adobe's RTMFP ecosystem.

the situation is analogous to having published TCP, but there's a lot more =
you need to know to talk to a web server with HTTPS (like TLS and HTTP).  i=
t's still useful to know how TCP works, and plenty more to do with it than =
talk to web servers.

> >> -- section 3.2: "Multiple endpoints SHOULD NOT have the same identity.=
"
> >>
> >> Why not MUST? Will things not break if two endpoints do have the same =
identity?
> >
> > this should be "It is RECOMMENDED that multiple endpoints not have the =
same identity."  if two
> endpoints have the same identity, then they will be indistinguishable.  t=
his will not break RTMFP, but
> might confuse an application.  that being said, there could potentially b=
e reasons to have different
> endpoints with indistinguishable identities and that potential should not=
 be normatively prohibited.
>=20
> As Barry mentioned, RECOMMENDED is a synonym for SHOULD. Adding some text=
 the effect of your
> additional explanation would solve my concern.

i changed this to RECOMMENDED (because while i agree that RECOMMENDED and S=
HOULD impart the same force of normative requirement for an implementer, th=
e words' different English meanings help the reader understand the reason f=
or the normative constraint).  see draft -08 for additional explanation i a=
dded for this constraint.

[...]

> >> *** Nits/editorial comments:
> >>
> >> -- General: There's quite a bit of inconsistent use of third-person vs=
 second-person language.
> >
> > i will try to clean that up.
>=20
> Okay.

as i mentioned in a separate message: """i believe the "second-person" voic=
e in this memo is used exclusively for detailing algorithms that are to be =
performed. i believe the imperative "do it like this" voice is appropriate =
to that use, so i did not change it. i also feel that the change in voice h=
elps indicate that the implementation is being addressed/instructed."""

[...]

thanks.

-michael thornburgh


From ben@nostrum.com  Wed Jun 26 13:03:50 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C36E811E8205; Wed, 26 Jun 2013 13:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.145
X-Spam-Level: 
X-Spam-Status: No, score=-100.145 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Crq3PO7XGjsG; Wed, 26 Jun 2013 13:03:50 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DCBE011E8203; Wed, 26 Jun 2013 13:03:49 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-070-136.mycingular.net [166.147.70.136]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r5QK3i61077390 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Jun 2013 15:03:46 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com>
Date: Wed, 26 Jun 2013 15:03:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.70.136 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 20:03:50 -0000

Hi Michael,

Thanks for the continued responses. A few more comments inline. I =
deleted sections that did not seem to need further comment. In summary, =
all of my concerns are resolved except for the crypto profile question.

Thanks!

Ben.

On Jun 26, 2013, at 2:00 PM, Michael Thornburgh <mthornbu@adobe.com> =
wrote:

[...]

>>> with regard to comments in later messages in this thread, i'd be =
happy to include some (IESG-
>> supplied) boilerplate in the document to clarify that it is not the =
product of an IETF WG.  however,
>> note that both the title and first sentence of the Introduction =
indicate that this is "Adobe's
>> blahblahblah", consistent with other vendor-protocol RFCs and =
consistent with IESG editorial
>> insistence (as told to me by a former TSV AD).  see RFC 4332 and RFC =
6802 for two examples of vendor-
>> specific/supplied protocols.  see also the IESG note in RFC 4332 as =
an example disclaimer that could
>> be added.
>>=20
>> Some additional text (whether IESG boilerplate or otherwise) that =
clarifies the purpose of the draft
>> would help a lot.
>=20
> the sponsoring AD has proposed an additional statement that will be =
inserted by the RFC Editor on publication.  note that draft -08 has =
additional clarification that this is an Adobe protocol and is not the =
product of an IETF activity.

The additional statement in 08 resolves my concern in the context of =
this specific document. (I have mixed feelings about the idea of =
documenting proprietary protocols in IETF stream drafts at all, but it's =
not reasonable to hold any particular draft hostage over a larger policy =
question.)

>> At the time of writing yes. My concern is how a future implementor =
can be confident that this doc
>> describes RTMFP as used by Adobe at points in the future. When you =
say this is the authoritative
>> specification, does that mean that Adobe does not plan to modify the =
protocol without timely
>> publication of an update to this document?
>=20
> this is a problem for *any* published protocol.
>  RTMFP (as documented in this memo) hasn't changed substantially in =
many years.  i have every expectation that, should a change be made to =
the protocol, we would publish an updated specification.
>=20

(Let me preface this comment: This is also an issue with the general =
idea of publishing proprietary protocols in IETF stream documents. I'm =
not picking on this draft in particular, and we can consider this issue =
closed for the purposes of my Gen-ART review.)

I disagree that this is an issue for any published protocol. In the case =
of an IETF produced protocol, an RFC is the definitive specification. If =
the IETF chooses to revise the protocol in the future, it does so by =
publishing a new RFC that updates or obsoletes the original.=20

You indicate Adobe plans to do the same, and that this protocol is =
pretty stable. You mentioned previously that this document would be the =
authoritative specification. So, then maybe there's not an issue.  But =
if Adobe maintains internal documentation that an Adobe engineer would =
consult to understand and implement the protocol, and you revise that =
documentation internally, it's going to be pretty tricky keeping the =
IETF -published specification in sync.



>>>=20
>>> yes, endpoints need a common cryptography profile to interoperate.  =
there is no repository for
>> crypto profile documentation at this time. currently, there is one =
defined cryptography profile (the
>> one used for Flash communication) that is not publicly documented, =
because i do not yet have
>> permission to publish it.  i (meaning me personally) hope that a memo =
documenting the
>> crypto/application profile for Flash communication (as being a widely =
deployed and used profile for
>> RTMFP) would also be published someday as an I-D and hopefully an =
Informational RFC.
>>=20
>> I understand the issue about permission to publish, but does this =
document serve its purpose until you
>> are ready to publish the crypto profile? Ideally they would be =
published together and this document
>> would reference that one. Do I infer correctly that there is no way =
someone could create an
>> implementation that interops with Adobe products based on the =
documents available at this time?
>=20
> additional documentation is needed to interoperate (at the application =
layer) with the Adobe products that implement RTMFP. i hope that the =
successful publication of this memo will help me in getting the =
necessary approval to publish the higher layer details of Adobe's RTMFP =
ecosystem.
>=20
> the situation is analogous to having published TCP, but there's a lot =
more you need to know to talk to a web server with HTTPS (like TLS and =
HTTP).  it's still useful to know how TCP works, and plenty more to do =
with it than talk to web servers.

I don't think that's a fair analogy. I can use TCP for many purposes =
other than talking to web servers. It can even be useful all itself. But =
if I understand correctly, you can't expect to use RTMFP _at_all_ until =
you publish they crypto-profile(s). Is that correct? If so, a better =
analogy would be to publish TLS without any published cryptosuites.

If I am correct on the inability to use the protocol at all without more =
documentation that does not currently exist, then I think it would be =
reasonable to put a clearly worded assertion to that effect early in the =
draft, along with a comment that you intend to publish at least one =
crypto profile in the future. (Perhaps an applicability statement would =
be helpful here.)


>=20
>>>> -- section 3.2: "Multiple endpoints SHOULD NOT have the same =
identity."
>>>>=20
>>>> Why not MUST? Will things not break if two endpoints do have the =
same identity?
>>>=20
>>> this should be "It is RECOMMENDED that multiple endpoints not have =
the same identity."  if two
>> endpoints have the same identity, then they will be =
indistinguishable.  this will not break RTMFP, but
>> might confuse an application.  that being said, there could =
potentially be reasons to have different
>> endpoints with indistinguishable identities and that potential should =
not be normatively prohibited.
>>=20
>> As Barry mentioned, RECOMMENDED is a synonym for SHOULD. Adding some =
text the effect of your
>> additional explanation would solve my concern.
>=20
> i changed this to RECOMMENDED (because while i agree that RECOMMENDED =
and SHOULD impart the same force of normative requirement for an =
implementer, the words' different English meanings help the reader =
understand the reason for the normative constraint).  see draft -08 for =
additional explanation i added for this constraint.

The added text in 08 resolves my concerns. (I'm not going to get into =
the RECOMMENDED vs SHOULD argument other than to note that the thread on =
the IETF discussion list tells me that English speakers don't =
necessarily agree on the difference :-) )



>=20
> [...]
>=20
>>>> *** Nits/editorial comments:
>>>>=20
>>>> -- General: There's quite a bit of inconsistent use of third-person =
vs second-person language.
>>>=20
>>> i will try to clean that up.
>>=20
>> Okay.
>=20
> as i mentioned in a separate message: """i believe the "second-person" =
voice in this memo is used exclusively for detailing algorithms that are =
to be performed. i believe the imperative "do it like this" voice is =
appropriate to that use, so i did not change it. i also feel that the =
change in voice helps indicate that the implementation is being =
addressed/instructed."""

Oops, sorry, I meant to cut that part out of my previous reply after =
seeing your other email. I seem to recall finding 2nd person language in =
sections that were not clearly identified as algorithm specifications, =
but on re-review I can't find it--so consider it dropped.


From mthornbu@adobe.com  Wed Jun 26 14:09:27 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7969121F9B19; Wed, 26 Jun 2013 14:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.88
X-Spam-Level: 
X-Spam-Status: No, score=-4.88 tagged_above=-999 required=5 tests=[AWL=-0.736,  BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8cUgS7DO9-Py; Wed, 26 Jun 2013 14:09:09 -0700 (PDT)
Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) by ietfa.amsl.com (Postfix) with ESMTP id 6C85C21F9B0F; Wed, 26 Jun 2013 14:08:39 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKUctYT0KPr9/OJqS8eThBCw2NY9ORPz2P@postini.com; Wed, 26 Jun 2013 14:08:39 PDT
Received: from inner-relay-1.corp.adobe.com (ms-exchange.macromedia.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QL8PAI021519; Wed, 26 Jun 2013 14:08:26 -0700 (PDT)
Received: from SJ1SWM219.corp.adobe.com (sj1swm219.corp.adobe.com [10.5.77.61]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r5QL8P6A018936; Wed, 26 Jun 2013 14:08:25 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by SJ1SWM219.corp.adobe.com ([fe80::d55c:7209:7a34:fcf7%11]) with mapi; Wed, 26 Jun 2013 14:08:24 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>
Date: Wed, 26 Jun 2013 14:08:24 -0700
Thread-Topic: Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
Thread-Index: Ac5yqEjda+NG/nO7S76BMoYlgBj5ugAAyT6g
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AAE61@nambx08.corp.adobe.com>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com> <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com>
In-Reply-To: <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 21:09:27 -0000

hi Ben. comment inline.

> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Wednesday, June 26, 2013 1:04 PM
>=20
> Hi Michael,
>=20
> Thanks for the continued responses. A few more comments inline. I deleted=
 sections that did not seem
> to need further comment. In summary, all of my concerns are resolved exce=
pt for the crypto profile
> question.
>=20
> Thanks!
>=20
> Ben.
>=20
> On Jun 26, 2013, at 2:00 PM, Michael Thornburgh <mthornbu@adobe.com> wrot=
e:

[...]

> >>> yes, endpoints need a common cryptography profile to interoperate.  t=
here is no repository for
> >> crypto profile documentation at this time. currently, there is one def=
ined cryptography profile
> (the
> >> one used for Flash communication) that is not publicly documented, bec=
ause i do not yet have
> >> permission to publish it.  i (meaning me personally) hope that a memo =
documenting the
> >> crypto/application profile for Flash communication (as being a widely =
deployed and used profile for
> >> RTMFP) would also be published someday as an I-D and hopefully an Info=
rmational RFC.
> >>
> >> I understand the issue about permission to publish, but does this docu=
ment serve its purpose until
> you
> >> are ready to publish the crypto profile? Ideally they would be publish=
ed together and this document
> >> would reference that one. Do I infer correctly that there is no way so=
meone could create an
> >> implementation that interops with Adobe products based on the document=
s available at this time?
> >
> > additional documentation is needed to interoperate (at the application =
layer) with the Adobe
> products that implement RTMFP. i hope that the successful publication of =
this memo will help me in
> getting the necessary approval to publish the higher layer details of Ado=
be's RTMFP ecosystem.
> >
> > the situation is analogous to having published TCP, but there's a lot m=
ore you need to know to talk
> to a web server with HTTPS (like TLS and HTTP).  it's still useful to kno=
w how TCP works, and plenty
> more to do with it than talk to web servers.
>=20
> I don't think that's a fair analogy. I can use TCP for many purposes othe=
r than talking to web
> servers. It can even be useful all itself. But if I understand correctly,=
 you can't expect to use
> RTMFP _at_all_ until you publish they crypto-profile(s). Is that correct?=
 If so, a better analogy
> would be to publish TLS without any published cryptosuites.
>=20
> If I am correct on the inability to use the protocol at all without more =
documentation that does not
> currently exist, then I think it would be reasonable to put a clearly wor=
ded assertion to that effect
> early in the draft, along with a comment that you intend to publish at le=
ast one crypto profile in the
> future. (Perhaps an applicability statement would be helpful here.)

interoperating with the Flash ecosystem requires additional documentation. =
i agree that a better analogy is publishing TLS without any published crypt=
osuites.

using RTMFP requires _a_ cryptography profile. this memo describes the requ=
ired semantics of a cryptography profile.  the first bullet of Section 1.1 =
"Design Highlights" (which occurs on the first page after the TOC), Section=
 2.2.3 "Encryption", and the first paragraph of the Security Considerations=
 section all indicate that this protocol defines a general framework for se=
curity, and that the application designer chooses/defines the algorithms an=
d data formats to be used within that framework.  an application designer c=
ould, using only this memo (and knowledge of security and cryptography prin=
ciples), define her own cryptography profile suitable for her application o=
f RTMFP, and create a correct and useful RTMFP application.

since i don't yet have permission, i can't make a commitment in this memo t=
hat Adobe will (or intends to) publicly document any additional layers of t=
he RTMFP-in-Flash ecosystem.  just for extra clarification: it is my *perso=
nal* hope that i will be able to do so in the future.

[...]

thanks!

-michael thornburgh

From jari.arkko@piuha.net  Thu Jun 27 03:54:26 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34BBD21F9997 for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 03:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRSlatAV9w-B for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 03:54:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6637B21F9CD8 for <gen-art@ietf.org>; Thu, 27 Jun 2013 03:53:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5A3112CC48; Thu, 27 Jun 2013 13:53:07 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4ENzNRt453j; Thu, 27 Jun 2013 13:53:06 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 3DB6B2CC3C; Thu, 27 Jun 2013 13:53:06 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51ABAF46.7090005@gmail.com>
Date: Thu, 27 Jun 2013 06:53:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3ACAEE99-4418-4CD0-A990-4C54F4B36E81@piuha.net>
References: <51ABAF46.7090005@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-avtcore-avp-codecs.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-avtcore-avp-codecs-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 10:54:26 -0000

Brian - thank you very much for your review of this document. Based on =
this review and my (quicker) own review, I have balloted a No-objection =
for this draft.

Jari



From jari.arkko@piuha.net  Thu Jun 27 04:33:29 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4743321F9C52 for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 04:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t831tzjZwpkk for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 04:33:25 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 0DAB421F9C2F for <gen-art@ietf.org>; Thu, 27 Jun 2013 04:33:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5954A2CC48; Thu, 27 Jun 2013 14:33:24 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3l1624oZ0c2d; Thu, 27 Jun 2013 14:33:23 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 0D5DF2CC3C; Thu, 27 Jun 2013 14:33:22 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51C89A1D.10404@ericsson.com>
Date: Thu, 27 Jun 2013 07:33:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A24320F0-DB61-41DA-BB39-AFD17FDAA577@piuha.net>
References: <51C89A1D.10404@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-ipsecme-ad-vpn-problem.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-ipsecme-ad-vpn-problem-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 11:33:29 -0000

Thank you for the review, Suresh. Steve et al, do you have thoughts on =
these? FWIW, I think the question on 2.3 is quite important.

Jari

On Jun 24, 2013, at 3:12 PM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:

> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-ipsecme-ad-vpn-problem-07.txt
> Reviewer: Suresh Krishnan
> Review Date: 2013/06/24
> IESG Telechat date: 2013/06/27
>=20
> Summary: This draft is almost ready for publication as an =
Informational
> RFC but I do have a few comments that the authors may want to =
consider.
>=20
> Minor
> =3D=3D=3D=3D=3D
>=20
> * Section 2.3
>=20
> The following sentence is a bit confusing. How does a mobile user
> connect to a new gateway without reinitiating a connection? Can you
> please clarify or reword.
>=20
> "The mobile user ought to be able to discover and then connect to the
> current most efficient gateway without having to reinitiate the =
connection."
>=20
> * Section 4.1. Requirement 5
>=20
> Shouldn't there be a requirement here that states what kind of damage =
is
> allowed and prohibited in case a hub node is compromised?
>=20
> * Section 4.1. Requirement 12
>=20
> It is unclear what this requirement means. Is the requirement for the
> solution to integrate with multicast routing protocols to come up with =
a
> different (and optimized) multicast ADVPN topology or to simply allow
> the advpn to carry (flattened out) multicast traffic?
>=20
> * Section 4.1. Requirement 14
>=20
> Are there any special requirements that L3VPN poses on top of what is
> required for carrying generic IP traffic? If so, can you elaborate =
here.
>=20
> Thanks
> Suresh
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Thu Jun 27 04:42:02 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447A321F9BBE for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 04:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id de9ZHqE3yEnE for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 04:41:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C830D21F9A2C for <gen-art@ietf.org>; Thu, 27 Jun 2013 04:41:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D7A1B2CC48; Thu, 27 Jun 2013 14:41:49 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9KM4RMB8UIw0; Thu, 27 Jun 2013 14:41:48 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 10A012CC3C; Thu, 27 Jun 2013 14:41:47 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51B05EE4.1010405@isode.com>
Date: Thu, 27 Jun 2013 07:41:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <284C9A7B-1167-41D6-8CB3-85ABAB82C5C5@piuha.net>
References: <51B05EE4.1010405@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org, "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-forces-interop-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 11:42:02 -0000

Thank you for this review, Alexey. I have balloted a No-Objection based =
on it.=20

BTW, the thread title is wrong, but I assume the review is on the GMPLS =
document draft-ietf-pce-gmpls-aps-req as your comments match the =
document content :-)

Jari

On Jun 6, 2013, at 6:05 AM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document:  draft-ietf-pce-gmpls-aps-req-07
> Reviewer: Alexey Melnikov
> Review Date: 2013-06-06
> IETF LC End Date: 2013-06-07
> IESG Telechat date: (if known)
>=20
> Summary: This draft is ready for publication as an informational RFC.
>=20
> Major issues: None.
>=20
> Minor issues: None.
>=20
> Nits/editorial comments:
>=20
> I might have missed that, but I think the first mention of ERO
> needs expansion of the acronym and a reference.
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Thu Jun 27 05:20:56 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA6521F9CDF; Thu, 27 Jun 2013 05:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMH5KhDofpzk; Thu, 27 Jun 2013 05:20:51 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3E17421F9CDC; Thu, 27 Jun 2013 05:20:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 61B802CC48; Thu, 27 Jun 2013 15:20:32 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HesJlnkmX_R7; Thu, 27 Jun 2013 15:20:31 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 127E82CC3C; Thu, 27 Jun 2013 15:20:30 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC74398261AAE61@nambx08.corp.adobe.com>
Date: Thu, 27 Jun 2013 08:20:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <23465268-C5EB-42E7-BC98-0B300BBCCDCC@piuha.net>
References: <9BC409BF-0E49-4057-B590-9D030228DC6E@nostrum.com> <D9D602D39A98E34D9C43E965BEC7439825F20CD3@nambx08.corp.adobe.com> <8259B3A4-BDBE-4BE0-AEF6-51DA65E4652E@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE1D@nambx08.corp.adobe.com> <3F184F54-61DA-44D3-A705-A12F224E716A@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AAE61@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-thornburgh-adobe-rtmfp-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 12:20:56 -0000

Ben, thank you very much for the review, and Michael, thank you for =
answering and addressing the issues.=20

I am still concerned about the crypto profile question, however. I'd =
like to understand what the lack of a profile specification means for =
interoperability and the ability of others to use this spec.

Jari


From Francis.Dupont@fdupont.fr  Thu Jun 27 09:15:40 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E48021F9D02 for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 09:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yd77+t4NkJFB for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 09:15:39 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 417E321F9CD5 for <gen-art@ietf.org>; Thu, 27 Jun 2013 09:15:39 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r5RGFcqn049951; Thu, 27 Jun 2013 18:15:38 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201306271615.r5RGFcqn049951@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Thu, 27 Jun 2013 18:15:38 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-rtgwg-cl-requirement.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-rtgwg-cl-requirement-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 16:15:40 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-rtgwg-cl-requirement-10.txt
Reviewer: Francis Dupont
Review Date: 20130617
IETF LC End Date: 20130619
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - ToC page 3 and 7 page 12: Acknowledgements -> Acknowledgments

 - 2 page 4: double include words in:

   The services supported include pseudowire based services (RFC 3985
   [RFC3985]), including VPN services,

 I suggest something like:

   The supported services are, but not limited to, pseudowire based
   services (RFC 3985 [RFC3985]), including VPN services,

 - 3 page 5 (component link): the term NPO is used before being defined

 - 3 page 5 (component link): expand the WDM abbrev -- not well known
  according tothe RFC Editor list:
  http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

 - 3 page 5 (flow identification): same for the PW abbrev

 - 4.1 page 6: CAN -> MAY

 - 6 page 12 (MR#10) -> interpretted -> interpreted

 - 9 page 13: Encrption -> Encryption

 - Authors' Addresses: add the country (USA) in postal addresses

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Thu Jun 27 09:28:11 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08DFD21F9DB5 for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 09:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWfeXRkFb9i1 for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 09:28:09 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 0351121F996A for <gen-art@ietf.org>; Thu, 27 Jun 2013 09:28:08 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r5RGS2N1050704; Thu, 27 Jun 2013 18:28:02 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201306271628.r5RGS2N1050704@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Thu, 27 Jun 2013 18:28:02 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-xrblock-rtcp-xr-discard-rle-metrics.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 16:28:11 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.txt
Reviewer: Francis Dupont
Review Date: 20130625
IETF LC End Date: 20130701
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - title page 1: for  Run Length -> for Run Length

 - ToC page 2 and 9 page 9: Acknowledgements -> Acknowledgments

 - 1 page 3: take benefit of the first "Extended Reports" to introduce
 the XR abbrev

 - 1 page 3: expand the RR abbrev (not well known according to the RFC Editor
  list http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
  and BTW has at least 3 different meanings :-)

 - 1 page 3: RLE is well known (so you can keep it!)

 - 1 page 3: playout > play out (according to my spell checker...)

 - 3 page 4 (still the spell checker): recaps

Thanks

Francis.Dupont@fdupont.fr

From curtis@ipv6.occnc.com  Thu Jun 27 11:05:32 2013
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A5621F9E8A for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 11:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4XpJ3AiXoy+l for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 11:05:28 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id 8921721F9E86 for <gen-art@ietf.org>; Thu, 27 Jun 2013 11:05:25 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r5RI2qOw096500; Thu, 27 Jun 2013 14:02:52 -0400 (EDT) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201306271802.r5RI2qOw096500@gateway1.orleans.occnc.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Thu, 27 Jun 2013 18:15:38 +0200." <201306271615.r5RGFcqn049951@givry.fdupont.fr>
Date: Thu, 27 Jun 2013 14:02:51 -0400
X-Mailman-Approved-At: Thu, 27 Jun 2013 11:08:04 -0700
Cc: gen-art@ietf.org, draft-ietf-rtgwg-cl-requirement.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-rtgwg-cl-requirement-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 18:05:32 -0000

In message <201306271615.r5RGFcqn049951@givry.fdupont.fr>
Francis Dupont writes:
 
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>  
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>  
> Please resolve these comments along with any other Last Call comments
> you may receive.
>  
> Document: draft-ietf-rtgwg-cl-requirement-10.txt
> Reviewer: Francis Dupont
> Review Date: 20130617
> IETF LC End Date: 20130619
> IESG Telechat date: unknown
>  
> Summary: Ready
>  
> Major issues: None
>  
> Minor issues: None

OK.  Thanks but it appears the document is headed back to another WGLC
due to other comments, mostly due to the RtgDir review comments.

> Nits/editorial comments:
>  - ToC page 3 and 7 page 12: Acknowledgements -> Acknowledgments

It appears that both spellings are acceptable according to my spell
checker.  I will leave as is unless there is continued objection.

>  - 2 page 4: double include words in:
>  
>    The services supported include pseudowire based services (RFC 3985
>    [RFC3985]), including VPN services,
>  
>  I suggest something like:
>  
>    The supported services are, but not limited to, pseudowire based
>    services (RFC 3985 [RFC3985]), including VPN services,

Thank you.  I will make this change.

>  - 3 page 5 (component link): the term NPO is used before being defined
>  
>  - 3 page 5 (component link): expand the WDM abbrev -- not well known
>   according tothe RFC Editor list:
>   http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>  
>  - 3 page 5 (flow identification): same for the PW abbrev

A last call comment from our AD is to expand all acronyms before use.
The SecDir comments also requested this.

>  - 4.1 page 6: CAN -> MAY

Thank you.  I will make this change.

>  - 6 page 12 (MR#10) -> interpretted -> interpreted

Thank you.  My spell checker agrees.  I will make this change.

>  - 9 page 13: Encrption -> Encryption

Thank you.  I obviously didn't make spell check corrections in a
recent edit.  I will make this change.

I will also do a full spell check and see what else the spell checker
find.  (I am using International Ispell Version 3.3.02 12 Jun 2005
with English and American English dictionary files).

>  - Authors' Addresses: add the country (USA) in postal addresses

Thank you.  I will make this change.

> Regards
>  
> Francis.Dupont@fdupont.fr

Thank you for the review of this document.

Curtis

From varun@comnet.tkk.fi  Thu Jun 27 15:52:54 2013
Return-Path: <varun@comnet.tkk.fi>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BBC21F9AE0 for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 15:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zn2DfSa5mmgh for <gen-art@ietfa.amsl.com>; Thu, 27 Jun 2013 15:52:49 -0700 (PDT)
Received: from smtp-out-02.aalto.fi (smtp-out-02.aalto.fi [130.233.228.121]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD1021F9AE2 for <gen-art@ietf.org>; Thu, 27 Jun 2013 15:52:47 -0700 (PDT)
Received: from smtp-out-02.aalto.fi (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 391812718FC_1CCC23FB; Thu, 27 Jun 2013 22:52:47 +0000 (GMT)
Received: from smtp.netlab.hut.fi (cinema.netlab.hut.fi [130.233.154.177]) by smtp-out-02.aalto.fi (Sophos Email Appliance) with ESMTP id ECD322718F9_1CCC23EF; Thu, 27 Jun 2013 22:52:46 +0000 (GMT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id D41051E142; Fri, 28 Jun 2013 01:52:46 +0300 (EEST)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id s9psnTbAebyq; Fri, 28 Jun 2013 01:52:41 +0300 (EEST)
Received: from [192.168.0.10] (cs181253247.pp.htv.fi [82.181.253.247]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id 781EE1E11E; Fri, 28 Jun 2013 01:52:41 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: Varun Singh <varun@comnet.tkk.fi>
In-Reply-To: <201306271628.r5RGS2N1050704@givry.fdupont.fr>
Date: Fri, 28 Jun 2013 01:52:41 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0871C7A1-0F51-4A1B-B025-80782DACC372@comnet.tkk.fi>
References: <201306271628.r5RGS2N1050704@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Thu, 27 Jun 2013 16:49:04 -0700
Cc: gen-art@ietf.org, draft-ietf-xrblock-rtcp-xr-discard-rle-metrics.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 22:52:54 -0000

Hi,

Thank you for the comments, responses inline.

Cheers,
Varun

On Jun 27, 2013, at 7:28 PM, Francis Dupont wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.txt
> Reviewer: Francis Dupont
> Review Date: 20130625
> IETF LC End Date: 20130701
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
> - title page 1: for  Run Length -> for Run Length

Ok.

>=20
> - ToC page 2 and 9 page 9: Acknowledgements -> Acknowledgments

Ok.

>=20
> - 1 page 3: take benefit of the first "Extended Reports" to introduce
> the XR abbrev

It is in the title, but I've expanded it at first occurrence in text.

>=20
> - 1 page 3: expand the RR abbrev (not well known according to the RFC =
Editor
>  list http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>  and BTW has at least 3 different meanings :-)
>=20

Ok.

> - 1 page 3: RLE is well known (so you can keep it!)
>=20

It is expanded in the title, but I expanded it at first occurrence in =
the text.

> - 1 page 3: playout > play out (according to my spell checker=85)

In multimedia we often use: playout buffer, playout delay.=20
But in this case playout is acting more as a verb instead of a noun.=20
Anyone else have an opinion about this?=20

> - 3 page 4 (still the spell checker): recaps
>=20

recaps is an informal word, I can replace it.
recaps -> describes

> Thanks
>=20
> Francis.Dupont@fdupont.fr


From peter@akayla.com  Fri Jun 28 00:05:11 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD79821F9E27 for <gen-art@ietfa.amsl.com>; Fri, 28 Jun 2013 00:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CU-EWOewGdU for <gen-art@ietfa.amsl.com>; Fri, 28 Jun 2013 00:05:02 -0700 (PDT)
Received: from m1plsmtpa01-05.prod.mesa1.secureserver.net (m1plsmtpa01-05.prod.mesa1.secureserver.net [64.202.165.10]) by ietfa.amsl.com (Postfix) with ESMTP id DF15021F9DDC for <gen-art@ietf.org>; Fri, 28 Jun 2013 00:04:56 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by m1plsmtpa01-05.prod.mesa1.secureserver.net with  id tj4v1l00E1huGat01j4vxs; Fri, 28 Jun 2013 00:04:56 -0700
From: "Peter Yee" <peter@akayla.com>
To: <gen-art@ietf.org>
Date: Fri, 28 Jun 2013 00:05:07 -0700
Message-ID: <03c901ce73cd$d30c1f40$79245dc0$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03CA_01CE7393.26AE58B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5zzTNCrJOZ6lkwS7aJ9XIo6w4U/g==
Content-Language: en-us
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-06-27
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2013 07:05:12 -0000

This is a multipart message in MIME format.

------=_NextPart_000_03CA_01CE7393.26AE58B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

The following reviewers have assignments:

 

Reviewer          LC end       Draft

---------------------------------------------------------------------

Meral Shirazipour 2013-07-22  draft-ivov-grouptextchat-purpose-03

 

Roni Even         2013-07-23  draft-merkle-tls-brainpool-02

 

Contact me if you have any issues with the assignments.  I tried to follow
Jean's directions!

 

I have made the assignments in the review tool:

http://art.tools.ietf.org/tools/art/genart/

 

And the assignments are captured in the spreadsheets:

http://wiki.tools.ietf.org/dav/genart/gen-art.html

http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

 

 

The standard template is included below.

 

Thanks,

 

Peter

 

-------------------------------------------------------------------

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

 

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document:

Reviewer:

Review Date:

IETF LC End Date:

IESG Telechat date: (if known)

 

Summary:

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

_______________________________________________

Gen-art mailing list

Gen-art@ietf.org

https://www.ietf.org/mailman/listinfo/gen-art

 


------=_NextPart_000_03CA_01CE7393.26AE58B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@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:0in;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The following reviewers have =
assignments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Reviewer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LC =
end&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Draft<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
--<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'>Meral Shirazipour 2013-07-22 =
&nbsp;draft-ivov-grouptextchat-purpose-03<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'>Roni =
Even&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-07-23 =
&nbsp;draft-merkle-tls-brainpool-02<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'>Contact me if you have any issues =
with the assignments.&nbsp; I tried to follow Jean&#8217;s =
directions!<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>I have made the assignments in the =
review tool:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>http://art.tools.ietf.org/tools/art/genart/<o:p></o:p></span></p><p=
 class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>And the assignments are captured in =
the spreadsheets:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>http://wiki.tools.ietf.org/dav/genart/gen-art.html<o:p></o:p></span=
></p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The standard template is included =
below.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Thanks,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Peter<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<o:=
p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Please =
resolve these comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Document:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Reviewer:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Review =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IETF LC End =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IESG Telechat date: (if =
known)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Summary:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>_______________________________________________<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art mailing list<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art@ietf.org<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>https://www.ietf.org/mailman/listinfo/gen-art<o:p></o:p></span></p>=
<p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_03CA_01CE7393.26AE58B0--


From peter@akayla.com  Fri Jun 28 01:03:27 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F00E21F8495 for <gen-art@ietfa.amsl.com>; Fri, 28 Jun 2013 01:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rgbLZaW5XQ9j for <gen-art@ietfa.amsl.com>; Fri, 28 Jun 2013 01:03:17 -0700 (PDT)
Received: from p3plsmtpa11-01.prod.phx3.secureserver.net (p3plsmtpa11-01.prod.phx3.secureserver.net [68.178.252.102]) by ietfa.amsl.com (Postfix) with ESMTP id 300A121F9EE6 for <gen-art@ietf.org>; Fri, 28 Jun 2013 01:02:59 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-01.prod.phx3.secureserver.net with  id tk2x1l0031huGat01k2xDk; Fri, 28 Jun 2013 01:02:57 -0700
From: "Peter Yee" <peter@akayla.com>
To: <gen-art@ietf.org>
Date: Fri, 28 Jun 2013 01:03:09 -0700
Message-ID: <03d501ce73d5$ee212160$ca636420$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03D6_01CE739B.41C3A8F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5z1QWXtlPE7WWkTyi6BUPOJjaEHQ==
Content-Language: en-us
Subject: [Gen-art] Assignments for the 2013-07-11 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2013 08:03:27 -0000

This is a multipart message in MIME format.

------=_NextPart_000_03D6_01CE739B.41C3A8F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

The following reviewers have assignments:

 

Reviewer               LC end     Draft

----------------------------------------------------------------------------
--------

Joel Halpern           2013-06-19
draft-ietf-ospf-manet-single-hop-mdr-03 **

 

Kathleen Moriarty      2013-06-28
draft-ietf-ipfix-protocol-rfc5101bis-08 **

 

Peter Yee              2013-06-27     draft-ietf-appsawg-rfc5451bis-07 ** 

 

Suresh Krishnan        2013-01-21     draft-ietf-lisp-mib-11 * (Reassigned
from Miguel Garcia)

 

* Earlier draft reviewed

** Already reviewed

 

 

 

I have made the assignments in the review tool:

 <http://art.tools.ietf.org/tools/art/genart/>
http://art.tools.ietf.org/tools/art/genart/

 

And the assignments are captured in the spreadsheets:

 <http://wiki.tools.ietf.org/dav/genart/gen-art.html>
http://wiki.tools.ietf.org/dav/genart/gen-art.html

 <http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html>
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

 

For your convenience, the review boilerplate template is included below.

 

Note that reviews should ideally be posted to the gen-art mailing list by
COB on Tuesday:

 <http://wiki.tools.ietf.org/area/gen/trac/wiki/>
http://wiki.tools.ietf.org/area/gen/trac/wiki/

 

Peter

 

-------------------------------------------------------------------

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at <
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please wait for direction from your document shepherd or AD before posting a
new version of the draft.

 

Document:

Reviewer:

Review Date:

IETF LC End Date:

IESG Telechat date: (if known)

 

Summary:

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

_______________________________________________

Gen-art mailing list

 <mailto:Gen-art@ietf.org> Gen-art@ietf.org

 <https://www.ietf.org/mailman/listinfo/gen-art>
https://www.ietf.org/mailman/listinfo/gen-art


------=_NextPart_000_03D6_01CE739B.41C3A8F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@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:0in;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The following reviewers have =
assignments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Reviewer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; LC end&nbsp;&nbsp;&nbsp;&nbsp; =
Draft<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
-----------------<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Joel =
Halpern&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2013-06-19 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-ospf-manet-single-hop-mdr-03 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Kathleen =
Moriarty&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-28 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-ipfix-protocol-rfc5101bis-08 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Peter =
Yee&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 2013-06-27 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-appsawg-rfc5451bis-07 ** =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Suresh =
Krishnan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-01-21 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-lisp-mib-11 * (Reassigned from Miguel =
Garcia)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>* Earlier =
draft reviewed<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>** Already =
reviewed<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I have =
made the assignments in the review tool:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"http://art.tools.ietf.org/tools/art/genart/"><span =
style=3D'color:windowtext;text-decoration:none'>http://art.tools.ietf.org=
/tools/art/genart/</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>And the assignments are captured in =
the spreadsheets:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/dav/genart/gen-art.html"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/dav/genart/gen-art.html</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html"><=
span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/dav/genart/gen-art-by-reviewer.html</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>For your convenience, the review =
boilerplate template is included below.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Note that reviews should ideally be =
posted to the gen-art mailing list by COB on =
Tuesday:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/area/gen/trac/wiki/</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Peter<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt; <a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/area/gen/trac/wiki/GenArtfaq</span></a>&gt;.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Please wait for direction from your =
document shepherd or AD before posting a new version of the =
draft.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Document:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Reviewer:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Review =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IETF LC End =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IESG Telechat date: (if =
known)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Summary:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>_______________________________________________<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art mailing list<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"mailto:Gen-art@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>Gen-art@ietf.org</span></=
a><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"https://www.ietf.org/mailman/listinfo/gen-art"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/gen-art</span></a><o:p></o:p></span></p></div></body></html>
------=_NextPart_000_03D6_01CE739B.41C3A8F0--


From curtis@occnc.com  Sat Jun 29 19:03:05 2013
Return-Path: <curtis@occnc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02CA21F9CF7 for <gen-art@ietfa.amsl.com>; Sat, 29 Jun 2013 19:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xdj1o3l2UpLD for <gen-art@ietfa.amsl.com>; Sat, 29 Jun 2013 19:03:02 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id D6D5B21F9CB8 for <gen-art@ietf.org>; Sat, 29 Jun 2013 19:03:01 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r5U20IBo024176; Sat, 29 Jun 2013 22:00:19 -0400 (EDT) (envelope-from curtis@occnc.com)
Message-Id: <201306300200.r5U20IBo024176@gateway1.orleans.occnc.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 27 Jun 2013 18:15:38 +0200." <201306271615.r5RGFcqn049951@givry.fdupont.fr>
Date: Sat, 29 Jun 2013 22:00:18 -0400
X-Mailman-Approved-At: Sat, 29 Jun 2013 20:45:19 -0700
Cc: gen-art@ietf.org, draft-ietf-rtgwg-cl-requirement.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-rtgwg-cl-requirement-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@occnc.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jun 2013 02:03:06 -0000

Francis,

This draft is headed back to WGLC, but I edited in the changes that
you suggested, except as noted.  See inline.

In message <201306271615.r5RGFcqn049951@givry.fdupont.fr>
Francis Dupont writes:
> 
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>  
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>  
> Please resolve these comments along with any other Last Call comments
> you may receive.
>  
> Document: draft-ietf-rtgwg-cl-requirement-10.txt
> Reviewer: Francis Dupont
> Review Date: 20130617
> IETF LC End Date: 20130619
> IESG Telechat date: unknown
>  
> Summary: Ready
>  
> Major issues: None
>  
> Minor issues: None
>  
> Nits/editorial comments:
>  - ToC page 3 and 7 page 12: Acknowledgements -> Acknowledgments

Acceptabel spelling AFAIK.

>  - 2 page 4: double include words in:
>  
>    The services supported include pseudowire based services (RFC 3985
>    [RFC3985]), including VPN services,
>  
>  I suggest something like:
>  
>    The supported services are, but not limited to, pseudowire based
>    services (RFC 3985 [RFC3985]), including VPN services,

This section was moved to the companion draft "Composite Link Use
Cases and Design Considerations" at the request of the RtgDir review
but the change has been made in that document.

>  - 3 page 5 (component link): the term NPO is used before being defined

The term NPO conflicts with ITU-T usage of the term and is no longer
used (another change prompted by the RtgDir review).

>  - 3 page 5 (component link): expand the WDM abbrev -- not well known
>   according tothe RFC Editor list:
>   http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

The paragraph provides non-essential discussion and was moved
out of the definition and appears after the set of definitions.  The
acronyms were in a "for example" context and are now removed.

The text now reads:

   A Component Link may be a point-to-point physical link (where a
   "physical link" includes one or more link layer plus a physical
   layer) or a logical link that preserves ordering in the steady
   state.  A component link may have transient out of order events,
   but such events must not exceed the network's Performance
   Objectives.  For example, a compoent link may be comprised of any
   supportable combination of link layers over a physical layer or
   over logical sub-layers, including those providing physical layer
   emulation.

The examples given used the terms WDM, Ethernet, VLAN, SONET, and OTN
but the examples are now gone.

>  - 3 page 5 (flow identification): same for the PW abbrev

Done.

>  - 4.1 page 6: CAN -> MAY

Done.

>  - 6 page 12 (MR#10) -> interpretted -> interpreted
>  
>  - 9 page 13: Encrption -> Encryption

These two corrections were made.  A spell check of the entire document
was done and it caught a few more errors.

>  - Authors' Addresses: add the country (USA) in postal addresses

Done

> Regards
>  
> Francis.Dupont@fdupont.fr

Thank you for the review.  Please let me know if the changes are
acceptable.

Curtis

From ron.even.tlv@gmail.com  Sat Jun 29 23:46:17 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D4521F9E0E; Sat, 29 Jun 2013 23:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.865
X-Spam-Level: 
X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=0.733,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkzT7OprMUdM; Sat, 29 Jun 2013 23:46:16 -0700 (PDT)
Received: from mail-ea0-x234.google.com (mail-ea0-x234.google.com [IPv6:2a00:1450:4013:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 8406121F9E2D; Sat, 29 Jun 2013 23:46:14 -0700 (PDT)
Received: by mail-ea0-f180.google.com with SMTP id k10so1474675eaj.39 for <multiple recipients>; Sat, 29 Jun 2013 23:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=a5AKKqHA8lQoKMEDEWHsncQlifonfwm77je6HtSQxnM=; b=HV+LsGLBWhiFa/uplePeE5TrNm9An7fNun8eTukZA4L5EqoPt6AH2iNEVlAj++EcJ6 FgtYK72Z7ExK+8ufpuJ/wDUCoBsWBgcmQRXxDLoWExKi8xQp3rmqv/EW32m6osfzB4iZ AvvW5tU0zA23fJsbw60SWlM67RXL3FYDLHynbJDYt4N7Cd7XRgNfzbMLXQO7XyAviZAP W4gf3hrT4XnBwts+Fbox1y8i7rRRg0cshR5M5HsE2WbytKl9H44GDkFrUJzJ+z11w1e8 Su++GobPuIo4QEUqrsI5qqlIX6PJcx8NTqINHCs82NMPDwFifYlmcazF37imIgF/AlDA z1ZQ==
X-Received: by 10.14.178.134 with SMTP id f6mr16079448eem.91.1372574773201; Sat, 29 Jun 2013 23:46:13 -0700 (PDT)
Received: from RoniE ([109.67.165.48]) by mx.google.com with ESMTPSA id i2sm21448812eeu.4.2013.06.29.23.46.10 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 29 Jun 2013 23:46:12 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-merkle-tls-brainpool.all@tools.ietf.org>
Date: Sun, 30 Jun 2013 09:44:45 +0300
Message-ID: <048001ce755d$505996e0$f10cc4a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0481_01CE7576.75A76B20"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac51XUZ2uR+caSBhSvyQOZR9tzTtoA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-merkle-tls-brainpool-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jun 2013 06:46:17 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0481_01CE7576.75A76B20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-merkle-tls-brainpool-02

Reviewer: Roni Even

Review Date:2013-6-30

IETF LC End Date: 2013-7-23

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

In section 1 you reference TLS 1.0 and 1.1 usage based on RFC 4492. What
about TLS 1.2 usage specified in RFC5246 A.7

 

 

 

Nits/editorial comments:

1.	In section 3 the  registry name is EC Named Curve
2.	In section 3 change "suitability" to "suitable"

 


------=_NextPart_000_0481_01CE7576.75A76B20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:510795705;
	mso-list-type:hybrid;
	mso-list-template-ids:1559919828 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span>draft-merkle-tls-brainpool-02<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;6&#8211;30<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-7&#8211;23<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
1 you reference TLS 1.0 and 1.1 usage based on RFC 4492. </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>What about =
TLS 1.2 usage specified in RFC5246 A.7<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>In =
section 3 the&nbsp; registry name is EC Named Curve<o:p></o:p></li><li =
class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>In section 3 change =
&#8220;suitability&#8221; to =
&#8220;suitable&#8221;<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0481_01CE7576.75A76B20--


From gonzalo.camarillo@ericsson.com  Sun Jun 30 23:22:06 2013
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 025F721F9DE2 for <gen-art@ietfa.amsl.com>; Sun, 30 Jun 2013 23:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.793
X-Spam-Level: 
X-Spam-Status: No, score=-105.793 tagged_above=-999 required=5 tests=[AWL=0.456, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mesj9UCLevOQ for <gen-art@ietfa.amsl.com>; Sun, 30 Jun 2013 23:22:01 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4E57221F9F15 for <gen-art@ietf.org>; Sun, 30 Jun 2013 23:22:00 -0700 (PDT)
X-AuditID: c1b4fb30-b7ef76d000004bbc-06-51d12005dde0
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id D7.2C.19388.50021D15; Mon,  1 Jul 2013 08:21:57 +0200 (CEST)
Received: from [131.160.126.77] (153.88.183.17) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.2.328.9; Mon, 1 Jul 2013 08:21:57 +0200
Message-ID: <51D12004.8090102@ericsson.com>
Date: Mon, 1 Jul 2013 09:21:56 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <51C7A88A.9080102@gmail.com> <1670FE635C32C34AAD005D960F1C501115C6F5EF@xmb-aln-x11.cisco.com> <51C857FA.2050304@stpeter.im> <51C9F79F.2060509@gmail.com> <51C9FB6A.5090802@stpeter.im>
In-Reply-To: <51C9FB6A.5090802@stpeter.im>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM+JvrS6rwsVAg9dtZhZtF/cxWdw5upLd 4uqrzywWn/fvZ7a4t7yFzeLYnn5mBzaPKb83snrsnHWX3WPJkp9MHnP3vGD2+HL5M1sAaxSX TUpqTmZZapG+XQJXxqLdhxkLHltXNO7oYm9gnGvQxcjJISFgIrG19ywThC0mceHeerYuRi4O IYHDjBJH57RAOasYJd4t7WLuYuTg4BXQlph/yAukgUVAReLt/5ssIDabgIXEllv3wWxRgSiJ 1t6pzCA2r4CgxMmZT8DiIgJaEpeu9bGDzGQWmMMksezIGnaQhLCAncS6nlZGiGWHGCUWTF3F CJLgBOpYe+MfO8R5khJbXrSD2cwCmhKt239D2fIS29/OAdsmBHTc8mctLBMYhWYhWT4LScss JC0LGJlXMbLnJmbmpJebb2IEBv3BLb8NdjBuui92iFGag0VJnHez3plAIYH0xJLU7NTUgtSi +KLSnNTiQ4xMHJxSDYwBs6SPbbwQp5Z4XY85Rnv9lEUb92+8zMOwR3aC+9+3m5hDU68qK0rJ uv57K+5vdvUuR/Yhpndyr5Xt1q22d3qpqMI89+/+1jO2m29XrmH2lXFYd2fj5wky604azs14 yuxiZ+U8f/fx1hORwQq8R/cHrbc8qrGtIySE2+OZZy/r3R8/Lrb+43ylxFKckWioxVxUnAgA S2yRG0gCAAA=
Cc: "draft-ivov-xmpp-cusax.all@tools.ietf.org" <draft-ivov-xmpp-cusax.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ivov-xmpp-cusax-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 06:22:06 -0000

Hi,

yes, we will revise the draft after the IETF LC and before the IESG review.

Cheers,

Gonzalo

On 25/06/2013 11:19 PM, Peter Saint-Andre wrote:
> Great. I expect that we'll submit a revised I-D before IESG review.
> 
> On 6/25/13 2:03 PM, Brian E Carpenter wrote:
>> Hi Peter,
>>
>> Thanks, that all seems fine in the light of your comments. I would
>> expect to review this as "Ready" when it reaches the IESG agenda.
>>
>> Regards
>>    Brian
>>
>> On 25/06/2013 02:30, Peter Saint-Andre wrote:
>>> On 6/23/13 8:27 PM, Peter Saint-Andre (psaintan) wrote:
>>>> Hi Brian, thanks for the review.
>>>
>>> Here is a provisional diff that addresses your feedback:
>>>
>>> https://github.com/emcho/cusax/commit/1c5e9d681748685360cc6677ea2e369b352e66db#draft-ivov-xmpp-cusax-07.xml
>>>
>>>> On Jun 23, 2013, at 8:01 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>>>>  wrote:
>>>>
>>>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>>>> Gen-ART, please see the FAQ at
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>>
>>>>> Please resolve these comments along with any other Last Call comments
>>>>> you may receive.
>>>>>
>>>>> Document: draft-ivov-xmpp-cusax-06.txt
>>>>> Reviewer: Brian Carpenter
>>>>> Review Date: 2013-06-24
>>>>> IETF LC End Date: 2013-07-16
>>>>> IESG Telechat date:
>>>>>
>>>>> Summary:  Almost ready
>>>>> --------
>>>>>
>>>>> Comment:
>>>>> --------
>>>>>
>>>>> I have some issues, but I don't know whether to classify any of them as
>>>>> major.
>>>>>
>>>>> Issues:
>>>>> -------
>>>>>
>>>>> In Introduction:
>>>>>
>>>>> "  As a result, a number of adopters have found themselves needing
>>>>>   features that are not offered by any single-protocol solution, but
>>>>>   that separately exist in SIP and XMPP implementations.  The idea of
>>>>>   seamlessly using both protocols together would hence often appeal to
>>>>>   service providers. "
>>>>>
>>>>> A few paragraphs later, you discuss the case of an end user who would like
>>>>> to use SIP and XMPP together with *different* service providers.
>>>> Although that's out of scope for this document. We might address that scenario in a future document.
>>>>
>>>>>  I would suggest
>>>>> ending this sentence with "appeal to service providers and users."
>>>> Good point.
>>>>> "  Finally, this document makes a further simplifying assumption by
>>>>>   discussing only the use of a single client, not use of and
>>>>>   coordination among multiple endpoints controlled by the same user
>>>>>   (e.g., user agents running simultaneously on a laptop computer,
>>>>>   tablet, and mobile phone)."
>>>>>
>>>>> Hmm. Isn't that the normal case today, and your simplifying assumption
>>>>> the exception? It's certainly extremely annoying to have different
>>>>> contacts lists on different devices, for example. This seems like a
>>>>> big gap in the model, with no hints on how it might be filled. (As big
>>>>> as the gap between POP3 and IMAP, in some ways.)
>>>> At least in XMPP, you'd have the same contact list on all of those devices. But we can word this more carefully.
>>>>
>>>>> In Client Bootstrap:
>>>>>
>>>>> "  While it should be possible for CUSAX users to manually configure
>>>>>   their separate SIP and XMPP accounts, service providers offering
>>>>>   CUSAX services to users of dual-stack SIP/XMPP clients ought to
>>>>>   provide means of online provisioning,..."
>>>>>
>>>>> 1. I would anyway expect my CUSAX client to come with a configuration
>>>>> wizard, including a path to the online provisioning if available.
>>>> True.
>>>>> 2. Is there any reason why SIP service providers and XMPP service
>>>>> providers shouldn't individually provide on-line provisioning?
>>>> No.
>>>>
>>>> (Something like the technology proposed at the aggsrv BoF in Orlando might help, too, but that's just a gleam in the eye at this point.)
>>>>
>>>>>  You're
>>>>> describing something close to a captive-customer scenario,
>>>> We are indeed assuming that a dual-stack user agent would interact with a combined service (i.e., CUSAX on the client side and CUSAX on the server side).  I am not sure that a customer of such a service is a captive.
>>>>
>>>>> rather than
>>>>> encouraging an open approach to provisioning.
>>>> As far as I can see, no open provisioning protocol is available yet. The aforementioned aggsrv approach might fit the bill. It's too early to say, but we can at least mention the possibility that such a technology might be developed in the future.
>>>>
>>>>> The CUSAX client would
>>>>> in any case have to deal with any inconsistencies in provisioning.
>>>> I'm not sure what actionable advice we can provide here, but I'll discuss with with my co-authors.
>>>>> In Server-Side Setup:
>>>>>
>>>>> "  In order for CUSAX to function properly, XMPP service administrators
>>>>>   should make sure that at least one of the vCard [RFC6350] "tel"
>>>>>   fields for each contact is properly populated with a SIP URI or a
>>>>>   phone number when an XMPP protocol for vCard storage is used (e.g.,..."
>>>>>
>>>>> How can they do that, given that users are normally responsible for
>>>>> maintaining their contacts lists?
>>>> When a user uploads their vCard (or, say, modifies it in a web interface), the server could apply automated checks or make the "tel" field mandatory.
>>>>> In Summary of Suggested Practices:
>>>>>
>>>>> "  1.   By default, prefer SIP for audio and video, and XMPP for
>>>>>        messaging and presence."
>>>>>
>>>>> At the beginning of the Operation section, this seems to be stated as
>>>>> a rule, not as a default (" Audio/video features however, are disabled
>>>>> in the XMPP stack..."). Which is it?
>>>> I'm not seeing a huge difference here -- the XMPP stack in the CUSAX user agent might have audio/video capabilities, but typically those would be disabled (disabled by default, but the user might be allowed to turn them on for certain kinds of contacts, etc.).
>>>>
>>>> I suggest this change in the Operation section.
>>>>
>>>> OLD
>>>>    Audio/video features however, are
>>>>    disabled in the XMPP stack, so any form of communication based on
>>>>    these features (e.g. direct calls, conferences, desktop streaming,
>>>>    etc.) will happen over SIP.
>>>>
>>>> NEW
>>>>    Audio/video features however, would typically be
>>>>    disabled in the XMPP stack, so any form of communication based on
>>>>    these features (e.g. direct calls, conferences, desktop streaming,
>>>>    etc.) would happen over SIP.
>>>>
>>>>> In Security Considerations:
>>>>>
>>>>> "  ... a CUSAX client might
>>>>>   successfully negotiate Transport Layer Security (TLS) [RFC5246] when
>>>>>   connecting to the XMPP aspect of the service but not when connecting
>>>>>   to the SIP aspect.  Such mismatches could introduce the possibility
>>>>>   of downgrade attacks."
>>>>>
>>>>> I'd say *would* introduce the possibility.
>>>> Yes, that's more accurate.
>>>>
>>>>>  It would seem possible for a
>>>>> bad actor to pick up authentication data from the insecure service and
>>>>> exploit it to attack the secured service. Therefore,
>>>>>
>>>>> "  User agent developers and service providers
>>>>>   ought to ensure that such mismatches are avoided as much as possible."
>>>>>
>>>>> seems a bit weak. Shouldn't the client also be *required* to alert the user
>>>>> that the session as a whole is not secured?
>>>>>
>>>> IMHO that would be advisable. Good catch.
>>>>
>>>> Peter
>>>>
>>>
> 

