Re: [IPFIX] "ID" in Information Element names

Andrew,

I agree. There seems to be some inconsistency here.

IPFIX-doctors says:

    o  use capital letters for the first letter of each component except
       for the first one (aka "camel case").  All other letters are non-
       capitalized, even for acronyms.  Exceptions are made for acronyms
       containing non-capitalized letters, such as 'IPv4' and 'IPv6'.
       Examples are "sourceMacAddress" and "destinationIPv4Address."


So it seems that:

     "wlanSSID" should be "wlanSsid"
     "ingressVRFID should be "ingressVrfId"
     "egressVRFID should be "egressVrfId"
     "virtualStationUUID" should be "virtualStationUuid".

- which all look wrong.

Else, the IPFIX-doctors rule should be relaxed to allow the existing 
names. Or, it should allow reviewer discretion.

Thanks,
P.


On 14/11/12 22:38, Andrew Feren wrote:
> Hi Paul,
>
> It occurs to me that if well known names keep their case then there is 
> a case for using "AS" in
>
> 16 	bgpSourceAsNumber 	unsigned32 	identifier 	current 	
>
> The autonomous system (AS) number of the source IP address. If AS path 
> information for this Flow is only available as an unordered AS set 
> (and not as an ordered AS sequence), then the value of this 
> Information Element is 0.
>
> 	
> 	
> 	
>
> See [RFC4271 <http://www.iana.org/go/rfc4271>] for a description of 
> BGP-4, and see [RFC1930 <http://www.iana.org/go/rfc1930>] for the 
> definition of the AS number.
>
> 	[RFC5102 <http://www.iana.org/go/rfc5102>]
> 17 	bgpDestinationAsNumber 	unsigned32 	identifier 	current 	
>
> The autonomous system (AS) number of the destination IP address. If AS 
> path information for this Flow is only available as an unordered AS 
> set (and not as an ordered AS sequence), then the value of this 
> Information Element is 0.
>
> 	
> 	
> 	
>
> See [RFC4271 <http://www.iana.org/go/rfc4271>] for a description of 
> BGP-4, and see [RFC1930 <http://www.iana.org/go/rfc1930>] for the 
> definition of the AS number.
>
> 	[RFC5102 <http://www.iana.org/go/rfc5102>]
>
> and
>
> 128 	bgpNextAdjacentAsNumber 	unsigned32 	identifier 	current 	
>
> The autonomous system (AS) number of the first AS in the AS path to 
> the destination IP address. The path is deduced by looking up the 
> destination IP address of the Flow in the BGP routing information 
> base. If AS path information for this Flow is only available as an 
> unordered AS set (and not as an ordered AS sequence), then the value 
> of this Information Element is 0.
>
> 	
> 	
> 	
>
> See [RFC4271 <http://www.iana.org/go/rfc4271>] for a description of 
> BGP-4, and see [RFC1930 <http://www.iana.org/go/rfc1930>] for the 
> definition of the AS number.
>
> 	[RFC5102 <http://www.iana.org/go/rfc5102>]
> 129 	bgpPrevAdjacentAsNumber 	unsigned32 	identifier 	current 	
>
> The autonomous system (AS) number of the last AS in the AS path from 
> the source IP address. The path is deduced by looking up the source IP 
> address of the Flow in the BGP routing information base. If AS path 
> information for this Flow is only available as an unordered AS set 
> (and not as an ordered AS sequence), then the value of this 
> Information Element is 0. In case of BGP asymmetry, the 
> bgpPrevAdjacentAsNumber might not be able to report the correct value.
>
> 	
> 	
> 	
>
> See [RFC4271 <http://www.iana.org/go/rfc4271>] for a description of 
> BGP-4, and see [RFC1930 <http://www.iana.org/go/rfc1930>] for the 
> definition of the AS number.
>
> 	[RFC5102 <http://www.iana.org/go/rfc5102>]
>
>
> The uppercase version is used in the description.
>
> Just thinking,
> -Andrew

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix