> From: Suresh Krishnan <[email protected]>
> Enhancement request
> ===================
>
> * Maybe it is too much to ask, but it would be great if the mailing list
> references contained an URL to the archive as it is easier to get the
> right mail. I leave it upto your discretion if you want to do this or not.
>
> e.g.
>
> For
> [kyzivat-2]
> Kyzivat, P., "[Sip-implementors] draft-worley-service-
> example-02", sip-implementors mailing list 020426,
> September 2008.
>
>
> add
>
> https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-September/020426.html
This draft is prepared using XML2RFC, and the XML source provides a
link. E.g.,
<reference anchor="kyzivat-2">
<!-- Kyzivat's e-mail #2 -->
<front>
<title>[Sip-implementors] draft-worley-service-example-02</title>
<author initials="P." surname="Kyzivat"><organization/></author>
<date month="September" year="2008"/>
</front>
<seriesInfo name="sip-implementors mailing list" value="020426" />
<format type="TXT"
target="https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-September/020426.html";
/>
</reference>
The text form does not contain the link:
[kyzivat-2]
Kyzivat, P., "[Sip-implementors] draft-worley-service-
example-02", sip-implementors mailing list 020426,
September 2008.
Much stranger, the HTML form does not either:
http://svn.resiprocate.org/rep/ietf-drafts/worley/draft-worley-service-example-14.html
<tr>
<td class="reference">
<b id="kyzivat-2">[kyzivat-2]</b>
</td>
<td class="top"><a>Kyzivat, P.</a>, "<a>[Sip-implementors]
draft-worley-service-example-02</a>", sip-implementors mailing list 020426,
September 2008.</td>
</tr>
On the other hand, the HTML form does give links for the RFCs. and
the XML source for those references is not much different:
http://xml.resource.org/public/rfc/bibxml/reference.RFC.3261.xml
<?xml version='1.0' encoding='UTF-8'?>
<reference anchor='RFC3261'>
<front>
<title>SIP: Session Initiation Protocol</title>
<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'>
<organization /></author>
<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'>
<organization /></author>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<author initials='A.' surname='Johnston' fullname='A. Johnston'>
<organization /></author>
<author initials='J.' surname='Peterson' fullname='J. Peterson'>
<organization /></author>
<author initials='R.' surname='Sparks' fullname='R. Sparks'>
<organization /></author>
<author initials='M.' surname='Handley' fullname='M. Handley'>
<organization /></author>
<author initials='E.' surname='Schooler' fullname='E. Schooler'>
<organization /></author>
<date year='2002' month='June' />
<abstract>
<t>This document describes Session Initiation Protocol (SIP), an
application-layer control (signaling) protocol for creating, modifying, and
terminating sessions with one or more participants. These sessions include
Internet telephone calls, multimedia distribution, and multimedia conferences.
[STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='3261' />
<format type='TXT' octets='647976'
target='http://www.rfc-editor.org/rfc/rfc3261.txt' />
</reference>
The ideal solution would be to update XML2RFC to show the provided
links.
In a more reasonable time frame, probably the best thing to do is have
the RFC Editor add the link to the references.
Dale
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
