Re: Storage Maintenance (storm) BOF reminder & requests
"Felix Marti" <[email protected]> Wed, 25 Mar 2009 23:45:30 -0700
| Newsgroups | gmane.ietf.rddp |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============1815431043== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9ADDE.D4715774" This is a multi-part message in MIME format. ------_=_NextPart_001_01C9ADDE.D4715774 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 The same applies to me (unable to attend but interested in contributing). =20 Regards, felix =20 =20 From: [email protected] [mailto:[email protected]] On Behalf Of Fredy Neeser Sent: Wednesday, March 25, 2009 9:58 AM To: [email protected]; [email protected]; [email protected] Subject: [Junk released by Allow List] Re: [rddp] Storage Maintenance (storm) BOF reminder & requests =20 David, All,=20 While I am unfortunately unable to attend the BOF this week,=20 I am interested in contributing to=20 - RDDP MPA: Small startup update for MPI application support.=20 preferably through your Option (C), the "virtual" working group.=20 ***=20 The interoperability of MPA-based RDMA connection management=20 is still a concern - for MPI, NFS/RDMA and other apps.=20 Because MPA has the (theoretically well-known) requirement that=20 the first FPDU be sent from the RDMA initiator side, whereas=20 InfiniBand has no such requirement, RDMA application writers=20 tend to be caught by surprise when an application that violates=20 this requirement works on InfiniBand but doesn't on iWARP.=20 The so-called "peer-to-peer connection management" that was=20 discussed in various flavours on the Linux OpenFabrics=20 reflector for making RDMA connection management more uniform=20 (among transports) and easier to use should be studied in detail.=20 The solution should be flexible enough to allow an optimized=20 application to avoid unnecessary additional round-trip delays.=20 In addition, MPA's "delayed startup sequence" (a.k.a. delayed=20 transition to RDMA mode or socket conversion) may need further=20 clarification. For instance, the negotiation of connection=20 parameters such as IRD and ORD should be clarified for cases=20 where Private Data is not used in MPA Request/Reply.=20 (IRD adjustment in RTS state is not mandatory according=20 to the RDMAC Verbs, p. 74).=20 ***=20 Besides contributing to draft text, I am interested in=20 early testing of the MPA startup update through a=20 software implementation.=20 Thanks,=20 - Fredy=20 -----------------------------------=20 Fredy Neeser, Research Staff Member=20 IBM Zurich Research Laboratory=20 Saeumerstrasse 4=20 CH-8803 Rueschlikon, Switzerland e-Mail: [email protected] Phone : +41 (0)44 724 8487=20 -----------------------------------=20 From:=20 [email protected]=20 To:=20 <[email protected]>, <[email protected]>=20 Cc:=20 [email protected], [email protected]=20 Date:=20 12.03.2009 00:29=20 Subject:=20 [rddp] Storage Maintenance (storm) BOF reminder & requests=20 Sent by:=20 [email protected] =20 ________________________________ This is a reminder that the Storage Maintenance BOF will be held in about 2 weeks at the IETF meetings in San Francisco. Please plan to attend if you're interested: THURSDAY, March 26, 2009 Continental 1&2 TSV storm Storage Maintenance BOF The BOF description is at: http://www.ietf.org/mail-archive/web/ips/current/msg02669.html <http://www.ietf.org/mail-archive/web/ips/current/msg02669.html>=20 The initial agenda is here: http://www.ietf.org/mail-archive/web/ips/current/msg02670.html <http://www.ietf.org/mail-archive/web/ips/current/msg02670.html>=20 I'm going to go upload that initial agenda as the BOF agenda, and it can be bashed at the meeting. The primary purpose of this BOF is to answer two questions: (1) What storage maintenance work (IP Storage, Remote Direct Data Placement) should be done? (2) Should an IETF Working Group be formed to undertake that work? Everyone gets to weigh in on these decisions, even those who can't attend the BOF meeting. Anyone who thinks that there is work that should be done, and who cannot come to the BOF meeting should say so on the IPS or RDDP mailing lists (and it'd be a good idea for those who can come to do this). As part of the email, please indicate how you're interested in helping (author or co-author of specific drafts, promise to review and comment on specific drafts). Here's a summary of the initial draft list of work items: - iSCSI: Combine RFCs into one document, removing unused features. - iSCSI: Interoperability report on what has been implemented and interoperates in support of Draft Standard status for iSCSI. - iSCSI: Add backwards-compatible features to support SAM-4. - iFCP: The Address Translation mode of iFCP needs to be deprecated. - RDDP MPA: Small startup update for MPI application support. - iSER: A few minor updates based on InfiniBand experience. Additional work (e.g., updated/improved iSNS for iSCSI, MIB changes, updated ipsec security profile [i.e., IKEv2-based]) is possible if there's interest. There are (at least) four possible outcomes: (A) None of this work needs to be done. (B) There are some small work items that make sense. Individual drafts with a draft shepherd (i.e., David Black) will suffice. (C) A working group is needed to undertake more complex work items and reach consensus on design issues. The WG can be "virtual" and operate mostly via the mailing list until/unless controversial/contentious issues arise. (D) There is a lot of complex work that is needed, and a WG that will plan to meet at every IETF meeting should be formed. Please note that the IETF "rough consensus" process requires a working group in practice to be effective. This makes outcome (C) look attractive to me, as: - I'm coming under increasing pressure to limit travel, and the next two IETF meetings after San Francisco are not in the US. - I'd rather have the "rough consensus" process available and not need it than need it and not have it available. Setting an example for how to express interest ... --------------- I think that the iSCSI single RFC and interoperability report are good ideas, but I want to see a bunch of people expressing interest in these, as significant effort is involved. It might make sense to do the single iSCSI RFC but put off the interoperability report (the resulting RFC would remain at Proposed Standard rather than going to Draft Standard), as I'm not hearing about major iSCSI interoperability issues. I think the latter four items (SAM-4 for iSCSI, deprecate iFCP address translation, MPI fix to MPA and iSER fixes) should all be done. I plan to author the iFCP address translation deprecation draft, and review all other drafts. I think that a virtual WG should be formed that plans to do its work primarily via the mailing list. I believe the SAM-4 work by itself is complex enough to need a working group - I would expect design issues to turn up at least there and in determining whether to remove certain iSCSI features, but I'm cautiously optimistic that the mailing list is sufficient to work these issues out (and concerned that travel restrictions are likely to force use of the mailing list). ----------------- Ok, who wants to go next? Thanks, --David ---------------------------------------------------- David L. Black, Distinguished Engineer EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 [email protected] Mobile: +1 (978) 394-7754 ---------------------------------------------------- _______________________________________________ rddp mailing list [email protected] https://www.ietf.org/mailman/listinfo/rddp <https://www.ietf.org/mailman/listinfo/rddp>=20 ------_=_NextPart_001_01C9ADDE.D4715774 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" = xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" = xmlns:a=3D"urn:schemas-microsoft-com:office:access" = xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" = xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" = xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" = xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" = xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" = xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" = xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" = xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" = xmlns:html=3D"http://www.w3.org/TR/REC-html40" = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" = xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" = xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" = xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" = xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" = xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" = xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" = xmlns:udc=3D"http://schemas.microsoft.com/data/udc" = xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" = xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"= xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" = xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" = xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" = xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" = xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" = xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" = xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" = xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" = xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" = xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig= nature" = xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006= " xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi= ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" = xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"= = xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag= es" = xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/= " = xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub= lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" = xmlns:st=3D"" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)"> <!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} tt {mso-style-priority:99; font-family:"Courier New";} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'>All,<o:p></o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'>The same applies to me (unable to attend but interested = in contributing).<o:p></o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'>Regards,<o:p></o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'>felix<o:p></o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in = 0in 4.0pt'> <div> <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt = 0in 0in 0in'> <p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> [email protected] [mailto:[email protected]] <b>On Behalf Of = </b>Fredy Neeser<br> <b>Sent:</b> Wednesday, March 25, 2009 9:58 AM<br> <b>To:</b> [email protected]; [email protected]; [email protected]<br> <b>Subject:</b> [Junk released by Allow List] Re: [rddp] Storage = Maintenance (storm) BOF reminder & requests<o:p></o:p></span></p> </div> </div> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <tt><span style=3D'font-size:10.0pt'>David, All,</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>While I am unfortunately unable to = attend the BOF this week,</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>I am interested in contributing = to</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>- RDDP MPA: Small startup update = for MPI application support.</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>preferably through your Option (C), = the "virtual" working group.</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'> = = ***</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>The interoperability of MPA-based = RDMA connection management</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>is still a concern - for MPI, = NFS/RDMA and other apps.</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>Because MPA has the (theoretically well-known) requirement that</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>the first FPDU be sent from the = RDMA initiator side, whereas</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>InfiniBand has no such requirement, = RDMA application writers</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>tend to be caught by surprise when = an application that violates</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>this requirement works on = InfiniBand but doesn't on iWARP.</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>The so-called "peer-to-peer = connection management" that was</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>discussed in various flavours on = the Linux OpenFabrics</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>reflector for making RDMA = connection management more uniform</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>(among transports) and easier to = use should be studied in detail.</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>The solution should be flexible = enough to allow an optimized</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>application to avoid unnecessary = additional round-trip delays.</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>In addition, MPA's "delayed = startup sequence" (a.k.a. delayed</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>transition to RDMA mode or socket conversion) may need further</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>clarification. For instance, the = negotiation of connection</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>parameters such as IRD and ORD = should be clarified for cases</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>where Private Data is not used in = MPA Request/Reply.</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>(IRD adjustment in RTS state is not mandatory according</span></tt> <br> <tt><span style=3D'font-size:10.0pt'> to the RDMAC Verbs, p. = 74).</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'> = = ***</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>Besides contributing to draft text, = I am interested in</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>early testing of the MPA startup = update through a</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>software = implementation.</span></tt> <br> <br> <tt><span style=3D'font-size:10.0pt'>Thanks,</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>- Fredy</span></tt> <br> <br> <tt><span = style=3D'font-size:10.0pt'>-----------------------------------</span></tt= > <br> <tt><span style=3D'font-size:10.0pt'>Fredy Neeser, Research Staff = Member</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>IBM Zurich Research = Laboratory</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>Saeumerstrasse 4</span></tt> <br> <tt><span style=3D'font-size:10.0pt'>CH-8803 Rueschlikon, = Switzerland</span></tt><span style=3D'font-size:10.0pt;font-family:"Courier New"'><br> <tt>e-Mail: [email protected]</tt><br> <tt>Phone : +41 (0)44 724 8487</tt></span> <br> <tt><span = style=3D'font-size:10.0pt'>-----------------------------------</span></tt= > <br> <br> <br> <o:p></o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"; color:#5F5F5F'>From:</span> <o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Black_David@em= c.com</span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"; color:#5F5F5F'>To:</span> <o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'><[email protected]= rg>, <[email protected]></span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"; color:#5F5F5F'>Cc:</span> <o:p></o:p></p> </td> <td style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>[email protected],= [email protected]</span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"; color:#5F5F5F'>Date:</span> <o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>12.03.2009 00:29</span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"; color:#5F5F5F'>Subject:</span> <o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>[rddp] Storage Maintenance (storm) BOF reminder & requests</span> = <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"; color:#5F5F5F'>Sent by:</span> <o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span = style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>rddp-bounces@i= etf.org</span><o:p></o:p></p> </td> </tr> </table> <p class=3DMsoNormal><o:p> </o:p></p> <div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'> <hr size=3D2 width=3D"100%" noshade style=3D'color:gray' align=3Dcenter> </div> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <br> <br> <tt><span style=3D'font-size:10.0pt'>This is a reminder that the Storage Maintenance BOF will</span></tt><span = style=3D'font-size:10.0pt;font-family:"Courier New"'><br> <tt>be held in about 2 weeks at the IETF meetings in San = Francisco.</tt><br> <tt>Please plan to attend if you're interested:</tt><br> <br> <tt>THURSDAY, March 26, 2009</tt><br> <tt>Continental 1&2 = TSV = storm = Storage Maintenance BOF</tt><br> <br> <tt>The BOF description is at:</tt><br> </span><a = href=3D"http://www.ietf.org/mail-archive/web/ips/current/msg02669.html"><= tt><span style=3D'font-size:10.0pt'>http://www.ietf.org/mail-archive/web/ips/curre= nt/msg02669.html</span></tt></a><span style=3D'font-size:10.0pt;font-family:"Courier New"'><br> <br> <tt>The initial agenda is here:</tt><br> </span><a = href=3D"http://www.ietf.org/mail-archive/web/ips/current/msg02670.html"><= tt><span style=3D'font-size:10.0pt'>http://www.ietf.org/mail-archive/web/ips/curre= nt/msg02670.html</span></tt></a><span style=3D'font-size:10.0pt;font-family:"Courier New"'><br> <br> <tt>I'm going to go upload that initial agenda as the BOF = agenda,</tt><br> <tt>and it can be bashed at the meeting.</tt><br> <br> <tt>The primary purpose of this BOF is to answer two questions:</tt><br> <tt>(1) What storage maintenance work (IP Storage, Remote = Direct</tt><br> <tt> Data = Placement) should be done?</tt><br> <tt>(2) Should an IETF Working Group be formed to undertake = that</tt><br> <tt> = work?</tt><br> <br> <tt>Everyone gets to weigh in on these decisions, even those = who</tt><br> <tt>can't attend the BOF meeting. Anyone who thinks that there = is</tt><br> <tt>work that should be done, and who cannot come to the BOF = meeting</tt><br> <tt>should say so on the IPS or RDDP mailing lists (and it'd be = a</tt><br> <tt>good idea for those who can come to do this). As part of = the</tt><br> <tt>email, please indicate how you're interested in helping = (author</tt><br> <tt>or co-author of specific drafts, promise to review and = comment</tt><br> <tt>on specific drafts).</tt><br> <br> <tt>Here's a summary of the initial draft list of work items:</tt><br> <tt>- iSCSI: Combine RFCs into one document, removing unused = features.</tt><br> <tt>- iSCSI: Interoperability report on what has been implemented = and</tt><br> <tt> = interoperates in support of Draft Standard status for iSCSI.</tt><br> <tt>- iSCSI: Add backwards-compatible features to support = SAM-4.</tt><br> <tt>- iFCP: The Address Translation mode of iFCP needs to be = deprecated.</tt><br> <tt>- RDDP MPA: Small startup update for MPI application = support.</tt><br> <tt>- iSER: A few minor updates based on InfiniBand experience.</tt><br> <br> <tt>Additional work (e.g., updated/improved iSNS for iSCSI, MIB = changes,</tt><br> <tt>updated ipsec security profile [i.e., IKEv2-based]) is possible = if</tt><br> <tt>there's interest.</tt><br> <br> <tt>There are (at least) four possible outcomes:</tt><br> <tt>(A) None of this work needs to be done.</tt><br> <tt>(B) There are some small work items that make sense. = Individual</tt><br> <tt> drafts with = a draft shepherd (i.e., David Black) will</tt><br> <tt> = suffice.</tt><br> <tt>(C) A working group is needed to undertake more complex = work</tt><br> <tt> items and = reach consensus on design issues. The WG can</tt><br> <tt> be "virtual" and operate mostly via the mailing list</tt><br> <tt> until/unless controversial/contentious issues arise.</tt><br> <tt>(D) There is a lot of complex work that is needed, and a WG</tt><br> <tt> that will = plan to meet at every IETF meeting should be</tt><br> <tt> = formed.</tt><br> <br> <tt>Please note that the IETF "rough consensus" process = requires a</tt><br> <tt>working group in practice to be effective. This makes = outcome</tt><br> <tt>(C) look attractive to me, as:</tt><br> <tt>- I'm coming under increasing pressure to limit travel, and</tt><br> <tt> the next two = IETF meetings after San Francisco are not</tt><br> <tt> in the = US.</tt><br> <tt>- I'd rather have the "rough consensus" process available = and</tt><br> <tt> not need it = than need it and not have it available.</tt><br> <br> <tt>Setting an example for how to express interest ...</tt><br> <br> <tt>---------------</tt><br> <tt>I think that the iSCSI single RFC and interoperability report = are</tt><br> <tt>good ideas, but I want to see a bunch of people expressing = interest</tt><br> <tt>in these, as significant effort is involved. It might make = sense</tt><br> <tt>to do the single iSCSI RFC but put off the interoperability = report</tt><br> <tt>(the resulting RFC would remain at Proposed Standard rather = than</tt><br> <tt>going to Draft Standard), as I'm not hearing about major = iSCSI</tt><br> <tt>interoperability issues.</tt><br> <br> <tt>I think the latter four items (SAM-4 for iSCSI, deprecate = iFCP</tt><br> <tt>address translation, MPI fix to MPA and iSER fixes) should = all</tt><br> <tt>be done.</tt><br> <br> <tt>I plan to author the iFCP address translation deprecation = draft,</tt><br> <tt>and review all other drafts.</tt><br> <br> <tt>I think that a virtual WG should be formed that plans to do = its</tt><br> <tt>work primarily via the mailing list. I believe the SAM-4 = work</tt><br> <tt>by itself is complex enough to need a working group - I = would</tt><br> <tt>expect design issues to turn up at least there and in = determining</tt><br> <tt>whether to remove certain iSCSI features, but I'm = cautiously</tt><br> <tt>optimistic that the mailing list is sufficient to work = these</tt><br> <tt>issues out (and concerned that travel restrictions are likely = to</tt><br> <tt>force use of the mailing list).</tt><br> <br> <tt>-----------------</tt><br> <br> <tt>Ok, who wants to go next?</tt><br> <br> <tt>Thanks,</tt><br> <tt>--David</tt><br> <tt>----------------------------------------------------</tt><br> <tt>David L. Black, Distinguished Engineer</tt><br> <tt>EMC Corporation, 176 South St., Hopkinton, MA 01748</tt><br> <tt>+1 (508) 293-7953 FAX: +1 = (508) 293-7786</tt><br> <tt>[email protected] Mobile: +1 (978) = 394-7754</tt><br> <tt>----------------------------------------------------</tt><br> <tt>_______________________________________________</tt><br> <tt>rddp mailing list</tt><br> <tt>[email protected]</tt><br> </span><a href=3D"https://www.ietf.org/mailman/listinfo/rddp"><tt><span style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/rddp</sp= an></tt></a><span style=3D'font-size:10.0pt;font-family:"Courier New"'><br> <br> </span><o:p></o:p></p> </div> </div> </body> </html> ------_=_NextPart_001_01C9ADDE.D4715774-- --===============1815431043== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rddp mailing list [email protected] https://www.ietf.org/mailman/listinfo/rddp --===============1815431043==--