Re: Load Selector Parameter Tag conflicts with SUA
"Pascal Bouveron (Netbricks)" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <00c301c6911e$d067ae60$1500a8c0@pbn> |
Brian, >> I was reviewing Brian's "draft-bidulock-sigtran-LOADSEL-04.txt" document, >> and discovered that the "Load Selector" Parameter Tag, defined to 0x0018, >> conflicts with SUA "Local RK Id". > > Well, its been that way for about 3 1/2 years now. Please see the notes > on > the bottom of page 37. Do you mean that there's no chance that the ids defined in LOADSEL would shift to clear the conflict ? >> It would have been a good idea to define the few SUA's Class-00 Parameter >> Tags within the Parameter Class-01, reserved for SUA... but that's far >> too >> late now. > > I pushed for quite the reverse. There are common parameters with common > procedures that are not in Class-00 and IMO should be. I see your point: M3UA defines the same Reg-Result, Dereg-Result, Reg-Status, Dereg-Status and Local-RK-id Parameters as SUA, but in the M3UA-Class, for historical reasons. Defining them in Class-00 for SUA is a way to push towards using these Parameters rather than defining new ones for any new UA that would use similar procedures. I totally agree with that. >> Can i suggest that any new UA-specific Parameters SHOULD be defined >> within >> their respective UA-Class rather than eating-up Class-00 ? > > I disagree: common parameters with common procedures should be in > Class-00. Indeed. Pascal Bouveron / Netbricks