Issue: InetPortNumber range

"Bernard Aboba" <bernard_aboba@hotmail.com> Sun, 14 May 2006 19:27 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Sun, 14 May 2006 19:28:01 +0000
Message-ID: <BAY106-F2496AEB50EC97643E53F9793A20@phx.gbl>
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: radiusext@ops.ietf.org
Bcc:
Subject: Issue: InetPortNumber range
Date: Sun, 14 May 2006 12:27:09 -0700
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"

From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com
To: radiusext@ops.ietf.org
Subject: RE: I-D ACTION:draft-ietf-radext-dynauth-client-mib-05.txt
Date: Thu, 11 May 2006 15:37:28 +0200

I think this document is fine now.
However, when I read:
    radiusDynAuthServerClientPortNumber OBJECT-TYPE
           SYNTAX     InetPortNumber
           MAX-ACCESS read-only

           STATUS     current
           DESCRIPTION
                 "The UDP destination port that the RADIUS Dynamic
                  Authorization Client is using to send requests to this
                  server. The value zero is invalid."
           ::= { radiusDynAuthServerEntry 4 }

I think I would make that

           SYNTAX     InetPortNumber (1..65535)
So that it is also determinable by machine that zero is invalid.
I know that I only pointed out that according to RFC4001 you must state
what zero means. But if the value is not allowed, as I now understand it,
then I think using the SYNTAX I suggest is better.

Bert



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

Issue: InetPortNumber range Bernard Aboba