draft-ietf-ipdvb-sec-req-09 - draft publication request

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 01 September 2008 10:26 UTC

Return-Path: <owner-ipdvb@erg.abdn.ac.uk>
X-Original-To: ietfarch-ipdvb-archive@core3.amsl.com
Delivered-To: ietfarch-ipdvb-archive@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 157C93A6925 for <ietfarch-ipdvb-archive@core3.amsl.com>; Mon, 1 Sep 2008 03:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.173
X-Spam-Status: No, score=-1.173 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_20=-0.74]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1tn7W3hLlZaY for <ietfarch-ipdvb-archive@core3.amsl.com>; Mon, 1 Sep 2008 03:26:52 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 6609D3A6962 for <ipdvb-archive@ietf.org>; Mon, 1 Sep 2008 03:26:51 -0700 (PDT)
Received: from dee.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id m819wePC026395 for <ipdvb-subscribed-users@dee.erg.abdn.ac.uk>; Mon, 1 Sep 2008 10:58:40 +0100 (BST)
Received: (from majordomo.lists@localhost) by dee.erg.abdn.ac.uk (8.13.4/8.12.2/Submit) id m819weYS026394 for ipdvb-subscribed-users; Mon, 1 Sep 2008 10:58:40 +0100 (BST)
X-Authentication-Warning: dee.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk []) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id m819wKYd026355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 1 Sep 2008 10:58:21 +0100 (BST)
Message-ID: <48BBBCBD.8080709@erg.abdn.ac.uk>
Date: Mon, 01 Sep 2008 10:58:21 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683.
User-Agent: Thunderbird (Macintosh/20080707)
MIME-Version: 1.0
To: Mark Townsley <townsley@cisco.com>
CC: "ipdvb@erg.abdn.ac.uk" <ipdvb@erg.abdn.ac.uk>, Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: draft-ietf-ipdvb-sec-req-09 - draft publication request
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean, Found to be clean
Sender: owner-ipdvb@erg.abdn.ac.uk
Precedence: bulk
Reply-To: ipdvb@erg.abdn.ac.uk
X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk

Dear Mark,

Here is the publication request for draft-ietf-ipdvb-sec-req-09 to be
published as INFO. The WG has finally have managed to address the
SECDIR comments and it was good to see new people involved in the
discussions as we progressed to conclusion of this draft.

Best wishes,



As required by RFC-to-be draft-ietf-proto-wgchair-doc-shepherding,
this is the current template for the Document Shepherd Write-Up.
Changes are expected over time.  This version is dated February 1, 2007.

    (1.a)  Who is the Document Shepherd for this document?  Has the
           Document Shepherd personally reviewed this version of the
           document and, in particular, does he or she believe this
           version is ready for forwarding to the IESG for publication?

This is a publication request from the IPDVB WG. I have read this 
document (draft-ietf-ipdvb-sec-req-09) and I think this
is ready for publication. The document shepherd is G Fairhurst
(gorry@erg.abdn.ac.uk) IPDVB WG Chair.

    (1.b)  Has the document had adequate review both from key WG members
           and from key non-WG members?  Does the Document Shepherd have
           any concerns about the depth or breadth of the reviews that
           have been performed?

Yes, A previous version of the document was reviewed in a WGLC prior to
IETF-71 (and received comments from DVB and the ETSI/BSM WG were it was
cross-posted). It was also submitted at this time for a SECDIR review, 
which revealed a set of issues. These issues were addressed in revision 
07 and 08 revs of the draft.

A new author - active within the group for some time, also made 
substantial contributions to the 08 revision, which was submitted
to a WGLC that concluded on 1-Aug-08. During this LC, 3 reviewers plus
the chair submitted new comments, which have been addressed in rev -09.

    (1.c)  Does the Document Shepherd have concerns that the document
           needs more review from a particular or broader perspective,
           e.g., security, operational complexity, someone familiar with
           AAA, internationalization or XML?

No, it seems that all the previously raised concerns have been
adequately addressed in the latest revision of the document.

    (1.d)  Does the Document Shepherd have any specific concerns or
           issues with this document that the Responsible Area Director
           and/or the IESG should be aware of?  For example, perhaps he
           or she is uncomfortable with certain parts of the document, or
           has concerns whether there really is a need for it.  In any
           event, if the WG has discussed those issues and has indicated
           that it still wishes to advance the document, detail those
           concerns here.  Has an IPR disclosure related to this document
           been filed?  If so, please include a reference to the
           disclosure and summarize the WG discussion and conclusion on
           this issue.

    (1.e)  How solid is the WG consensus behind this document?  Does it
           represent the strong concurrence of a few individuals, with
           others being silent, or does the WG as a whole understand and
           agree with it?

The working group supported this work.

    (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
           discontent?  If so, please summarise the areas of conflict in
           separate email messages to the Responsible Area Director.  (It
           should be in a separate email because this questionnaire is
           entered into the ID Tracker.)


    (1.g)  Has the Document Shepherd personally verified that the
           document satisfies all ID nits?  (See
           http://www.ietf.org/ID-Checklist.html and
           http://tools.ietf.org/tools/idnits/).  Boilerplate checks are
           not enough; this check needs to be thorough.  Has the document
           met all formal review criteria it needs to, such as the MIB
           Doctor, media type and URI type reviews?


    (1.h)  Has the document split its references into normative and
           informative?  Are there normative references to documents that
           are not ready for advancement or are otherwise in an unclear
           state?  If such normative references exist, what is the
           strategy for their completion?  Are there normative references
           that are downward references, as described in [RFC3967]?  If
           so, list these downward references to support the Area
           Director in the Last Call procedure for them [RFC3967].

The references have been verified.

    (1.i)  Has the Document Shepherd verified that the document IANA
           consideration section exists and is consistent with the body
           of the document?  If the document specifies protocol
           extensions, are reservations requested in appropriate IANA
           registries?  Are the IANA registries clearly identified?  If
           the document creates a new registry, does it define the
           proposed initial contents of the registry and an allocation
           procedure for future registrations?  Does it suggest a
           reasonable name for the new registry?  See [RFC2434].  If the
           document describes an Expert Review process has Shepherd
           conferred with the Responsible Area Director so that the IESG
           can appoint the needed Expert during the IESG Evaluation?

There are no IANA actions required for this document.

    (1.j)  Has the Document Shepherd verified that sections of the
           document that are written in a formal language, such as XML
           code, BNF rules, MIB definitions, etc., validate correctly in
           an automated checker?

Not appropriate.

    (1.k)  The IESG approval announcement includes a Document
           Announcement Write-Up.  Please provide such a Document
           Announcement Write-Up?  Recent examples can be found in the
           "Action" announcements for approved documents.  The approval
           announcement contains the following sections:

           Technical Summary
              Relevant content can frequently be found in the abstract
              and/or introduction of the document.  If not, this may be
              an indication that there are deficiencies in the abstract
              or introduction.

This document provides a threat analysis and derives the security
requirements when using the Transport Stream, TS, to support an Internet
network-layer using the Unidirectional Lightweight Encapsulation
(ULE) defined in RFC4326. The document also provides the
motivation for link-layer security for a ULE Stream. A ULE Stream
may be used to send IPv4 packets, IPv6 packets, and other
Protocol Data Units (PDUs) to an arbitrarily large number of
Receivers supporting unicast and/or multicast transmission.

           Working Group Summary
              Was there anything in WG process that is worth noting?  For
              example, was there controversy about particular points or
              were there decisions where the consensus was particularly

This document builds on RFC 4326, and identifies a set of
security-related topics that impact IP operation over a range of
broadcast links supporting IP.

           Document Quality
              Are there existing implementations of the protocol?  Have a
              significant number of vendors indicated their plan to
              implement the specification?  Are there any reviewers that
              merit special mention as having done a thorough review,
              e.g., one that resulted in important changes or a
              conclusion that the document had no substantive issues?  If
              there was a MIB Doctor, Media Type or other expert review,
              what was its course (briefly)?  In the case of a Media Type
              review, on what date was the request posted?

The IPDVB WG has reached consensus that this document is ready for
publication as an informational RFC. This document does not define a
protocol or new mechanism.