The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] I-D updates posted
Title: RE: I-D updates posted I had one question about the MIBs in general, and that is the handling of MTU. I can get an I/F MTU and presumably could trace an LSP box to box if I thought I was having a problem, but cannot determine/set a path MTU easily as there is no way to know what it is at the LSP ingress. As this can currently be known at an LSP ingress if RSVP is used, and extensions to LDP are progressing (Ben Black's draft), and I need a means of knowing it at the ingress for provisioned LSPs, would it not make sense to either add an entry to the FTN MIB (if we considered knowing the ingress value sufficient), or to the XC-entry in the LSR MIB (if we wanted the ability to examine how path MTU propagated). As a separate issue, I had asked about TTL handling on this list (vis-a-vis the MIB, uniform vs. pipe models), and one interpretation of the lack of interest is this did not seem to be an issue worth addressing. I'm only bringing it up now as if MTU leads to a change, should we not get everything over with at once. merry christmas
> -----Original Message-----
|
|