Open issues in manyfolks-03
Bis draft dependencies (100rel and Supported)
- Propose: make “manyfolks” depend on bis; delay its publication
-
Late-lastcall comments received this week from Flarion
- Additional wording is perhaps required to resolve case when both endpoints perform bi-directional resource reservation -- which set to use?
- Propose: use the resources described in the COMET message
- Propose: not use any single round-trip solution that would infringe on Flarion IPR
IPR statement
- Draft now contains the mandated text from RFC2026, no longer explicitly mentions both AT&T and 3Com