RE: RADEXT Issue 148 Items 2 and 3

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

Just to make sure - the text mentioned in comment 3 of the review, which
appears in all four documents in the Deprecated Objects sections is to
be replaced by the suggested text. 

Regards,

Dan


 
 

> -----Original Message-----
> From: Nelson, David [mailto:dnelson@enterasys.com] 
> Sent: Friday, December 09, 2005 5:26 PM
> To: radiusext@ops.ietf.org
> Cc: Romascanu, Dan (Dan)
> Subject: RADEXT Issue 148 Items 2 and 3
> 
> The following text is proposed as a resolution to RADEXT 
> Issue 148, Items 2 and 3:
> 
> <quote>
> 
> Managed entities SHOULD NOT instantiate row entries in the 
> deprecated table, containing IPv4-only address objects, when 
> the RADIUS server address represented in such a table row is 
> not an IPv4 address.  Managed entities SHOULD NOT return 
> inaccurate values of IP address or SNMP object access errors 
> for IPv4-only address objects in otherwise populated tables.  
> When row entries exist in both the deprecated IPv4-only table 
> and the new IP version neutral table, that describe the same 
> RADIUS server, the row indexes SHOULD be the same for the 
> corresponding rows in each table, to facilitate correlation 
> of these related rows by management applications.
> 
> </quote>
> 
> This text appears in Section 6. Deprecated Objects.
> 
> 

--
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/>