Generalized SCSI: A Generic Structure for Interface Switching Capability Descriptor (ISCD) Switching Capability Specific Information (SCSI)
draft-ietf-teas-gmpls-scsi-04

[Ballot discuss]
I do have a concern about error handling that should be pretty simple to fix.

* Section 3

The document needs to specify the error handling on the receiver when the SCSI-TLV length is not a multiple of 4 octets. Are the following SCSI-TLVs processed or is everything ignored? Is there an error message sent?

[Ballot comment]
- 6, paragraph 2: I think the draft needs to specify where IANA will put the registry, not leave it up to their discretion.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-ietf-teas-gmpls-scsi-03.txt. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete.

A new registry is to be created called the "Generalized SCSI (Switching Capability Specific Information) TLVs Types" registry. This new registry will be created on the Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters registry page located at:

https://www.iana.org/assignments/gmpls-sig-parameters/

The new registry will be maintained using Specification Required as defined by RFC 5226. There are initial registrations in the new registry as follows:

Value SCSI-TLV Switching Type Reference
--------- ----------------------- -------------- -------------
0 Reserved [ RFC-to-be ]
1-65535 Unassigned (value list) [ RFC-to-be ]

The IANA Services Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC: db3546@att.com, Vishnu Beeram , teas-chairs@ietf.org, teas@ietf.org, vbeeram@juniper.net, draft-ietf-teas-gmpls-scsi@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Generalized Interface Switching Capability Descriptor - Switching Capability Specific Information) to Proposed Standard


The IESG has received a request from the Traffic Engineering Architecture and
Signaling WG (teas) to consider the following document: - 'Generalized
Interface Switching Capability Descriptor - Switching
  Capability Specific Information'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-07-13. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  This document defines a generic information structure for information
  carried in routing protocol Interface Switching Capability Descriptor
  (ISCD) Switching Capability Specific Information (SCSI) fields.  This
  "Generalized SCSI" can be used with routing protocols that define
  GMPLS ISCDs, and any specific technology.  This document does not
  modify any existing technology specific formats and is defined for
  use in conjunction with new GMPLS Switching Capability types.  The
  context for this document is Generalized MPLS, and the reader is
  expected to be familiar with the GMPLS architecture and associate
  protocol standards.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-teas-gmpls-scsi/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-teas-gmpls-scsi/ballot/


No IPR declarations have been submitted directly on this I-D.

> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.

> Changes are expected over time. This version is dated 24 February 2012.

> (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)? 

Standards Track.

> Why is this the proper type of RFC? 

Standards Track is apt because the document defines link-state routing
protocol related format.

> Is this type of RFC indicated in the title page header?

Yes.

> (2) 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 defines a generic information structure for information
carried in routing protocol Interface Switching Capability Descriptor
(ISCD) Switching Capability Specific Information (SCSI) fields.  This
"Generalized SCSI" can be used with routing protocols that define
GMPLS ISCDs, and any specific technology.  This document does not
modify an existing technology specific formats and is defined for use
in conjunction with new GMPLS Switching Capability types.

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

This document was put together to address comments that were raised
during Gen-ART review for draft-ietf-ccamp-ospf-availability-extension.
This document has been fairly noncontroversial.

> 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 base (G)MPLS routing protocols have been implemented. The generic
protocol format discussed in this document is compatible with earlier
implementations. The first document that would be using the format
defined in this document is draft-ietf-ccamp-ospf-availability-extension.
While there have been no public statements on implementation, the authors
of draft-ietf-ccamp-ospf-availability-extension are from multiple vendors,
and implementation is expected.

> Personnel
>
>  Who is the Document Shepherd?

Vishnu Pavan Beeram

> Who is the Responsible Area Director?

Deborah Brungard

> (3) Briefly describe the review of this document that was performed by
> the Document Shepherd.  If this version of the document is not ready
> for publication, please explain why the document is being forwarded to
> the IESG.

The Document Shepherd has reviewed the document as it has progressed
through the WG. The Shepherd believes this document is ready for publication.

> (4) Does the document Shepherd have any concerns about the depth or
> breadth of the reviews that have been performed?

No.

> (5) Do portions of the document need review from a particular or from
> broader perspective, e.g., security, operational complexity, AAA, DNS,
> DHCP, XML, or internationalization?

No.

> If so, describe the review that took place.

N/A.


> (6) Describe any specific concerns or issues that the Document Shepherd
> has 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.

No specific concerns.

> (7) Has each author confirmed that any and all appropriate IPR
> disclosures required for full conformance with the provisions of BCP 78
> and BCP 79 have already been filed. If not, explain why.

Yes, see thread -
https://mailarchive.ietf.org/arch/msg/teas/IXs2ZYF2wSXVWbj5-VTpWYV18hk


> (8) Has an IPR disclosure been filed that references this document?
> If so, summarize any WG discussion and conclusion regarding the IPR
> disclosures.

No disclosures have been made.

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

Solid among those who are interested. "strong concurrence of a few
individuals, with others being silent" is a reasonable
characterization.

> (10) 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 publicly available.)

No discontent seen.

> (11) Identify any ID nits the Document Shepherd has found in this
> document. (See https://www.ietf.org/tools/idnits/ and the Internet-Drafts
> Checklist). Boilerplate checks are not enough; this check needs to be
> thorough.

The document passes the basic ID nits. There is a warning raised for a
missing reference ('This ID' is mentioned on line 185, but not defined) —
but this is innocuous and can be ignored.

> (12) Describe how the document meets any required formal review
> criteria, such as the MIB Doctor, media type, and URI type reviews.

N/A.

> (13) Have all references within this document been identified as
> either normative or informative?

Yes.

> (14) 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 plan for their completion?

No.

> (15) Are there downward normative references (see RFC 3967)?
> If so, list these downward references to support the Area Director in
> the Last Call procedure.

No.

> (16) Will publication of this document change the status of any
> existing RFCs? Are those RFCs listed on the title page header, listed
> in the abstract, and discussed in the introduction? If the RFCs are not
> listed in the Abstract and Introduction, explain why, and point to the
> part of the document where the relationship of this document to the
> other RFCs is discussed. If this information is not in the document,
> explain why the WG considers it unnecessary.

No.

> (17) Describe the Document Shepherd's review of the IANA considerations
> section, especially with regard to its consistency with the body of the
> document. Confirm that all protocol extensions that the document makes
> are associated with the appropriate reservations in IANA registries.
> Confirm that any referenced IANA registries have been clearly
> identified. Confirm that newly created IANA registries include a
> detailed specification of the initial contents for the registry, that
> allocations procedures for future registrations are defined, and a
> reasonable name for the new registry has been suggested (see RFC 5226).

The IANA section was fully reviewed by the document shepherd. IANA is requested
to create and maintain a new registry for the protocol extension made in
the document. The document includes a detailed specification of the initial
contents for the new registry. The allocations procedures for future
registrations are defined, and a reasonable name for the new registry
has been suggested.


> (18) List any new IANA registries that require Expert Review for future
> allocations. Provide any public guidance that the IESG would find
> useful in selecting the IANA Experts for these new registries.

IANA is requested to create and maintain a new registry called the
“Generalized SCSI (Switching Capability Specific Information) TLVs
Types”. The following text (which should be removed before publication)
in the IANA Considerations section provides guidance on selecting Expert
Reviewers for this registry:
“The designated expert will be appointed by the Routing AD.  It is suggested
to appoint any current TEAS WG chair.”

> (19) Describe reviews and automated checks performed by the Document
> Shepherd to validate sections of the document written in a formal
> language, such as XML code, BNF rules, MIB definitions, etc.

N/A.