Re: clTRID element clarification
"Hollenbeck, Scott" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <831693C2CDA2E849A7D7A712B24E257F0D5BCF53@BRN1WNEXMBX01.vcorp.ad.vrsn.com> |
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Theo Kramer > Sent: Thursday, March 08, 2012 11:33 PM > To: [email protected] > Subject: Re: [provreg] clTRID element clarification > > > On 07 Mar 2012, at 11:08 AM, Hollenbeck, Scott wrote: > > > > Given that RFC 5730 is part of Standard 69 there's not much chance of > a near-term amendment, but our process allows us to collect errata. I'm > not convinced that there's anything here to correct, though. Section > 2.5 currently says this: > > > > "MAY be used to uniquely identify the command *to the client*" > > > > Is that not perhaps something that slipped through the cracks? Ie. > should it not read > > "MAY be used to uniquely identify the command from the client" ? No, the intention is for the clTRID to have meaning only in the client's context. That's not a typo about sending commands to clients. Scott _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg