DSL Forum Vendor-Specific RADIUS Attributes
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: RFC Editor <email@example.com> Cc: The IESG <firstname.lastname@example.org>, <email@example.com>, firstname.lastname@example.org Subject: Re: Informational RFC to be: draft-mammoliti-radius-dsl-vsa-04.txt The IESG has no problem with the publication of 'DSL Forum Vendor-Specific RADIUS Attributes' <draft-mammoliti-radius-dsl-vsa-04.txt> as an Informational RFC. The IESG would also like the IRSG or RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14249&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Dan Romascanu. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mammoliti-radius-dsl-vsa-04.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
Technical Summary This document describes the set of Remote Authentication Dial in User Service Vendor-Specific Attributes (RADIUS VSAs) defined by the DSL Forum. These attributes are designed to transport Digital Subscriber Line (DSL) information which is not supported by the standard RADIUS attribute set. It is expected that this document will be updated if and when the DSL Forum defines additional vendor-specific attribute, since its primary purpose is to provide a reference for DSL equipment vendors wishing to interoperate with other vendors' products. Working Group Summary This is Individual submission to the RFC Editor. The RADEXT WG Chair reviewed the document. The usage of Vendor Specific Attributes (VSAs) by other SDOs is an open issue in the RADEXT WG, and some particpants are of the opinion that no guarantee can be given about interoperability, but this does not prevent the publication of the document as an Informational RFC. Protocol Quality This document is a individual submission to the RFC Editor and targets Informational RFC. The document was reviewed by David Nelson (RADEXT WG chair) for compatibility with the RADIUS process and attributes space and by Joel Halpern for the RFC Editor. Note to RFC Editor Please add the following note as per RFC 3932, Section 4. This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment. See RFC 3932 for more information.