Re: [rbridge] working group last call for PPP TRILL protocol control protocol [was Re: I-D Action:draft-ietf-pppext-trill-protocol-02.txt]
James Carlson <[email protected]> Wed, 26 Jan 2011 14:47:10 -0500
| Newsgroups | gmane.ietf.pppext |
|---|---|
| Message-ID | <[email protected]> |
William Allen Simpson wrote: > On 1/25/11 2:04 PM, James Carlson wrote: >> I find I'm walking a narrow line. I want to provide a little guidance >> so that it's clear what's expected here, but I also want to avoid either >> just copying hunks of the TRILL and IS-IS documentation or (worse) >> carving out special exceptions. I probably can't please everyone. >> > Probably not. But it's fundamentally wrong to specify a configuration > requirement for two protocols that are both premised on auto-configuration! The other possible solution to avoid manual configuration (as I think I mentioned) is to outlaw the use of TRILL systems that have only PPP links and that also have no built-in (implementation-dependent) means of acquiring a System ID automatically. That's obviously possible, but besides being draconian in nature (how is it my business how you plan to work with network administrators?), it seems to strike a bit too close to the fundamentals of IS-IS. In other words, I think I can point out the potential issue that exists over in IS-IS to readers who might not be aware that (as part of an overall system design, not as part of PPP TRILL itself) they could be stepping in an area that lacks good solutions, but I don't think I should say anything here that's at the level of requirement. It's not my place to repeat IS-IS requirements. I can only do so badly and out-of-sync with the original. ;-} Informative works for me on this issue, but normative doesn't. > I'm sorry that I was off-line yesterday. We've had responses about the > requirements, and that clarifies things immensely. But I'm busy > cleaning up > yesterday's mess today. I promise some text tomorrow.... TIA! Delay is not a problem. I set a standard two-week timer to make sure that folks would follow up. But if there's still discussion going on at that point, I'll continue with it as long as necessary to close it out. (Or until I remember that I have other things to do, I suppose ...) -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ Pppext mailing list [email protected] https://www.ietf.org/mailman/listinfo/pppext