headers
Lou Berger | 3 Nov 2011 15:13
Favicon

possible bug in rfcmarkup

Henrik,
	Not sure what's happening, perhaps use of some bad source xml, but
http://tools.ietf.org/html/rfc6370 shows an HTML title that is unrelated
to the actual document title.

Shown:
    <title>RFC 6370 - (PWE3) architectures to support the capabilities
and functionalities of a packet transport network as defined by the
ITU-T.</title>

Actual:
	MPLS Transport Profile (MPLS-TP) Identifiers

Thought you'd want to know.

Lou

Note looks like the tools site is running rev 1.96.
Permalink | Reply | 3 comments |
headers
Henrik Levkowetz | 3 Nov 2011 16:08

Re: possible bug in rfcmarkup

Hi Lou,

On 2011-11-03 15:13 Lou Berger said:
> Henrik,
> 	Not sure what's happening, perhaps use of some bad source xml, but
> http://tools.ietf.org/html/rfc6370 shows an HTML title that is unrelated
> to the actual document title.
> 
> Shown:
>     <title>RFC 6370 - (PWE3) architectures to support the capabilities
> and functionalities of a packet transport network as defined by the
> ITU-T.</title>
> 
> Actual:
> 	MPLS Transport Profile (MPLS-TP) Identifiers
> 
> Thought you'd want to know.

Yes, thank you.  The title extraction had clearly failed; the string shown
came from the end of the Abstract.

I've removed the converted file, which causes a new conversion; it now shows
with correct title (and is generated using rev 1.98).

It would have been re-generated in abouth a month's time, which would have
brought it up to 1.98 anyway, but it's better to fix flaws at once.

Thanks for the alert!

> Lou
(Continue reading)

Permalink | Reply | 2 comments |
headers
Lou Berger | 3 Nov 2011 16:33
Favicon

Re: possible bug in rfcmarkup

Sounds like you're ahead of this one.

Much thanks,
Lou

PS really appreciate all the great tools!

On 11/3/2011 11:08 AM, Henrik Levkowetz wrote:
> Hi Lou,
> 
> On 2011-11-03 15:13 Lou Berger said:
>> Henrik,
>> 	Not sure what's happening, perhaps use of some bad source xml, but
>> http://tools.ietf.org/html/rfc6370 shows an HTML title that is unrelated
>> to the actual document title.
>>
>> Shown:
>>     <title>RFC 6370 - (PWE3) architectures to support the capabilities
>> and functionalities of a packet transport network as defined by the
>> ITU-T.</title>
>>
>> Actual:
>> 	MPLS Transport Profile (MPLS-TP) Identifiers
>>
>> Thought you'd want to know.
> 
> Yes, thank you.  The title extraction had clearly failed; the string shown
> came from the end of the Abstract.
> 
> I've removed the converted file, which causes a new conversion; it now shows
(Continue reading)

Permalink | Reply | 1 comment |
headers
Henrik Levkowetz | 3 Nov 2011 19:03

Re: possible bug in rfcmarkup


On 2011-11-03 16:33 Lou Berger said the following:
> PS really appreciate all the great tools!

Thank you!

Best regards,

	Henrik
Permalink | Reply | 0 comments |
headers
Robert Sparks | 8 Nov 2011 22:37
Favicon

Re: Agenda Development RFP SOW for Community Input

Tools developers -

I've provided a long feedback message at
<http://www.ietf.org/mail-archive/web/ietf-sow/current/msg00001.html>

If you haven't looked at the document yet, please do so. I think you'll find things you want to comment on.

RjS

On Nov 7, 2011, at 1:48 PM, IETF Administrative Director wrote:

> REMINDER
> 
> The IETF Administrative Oversight Committee (IAOC) plans to issue a Request for Proposal (RFP) in
November for a
> vendor to develop the IETF Meeting Agenda Scheduling Tool.  To that end the IAOC invites community
comments on the 
> draft Statement of Work (SOW) that is located at <http://iaoc.ietf.org/rfpsrfis.html>.
> 
> The community comment period ends 14 November 2011. The IAOC will consider all comments it receives
during that period.
> 
> The SOW describes the requirements for a Secretariat Meeting Agenda creation tool. The agenda tool will
handle all meeting 
> scheduling, as well as management of any/all space in use during an IETF meetings. This includes working
sessions, leadership 
> meetings, tutorials, BoFs, office hours, registration, breaks, and more.  Agenda scheduling is
currently a manual process.  
> The Draft SOW includes some questions for which feedback and suggestions are desired.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Henrik Levkowetz | 9 Nov 2011 15:40

Re: [TOOLS-DEVELOPMENT] Charter page list of dafts

Hi,

I've looked at these:

  http://datatracker.ietf.org/wg/mpls/
  http://tools.ietf.org/wg/mpls/

without finding the phenomenon you mention.  Could you clue me in on
where (which URL) you're seeing this?

	Henrik

On 2011-11-08 23:02 Adrian Farrel said:
> Hi,
> 
> I suspect this problem cut in at a specific recent date.
> 
> The recently published RFCs show in a new "Old Drafts" section rather than as
> published RFCs. 
> 
> I'm guessing some link from I-D to RFC (or vice versa) is missing.
> 
> Adrian
> 
>> -----Original Message-----
>> From: Loa Andersson [mailto:loa <at> pi.nu]
>> Sent: 08 November 2011 21:11
>> To: IETF-IESG via RT; Adrian Farrel; mpls-chairs <at> tools.ietf.org; Martin
> Vigoureux
>> Subject: What is this???
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Nottingham | 14 Nov 2011 16:53
Favicon
Gravatar

draft author updates

Hi,

I just send an e-mail to draft-gregorio-uritemplate <at> tools.ietf.org, and got a bounce back from
marc.hadly <at> oracle.com (see below).

That address *used* to be an author of the draft, but Marc has since updated his address (to
mhadley <at> mitre.org, as of draft 07, published on September 26). 

So, it appears that whatever tool scrapes drafts for addresses isn't keeping up-to-date with author
changes in drafts.

Cheers,

> From: Mail Delivery Subsystem <MAILER-DAEMON <at> acsmt358.oracle.com>
> Subject: Returned mail: see transcript for details
> Date: 14 November 2011 9:41:07 AM CST
> To: <mnot <at> mnot.net>
> 
> The original message was received at Mon, 14 Nov 2011 09:41:07 -0600
> from abhmt106.oracle.com [141.146.116.58]
> 
>  ----- The following addresses had permanent fatal errors -----
> <marc.hadley <at> oracle.com>
>   (reason: 550 5.1.1 Recipient unknown)
> 
>  ----- Transcript of session follows -----
> ... while talking to [141.146.40.155]:
>>>> RCPT To:<marc.hadley <at> oracle.com> NOTIFY=FAILURE
> <<< 550 5.1.1 Recipient unknown
> 550 5.1.1 <marc.hadley <at> oracle.com>... User unknown
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Saint-Andre | 15 Nov 2011 03:56
Favicon

etherpad for BoFs? (was: Fwd: [weirds] Updated agenda & other info for the BoF)

Henrik, do we have etherpad support for BoFs? Notice what Andrew says:

"BoFs really need complete minutes.  Does anyone want to volunteer in
advance to help by taking the minutes?"

-------- Original Message --------
Subject: [weirds] Updated agenda & other info for the BoF
Date: Mon, 14 Nov 2011 21:52:41 -0500
From: Andrew Sullivan <ajs <at> anvilwalrusden.com>
To: weirds <at> ietf.org

Dear colleagues,

I uploaded a new agenda to the meeting materials (and included it
below).

I have been in touch with the Meetecho people, and we will apparently
have at least some support from them for remote participants.  It
won't be two-way voice, though, so you'll need a jabber client at least.

BoFs really need complete minutes.  Does anyone want to volunteer in
advance to help by taking the minutes?

Best,

A

Agenda for WEIRDS BoF, IETF 82
  2011-11-15
(Continue reading)

Permalink | Reply | 1 comment |
headers
Peter Saint-Andre | 15 Nov 2011 05:05
Favicon

http://tools.ietf.org/agenda/82/

Is the data for the tools-style agenda available for use by other 
applications? Robert Sparks and I were both independently thinking that 
it would be cool to autopopulate the jabber chatroom subjects with links 
to the agenda, materials, audio streaming URLs, etc.

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Permalink | Reply | 5 comments |
headers
Adam Roach | 15 Nov 2011 05:21
Favicon

http://tools.ietf.org/agenda/82/

On 11/15/11 12:05 PM, Peter Saint-Andre wrote:
> Is the data for the tools-style agenda available for use by other 
> applications? Robert Sparks and I were both independently thinking 
> that it would be cool to autopopulate the jabber chatroom subjects 
> with links to the agenda, materials, audio streaming URLs, etc.
>
> Peter
>
See:

https://datatracker.ietf.org/meeting/81/agenda.csv

Or, for the "current" meeting (whatever that happens to be):

https://datatracker.ietf.org/meeting/agenda.csv

/a
Permalink | Reply | 1 comment |

Gmane