Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
draft-ietf-rserpool-common-param-18

IANA Last Call comments:

IANA has questions:

- Can you please verify that Parameter Type 0x0 is reserved but
all the rest of the parameters are available for assignment?
If so, please adjust the document accordingly.

- Can you please verify that Error Code 0x0 is reserved but
all the rest of the parameters are available for assignment?
If so, please adjust the document accordingly.

- Shouldn't you have a reference to draft-ietf-rserpool-asap-19.txt
in section 4 to make it clear where the message types come from?

Action 1:

Upon approval of this document, the IANA will create the registry
"RSerPool Parameter Types" at
http://www.iana.org/assignments/TBD

Registration Procedures: Specification Required
Initial contents of this registry will be:

Note: The Parameter Types are encoded such that the highest-order
two bits specify the action that must be taken if the processing
endpoint does not recognize the Parameter Type.

00 Stop processing this ENRP or ASAP message and discard it, do
not process any further parameters within it.

01 Stop processing this ENRP or ASAP message and discard it, do
not process any further parameters within it, and report the
unrecognized parameter in an 'Unrecognized Parameter' error
(see Section 3.12).

10 Skip this parameter and continue processing.

11 Skip this parameter and continue processing, but report the
unrecognized parameter in an 'Unrecognized Parameter' error
(see Section 3.12).

Registry:

Value Parameter Type Reference
-------- ----------------------------- ---------
0x0 (reserved by IETF) [RFC-rserpool-common-param-16]
0x1 IPv4 Address [RFC-rserpool-common-param-16]
0x2 IPv6 Address [RFC-rserpool-common-param-16]
0x3 DCCP Transport [RFC-rserpool-common-param-16]
0x4 SCTP Transport [RFC-rserpool-common-param-16]
0x5 TCP Transport [RFC-rserpool-common-param-16]
0x6 UDP Transport [RFC-rserpool-common-param-16]
0x7 UDP-Lite [RFC-rserpool-common-param-16]
0x8 Pool Member Selection Policy [RFC-rserpool-common-param-16]
0x9 Pool Handle [RFC-rserpool-common-param-16]
0xa Pool Element [RFC-rserpool-common-param-16]
0xb Server Information [RFC-rserpool-common-param-16]
0xc Operation Error [RFC-rserpool-common-param-16]
0xd Cookie [RFC-rserpool-common-param-16]
0xe PE Identifier [RFC-rserpool-common-param-16]
0xf PE Checksum [RFC-rserpool-common-param-16]
0x10 Opaque Transport [RFC-rserpool-common-param-16]
0x11- Available for assignment [RFC-rserpool-common-param-16]
0xffff


Action 2:

Upon approval of this document, the IANA will create the registry
"RSerPool Error Causes" at
http://www.iana.org/assignments/TBD

Registration Procedures: Specification Required
Initial contents of this registry will be:

Cause Code Value Cause Code Reference
------------------ ----------------------------------------- ------------
0x0 Unspecified Error
[RFC-rserpool-common-param-16]
0x1 Unrecognized Parameter
[RFC-rserpool-common-param-16]
0x2 Unrecognized Message
[RFC-rserpool-common-param-16]
0x3 Invalid Values
[RFC-rserpool-common-param-16]
0x4 Non-unique PE Identifier
[RFC-rserpool-common-param-16]
0x5 Inconsistent Pooling Policy
[RFC-rserpool-common-param-16]
0x6 Lack of Resources
[RFC-rserpool-common-param-16]
0x7 Inconsistent Transport Type
[RFC-rserpool-common-param-16]
0x8 Inconsistent Data/Control Configuration
[RFC-rserpool-common-param-16]
0x9 Unknown Pool Handle
[RFC-rserpool-common-param-16]
0xa Rejected due to security considerations
[RFC-rserpool-common-param-16]
0xb-0xffff Available for assignment
[RFC-rserpool-common-param-16]


We understand the above to be the only IANA Actions for this
document.

RFC 4858 Writeup for ASAP, ENRP and Common Parameters specifications (draft-ietf-rserpool-asap-17.txt, draft-ietf-rserpool-enrp-17.txt and draft-ietf-rserpool-common-param-13.txt)

(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?

No Document Shepherd has been appointed for this document, the
Working Group Chairs are taking responsibility for reviewing and
Forwarding the document.

  (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?

The documents have been reviewed by key WG members.

We have had a number of external comments, most particularly a detailed review and comments from Scott Bradner, former Transport AD.

  (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 concerns that we know of.

  (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.

There are no IPR filings on any of these documents.

  (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?

There is strong WG consensus on these documents.

  (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
          discontent?  If so, please summarize 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.)

No one has threatened an appeal or otherwise objected.

  (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?  If the document
          does not already indicate its intended status at the top of
          the first page, please indicate the intended status here.

Nit checker has been run on the documents successfully.  We are submitting the
Protocol documents as experimental.  The overview and threats can be either
Informational or experimental.

  (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].

Yes, references are split as required. 

  (1.i)  Has the Document Shepherd verified that the document's IANA
          Considerations 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 the Document
          Shepherd conferred with the Responsible Area Director so that
          the IESG can appoint the needed Expert during IESG Evaluation?

IANA considerations are documented in the ENRP, ASAP and Common Parameters drafts.  These are consistent with the bodies of the respective drafts.  The documents require that new registries be created for the ENRP and ASAP protocol parameters and provide initial contents of the registries plus allocation procedures for future registrations.  Naming and appropriate policies are called out for allocation of future values based on the Specification Required procedure defined in RFC 2434.

  (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?

There are no sections written in a formal language.

  (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

The three drafts provide a set of protocols and parameter definitions supporting Reliable Server Pooling requirements, as defined in RFC 3237.  ASAP defines a protocol for communication between server pool members and server pool users that supports functions such as server registration and lookup, liveness detection and limited failover.  ENRP defines a protocol for communication between name resolution servers that supports a fault-tolerant registry function for handling pool operation and membership information.  Parameter formats and codepoint assignments for both ASAP and ENRP are provided in a Common Parameters specification.

Working Group Summary

The Working Group process was constrained by the relatively small number of people actively involved (although those involved were committed to doing implementations of the protocols).  Otherwise there was little controversy within the group.

Document Quality

There are multiple implementations of both ENRP and ASAP protocols, thanks to participants.  However, there are no vendors that have indicated plans for implementation.  Based on this and the limited number of participants, Experimental track seems appropriate.  We received detailed comments and review from Scott Bradner and his help was greatly appreciated.

Personnel

Document Shepherding is being provided by the Working Group chairs, Maureen Stillman and Lyndon Ong.  Responsible Area Director is Magnus Westerland.