RE: Standardization of change sequence number
John Strassner <[email protected]> Fri, 14 Nov 2003 14:08:39 -0700
| Newsgroups | gmane.ietf.ldup |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3AAF3.7998FCB0 Content-Type: text/plain Apologies for not being able to attend the meeting. For the record, I fully support Chris' comments here. regards, John John C. Strassner Chief Strategy Officer Intelliden Inc. 90 South Cascade Avenue Colorado Springs, CO 80906 USA phone: +1.719.785.0648 fax: +1.719.785.0644 email: [email protected] -----Original Message----- From: Chris Apple [mailto:[email protected]] Sent: Wednesday, November 12, 2003 11:43 AM To: 'Steven Legg'; 'Jim Sermersheim'; [email protected] Subject: RE: Standardization of change sequence number There will more than likely be some slippage from the WG Last Call schedule discussed during the WG Meeting even if the CSN document is published as soon as possible after the I-D Administrator starts processing I-Ds again. Then the information model document would have to be revised before we could start the first grouping of WG Last Call documents mentioned during the WG Meeting. As co-chair I'm OK with pulling the CSN content out as a separate standards-track document if: 1) It is published as an LDUP WG document rather than an individual contribution. I realize that the rationale is that its applicability is broader than LDUP, but I'm skittish about suggestions to increase the dependency of the WG's deliverables on documents not within the control of any WG. This has caused problems before and I don't want to add more of that type of risk. 2) It is submitted to the I-D Editor as soon as possible after they begin accepting new submissions. 3) The new CSN LDUP I-D is included in the WG Last Call grouping of the first document that will reference it, INFOMOD. 4) The INFOMOD Document Editors are able to submit the revised INFOMOD draft within a couple of days of the CSN I-D Action announcement occurring. Keep in mind that if we go that way, we are introducing uncertainty in starting the WG Last Call sequence as discussed during the WG Meeting. This is not really a good thing from a process perspective, but does seem to be the right thing to do from a document management perspective. I'll wait to see some postings from other WG Members (especially need to hear from the INFOMOD Editors) before making a judgment call on this. This means that the first grouping WG Last Call won't happen as planned on the Monday after the IETF. INFOMOD Editors: please respond ASAP. Chris Apple -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steven Legg Sent: Wednesday, November 12, 2003 11:16 AM To: Jim Sermersheim; [email protected] Subject: RE: Standardization of change sequence number Jim, As editor of the URP document, I don't mind changing that document to reference a proposed standard definition for the change sequence number in the form outlined below. To avoid slowing the LDUP publication schedule, the CSN document would have to be produced immediately. Regards, Steven -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Jim Sermersheim Sent: Wednesday, 12 November 2003 7:49 AM To: [email protected] Subject: Standardization of change sequence number I (and I believe others) would like to see the change sequence number syntax be progressed in a standards-track document. Of those initially interested in this, I believe consensus is that it should be defined as a complex type (using ASN.1). A string encoding would be defined (which would likely look just like the one in draft-ietf-ldup-infomod-xx.txt). Then matching rules would be defined in terms of the complext type (not the string encoding). Do the authors of the relevant LDUP I-Ds want to participate in the act of pulling out the current LdapChangeSequenceNumber, and referring to a new I-D, or would they rather just leave it alone (in order to more quickly achieve last call), and let any new I-D progress without being referred to? Jim ------_=_NextPart_001_01C3AAF3.7998FCB0 Content-Type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII"> <meta name=Generator content="Microsoft Word 10 (filtered)"> <title>Message</title> <style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:"\@MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4;} @font-face {font-family:"Microsoft Sans Serif"; panose-1:2 11 6 4 2 2 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} h1 {margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:.3in; text-indent:-.3in; page-break-after:avoid; font-size:16.0pt; font-family:Arial; font-weight:bold;} h3 {margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:.5in; margin-bottom:.0001pt; text-indent:-.5in; page-break-after:avoid; font-size:13.0pt; font-family:Arial; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;} p {margin-right:0in; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman";} p.Numbered, li.Numbered, div.Numbered {margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.8in; margin-bottom:.0001pt; text-indent:-.25in; line-height:200%; font-size:10.0pt; font-family:"Times New Roman";} p.Bulletted, li.Bulletted, div.Bulletted {margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:1.5in; margin-bottom:.0001pt; text-indent:-.25in; line-height:200%; font-size:10.0pt; font-family:"Times New Roman";} p.Indented, li.Indented, div.Indented {margin-top:0in; margin-right:0in; margin-bottom:6.0pt; margin-left:.25in; text-autospace:none; font-size:12.0pt; font-family:"Times New Roman";} p.TableGrid8-mine, li.TableGrid8-mine, div.TableGrid8-mine {margin-top:3.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; text-indent:-.7pt; font-size:10.0pt; font-family:"Times New Roman";} p.TableGrid8-numbered, li.TableGrid8-numbered, div.TableGrid8-numbered {margin-top:3.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:35.3pt; text-indent:-.25in; font-size:10.0pt; font-family:"Times New Roman";} p.BodyTextKeep-Table, li.BodyTextKeep-Table, div.BodyTextKeep-Table {margin-top:2.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:.1in; text-align:justify; text-justify:inter-ideograph; font-size:11.0pt; font-family:Arial; letter-spacing:-.25pt; layout-grid-mode:line; font-weight:bold;} p.Bullist, li.Bullist, div.Bullist {margin-top:2.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:1.0in; text-indent:-.25in; font-size:11.0pt; font-family:Arial; letter-spacing:-.25pt;} p.BodyTextKeep-10pt, li.BodyTextKeep-10pt, div.BodyTextKeep-10pt {margin-top:2.0pt; margin-right:0in; margin-bottom:2.0pt; margin-left:0in; text-align:justify; text-justify:inter-ideograph; font-size:10.0pt; font-family:Arial; letter-spacing:-.25pt;} span.EmailStyle25 {font-family:Arial; color:navy;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {page:Section1;} /* List Definitions */ ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style> <style> p.MsoNormal {margin-left:3.0pt;} </style> </head> <body lang=EN-US link=blue vlink=purple style='margin-left:3.0pt;margin-top: 3.0pt;margin-right:3.0pt;margin-bottom:.75pt'> <div class=Section1> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Apologies for not being able to attend the meeting. For the record, I fully support Chris' comments here.</span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p> <div> <p><font size=3 color=navy face="Times New Roman"><span style='font-size:12.0pt; color:navy'>regards,<br> John </span></font></p> <p><font size=3 color=navy face="Times New Roman"><span style='font-size:12.0pt; color:navy'>John C. Strassner <br> Chief Strategy Officer <br> Intelliden Inc. <br> 90 South Cascade Avenue <br> Colorado Springs, CO 80906 USA <br> phone: +1.719.785.0648 <br> fax: +1.719.785.0644 <br> email: [email protected] </span></font></p> </div> <div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'> <p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt; font-family:Tahoma'>-----Original Message-----<br> <b><span style='font-weight:bold'>From:</span></b> </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Chris Apple</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> [mailto:[email protected]] <br> <b><span style='font-weight:bold'>Sent:</span></b> Wednesday, November 12, 2003 11:43 AM<br> <b><span style='font-weight:bold'>To:</span></b> 'Steven Legg'; 'Jim Sermersheim'; [email protected]<br> <b><span style='font-weight:bold'>Subject:</span></b> RE: Standardization of change sequence number</span></font></p> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'> </span></font></p> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>There will more than likely be some slippage from the WG Last Call schedule discussed during</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>the WG Meeting even if the CSN document is published as soon as possible after the I-D Administrator</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>starts processing I-Ds again.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>Then the information model document would have to be revised before we could start the first grouping</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>of WG Last Call documents mentioned during the WG Meeting.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>As co-chair I'm OK with pulling the CSN content out as a separate standards-track document if:</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>1) It is published as an LDUP WG document rather than an individual contribution. I realize that the</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>rationale is that its applicability is broader than LDUP, but I'm skittish about suggestions</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>to increase the dependency of the WG's deliverables on documents not within the control of</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>any WG. This has caused problems before and I don't want to add more of that type of risk.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>2) It is submitted to the I-D Editor as soon as possible after they begin accepting new</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>submissions.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>3) The new CSN LDUP I-D is included in the WG Last Call grouping of the first document</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>that will reference it, INFOMOD.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>4) The INFOMOD Document Editors are able to submit the revised INFOMOD draft within a</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>couple of days of the CSN I-D Action announcement occurring.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>Keep in mind that if we go that way, we are introducing uncertainty in starting the WG Last Call</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>sequence as discussed during the WG Meeting. This is not really a good thing from a process</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>perspective, but does seem to be the right thing to do from a document management perspective.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>I'll wait to see some postings from other WG Members (especially need to hear from the INFOMOD<br> Editors) before making a judgment call on this. This means that the first grouping WG Last Call won't</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>happen as planned on the Monday after the IETF.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>INFOMOD Editors: please respond ASAP.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>Chris Apple </span></font></p> </div> <blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'> <p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br> <b><span style='font-weight:bold'>From:</span></b> [email protected] [mailto:[email protected]] <b><span style='font-weight:bold'>On Behalf Of </span></b>Steven Legg<br> <b><span style='font-weight:bold'>Sent:</span></b> Wednesday, November 12, 2003 11:16 AM<br> <b><span style='font-weight:bold'>To:</span></b> Jim Sermersheim; [email protected]<br> <b><span style='font-weight:bold'>Subject:</span></b> RE: Standardization of change sequence number</span></font></p> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>Jim,</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>As editor of the URP document, I don't mind changing that document to reference a</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>proposed standard definition for the change sequence number in the form outlined</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>below. To avoid slowing the LDUP publication schedule, the CSN document would</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>have to be produced immediately.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>Regards,</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>Steven</span></font></p> </div> <blockquote style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt; margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'> <p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br> <b><span style='font-weight:bold'>From:</span></b> [email protected] [mailto:[email protected]]<b><span style='font-weight:bold'>On Behalf Of </span></b>Jim Sermersheim<br> <b><span style='font-weight:bold'>Sent:</span></b> Wednesday, 12 November 2003 7:49 AM<br> <b><span style='font-weight:bold'>To:</span></b> [email protected]<br> <b><span style='font-weight:bold'>Subject:</span></b> Standardization of change sequence number</span></font></p> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>I (and I believe others) would like to see the change sequence number syntax be progressed in a standards-track document. Of those initially interested in this, I believe consensus is that it should be defined as a complex type (using ASN.1). A string encoding would be defined (which would likely look just like the one in draft-ietf-ldup-infomod-xx.txt). Then matching rules would be defined in terms of the complext type (not the string encoding).</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>Do the authors of the relevant LDUP I-Ds want to participate in the act of pulling out the current LdapChangeSequenceNumber, and referring to a new I-D,</span></font><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial; color:blue'> </span></font><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>or would they rather just leave it alone (in order to more quickly achieve last call), and let any new I-D progress without being referred to?</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Microsoft Sans Serif"><span style='font-size:10.0pt;font-family:"Microsoft Sans Serif"'>Jim</span></font></p> </div> </blockquote> </blockquote> </div> </div> </body> </html> ------_=_NextPart_001_01C3AAF3.7998FCB0--