[apologize, hit send too quickly, wanted to add:]
public traceroute reports:
10 namehidden1 (ipaddress1) 20 ms 55 ms 36 ms
MPLS Label=698653 Exp=0 TTL=1 S=0
MPLS Label=301856 Exp=0 TTL=1 S=1
11 namehidden2 (ipaddress2) 45 ms 52 ms 50 ms
MPLS Label=323717 Exp=0 TTL=1 S=0
MPLS Label=301856 Exp=0 TTL=2 S=1
But RFC4950 does not prescribe a traceroute + LIB/LFIB manager, which I
think would be analogous.
Thanks,
-- Carlos.
On 12/28/2009 11:48 AM, Carlos Pignataro wrote:
> David,
>
> Please find one additional comment response to your suggestion.
>
> Excerpts from [email protected] on 12/27/2009:
>> I suggest adding a Section 3.3 to discuss use of ifIndex with ICMP and
>> network management tools (e.g., enhanced traceroute plus an SNMP
>> manager)
>
> I still feel that discussing this use would be a strong distraction and
> divertion, and not add substativeness to the spec, ultimatelly causing
> confusion.
>
> My traceroute app at home does IP address-to-name mapping, querying DNS
> and reporting hostnames; ICMP timexceeded was not spec'ed that way, but
> a 'traceroute + hostname manager querier' was useful. It also does:
> -A: Report AS# at each hop (from GRR)
> -O: Report owner at each hop (from DNS)
>
> because it was useful, and reports TOS change, none of which was
> including on the ICMP timeexceeded or unreachable definitions.
>
> A public use of the ifIndex can be to see different interfaces in a
> router, seeing ECMPs with unnumbered, and not mapping them to an
> interface name with an SNMP manager. That is a degree of idenfication,
> to know they are different.
>
> Describing an app like you suggest would implicitly limit, I think. We
> are not spec'ing an application, only the extensions of ICMP, and it
> seems to me that there is enough contextual applicability and motivation
> (without falling into over-framing and under-scoping).
>
> Thanks,
>
> -- Carlos.
>
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
