Re: [radext] [IANA #935820] Protocol Action: 'RADIUS Extensions for IP Port Configuration and Reporting' to Proposed Standard (draft-ietf-radext-ip-port-radius-ext-16.txt)

[Dean cheng <[e-mail]>]

Hi Amanda,

We've just posted the new revision of this draft (17.txt).

Thanks
Dean

> -----Original Message-----
> From: radext [mailto:[e-mail]] On Behalf Of Dean cheng
> Sent: Monday, November 14, 2016 7:13 PM
> To: [e-mail]
> Cc: [e-mail]
> Subject: Re: [radext] [IANA #935820] Protocol Action: 'RADIUS
> Extensions for IP Port Configuration and Reporting' to Proposed
> Standard (draft-ietf-radext-ip-port-radius-ext-16.txt)
> 
> Hello Amanda,
> 
> Thank you for all the three actions taken for the registry, which I've
> reviewed and found them correct.
> 
> I'll update the draft with the newly assigned numbers before post the
> 17.txt and let you know.
> 
> Regards
> Dean
> 
> > -----Original Message-----
> > From: radext [mailto:[e-mail]] On Behalf Of Amanda
> > Baber via RT
> > Sent: Monday, November 14, 2016 6:12 PM
> > Cc: [e-mail]
> > Subject: [radext] [IANA #935820] Protocol Action: 'RADIUS Extensions
> > for IP Port Configuration and Reporting' to Proposed Standard (draft-
> > ietf-radext-ip-port-radius-ext-16.txt)
> >
> > Dear Authors:
> >
> > ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED
> >
> > We've completed the registry actions for the following RFC-to-be:
> >
> > draft-ietf-radext-ip-port-radius-ext-16
> >
> > ACTION 1:
> >
> > The IANA Services Operator has added the following entry to the IPFIX
> > Information Elements registry:
> >
> > Element ID: 458
> > Name: sourceTransportPortsLimit
> > Data Type: unsigned16
> > Data Type Semantics: totalCounter
> > Status: current
> > Description: This Information Element contains the maximum number of
> > IP source transport ports that can be used by an end user when
> sending
> > IP packets; each user is associated with one or more (source) IPv4 or
> > IPv6 addresses. This IE is particularly useful in address sharing
> > deployments that adhere to REQ-4 of [RFC6888]. Limiting the number of
> > ports assigned to each user ensures fairness among users and
> mitigates
> > the denial-of-service attack that a user could launch against other
> > users through the address sharing device in order to grab more ports.
> > Units: ports
> > Range: 1-65535
> > Requester: [RFC-ietf-radext-ip-port-radius-ext-16]
> > Revision: 0
> > Date: 2016-11-10
> >
> > Please see
> > http://www.iana.org/assignments/ipfix
> >
> >
> > ACTION 2:
> >
> > We've added the following entries to the Radius Attribute Types
> > registry:
> >
> > 241.5    IP-Port-Limit-Info    [RFC-ietf-radext-ip-port-radius-ext-16,
> > Section 3.1.1]
> > 241.6    IP-Port-Range    [RFC-ietf-radext-ip-port-radius-ext-16,
> > Section 3.1.2]
> > 241.7    IP-Port-Forwarding-Map    [RFC-ietf-radext-ip-port-radius-
> ext-
> > 16, Section 3.1.3]
> >
> > Please see
> > http://www.iana.org/assignments/radius-types
> >
> >
> > ACTION 3:
> >
> > We've created the following registry under the "Radius Types" heading:
> >
> > RADIUS IP Port Configuration and Reporting TLVs Registration
> > Procedure(s): Standards Action
> > Reference: [RFC-ietf-radext-ip-port-radius-ext-16]
> >
> > Value 	Description 	Reference
> > 0	Reserved	[RFC-ietf-radext-ip-port-radius-ext-16]
> > 1	IP-Port-Type	[RFC-ietf-radext-ip-port-radius-ext-16, Section
> > 3.2.1]
> > 2	IP-Port-Limit	[RFC-ietf-radext-ip-port-radius-ext-16, Section
> > 3.2.2]
> > 3	IP-Port-Ext-IPv4-Addr	[RFC-ietf-radext-ip-port-radius-ext-16,
> > Section 3.2.3]
> > 4	IP-Port-Int-IPv4-Addr	[RFC-ietf-radext-ip-port-radius-ext-16,
> > Section 3.2.4]
> > 5	IP-Port-Int-IPv6-Addr	[RFC-ietf-radext-ip-port-radius-ext-16,
> > Section 3.2.5]
> > 6	IP-Port-Int-Port	[RFC-ietf-radext-ip-port-radius-ext-16, Section
> > 3.2.6]
> > 7	IP-Port-Ext-Port	[RFC-ietf-radext-ip-port-radius-ext-16, Section
> > 3.2.7]
> > 8	IP-Port-Alloc	[RFC-ietf-radext-ip-port-radius-ext-16, Section
> > 3.2.8]
> > 9	IP-Port-Range-Start	[RFC-ietf-radext-ip-port-radius-ext-16,
> > Section 3.2.9]
> > 10	IP-Port-Range-End	[RFC-ietf-radext-ip-port-radius-ext-16, Section
> > 3.2.10]
> > 11	IP-Port-Local-Id	[RFC-ietf-radext-ip-port-radius-ext-16, Section
> > 3.2.11]
> > 12-155	Unassigned
> >
> > Please see
> > http://www.iana.org/assignments/radius-types
> >
> >
> > The updated list of Protocol Registries is available here:
> >
> > http://www.iana.org/protocols/
> >
> > Please let us know whether the above registry actions have been
> > completed correctly. As soon as we receive your confirmation, we'll
> > notify the RFC Editor that this document's actions are complete. If
> > the document has a team of authors, one reply on behalf of everyone
> > will suffice.
> >
> > Since you'll be uploading the new version of the document shortly
> (the
> > new values can be added to that version before you upload), please
> let
> > us know when this is available to link to.
> >
> > We'll make any further reference updates in the registries when the
> > RFC Editor notifies us that they've assigned an RFC number.
> >
> > Best regards,
> >
> > Amanda Baber
> > Lead IANA Services Specialist
> > PTI
> >
> > _______________________________________________
> > radext mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/radext
> 
> _______________________________________________
> radext mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/radext

--- Begin Message ---

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions of the IETF.

        Title           : RADIUS Extensions for IP Port Configuration and Reporting
        Authors         : Dean Cheng
                          Jouni Korhonen
                          Mohamed Boucadair
                          Senthil Sivakumar
	Filename        : draft-ietf-radext-ip-port-radius-ext-17.txt
	Pages           : 39
	Date            : 2016-11-14

Abstract:
   This document defines three new RADIUS attributes.  For devices that
   implement IP port ranges, these attributes are used to communicate
   with a RADIUS server in order to configure and report IP transport
   ports, as well as mapping behavior for specific hosts.  This
   mechanism can be used in various deployment scenarios such as
   Carrier-Grade NAT, IPv4/IPv6 translators, Provider WLAN Gateway, etc.
   This document defines a mapping between some RADIUS attributes and
   IPFIX Information Element Identifiers.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-radext-ip-port-radius-ext/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-radext-ip-port-radius-ext-17

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-radext-ip-port-radius-ext-17


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
radext mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/radext

--- End Message ---