Stephen Farrell | 2 Dec 14:43 2014
Picon
Picon

Re: Connectivity Problems with IETF Tools Page


Adding tools-discuss where answers may be found...

S

On 02/12/14 12:16, Daniel Burnett wrote:
> Yes, I was having the same problem yesterday, with anything hosted at
> tools.ietf.org.  Haven't had time to try to debug yet . . .
> 
> -- dan
> 
> On Tue, Dec 2, 2014 at 4:14 AM, Hannes Tschofenig <hannes.tschofenig <at> gmx.net
>> wrote:
> 
>> Over the last few days I had noticed problems connecting to the IETF
>> tools page (such as https://tools.ietf.org/wg/dice/trac/report/1).
>>
>> Sometimes it worked, sometimes it didn't. It was always slow.
>>
>> Did someone notice something similar or is it just my side?
>>
>> Ciao
>> Hannes
>>
>>
> 

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
(Continue reading)

Carsten Bormann | 24 Nov 06:49 2014

Re: xml2rfc HTML renderer breaks at Fig. 100?


> On 23.11.2014, at 22:40, Julian Reschke <julian.reschke <at> greenbytes.de> wrote:
> 
>> On 2014-11-23 22:29, Yaron Sheffer wrote:
>> One more data point: when I save the document to a file named f.html,
>> Firefox breaks. But when I rename the file to f.xhtml, Firefox renders
>> it correctly (<div id="bla"/> is valid XHTML). In other words, it parses
>> the file by its extension and ignores the DOCTYPE.
>> 
>> Thanks,
>>     Yaron
> 
> 
> I agree that something is wrong with Firefox.

Yes, there is a bug triggered in Firefox by the bug in the HTML converter.

The bug in the HTML converter is that it is generating valid XHTML.   This same byte string happens also to be
valid HTML, but with a different meaning, which is not reflecting the intention of the source.  While most
browsers will render that alternate meaning in a way that resembles the XHTML meaning, this is just an accident.

> 
> That being said: the web service really really shouldn't serve XHTML content as text/html.

That battle was lost more than a decade ago, together with the whole botched upgrade to XHTML.  Very sad, but
bridge under the water.

So I was proposing to bugfix the HTML converter to generate HTML that means the same that the XHTML means. 
Never generate <gi/> syntax for elements that are not empty elements in HTML.  Instead, generate the
equivalent <gi></gi> syntax for those.  br, meta etc. of course should stay <gi/> as with all elements
(Continue reading)

Tony Hansen | 22 Nov 16:49 2014
Picon

Re: xml2rfc HTML renderer breaks at Fig. 100?

On 11/22/14, 4:54 AM, Julian Reschke wrote:
> On 2014-11-21 22:33, Tony Hansen wrote:
>> I'm going to mark THIS one down as a bug in the FireFox renderer, and
>> NOT as an XML2RFC bug.
>
> The version I tried yesterday in Firefox indeed contains:
>
>> <p class="figure">Figure 99: Salt, base64url-encoded</p>
>> <p id="rfc.section.5.3.3.p.3">Performing the key encryption operation 
>> over the CEK (Figure 97)) with the following:</p>
>> <p>
>>
>> </p><ul>
>>   Password (Figure 96;
>>   <li>Salt (Figure 99), encoded as an octet string; and</li>
>>   <li>Iteration count (8192)</li>
>> </ul>
>> <p id="rfc.section.5.3.3.p.5">produces the following encrypted key:</p>
>> <div id="rfc.figure.100">
>>
>> d3qNhUWfqheyPp4H8sjOWsDYajoej4c5Je6rlUtFPWdgtURtmeDV1g
>>
>> Figure 100: Encrypted Key, base64url-encoded
>> 5.3.4. Encrypting the Content
>> The following are generated before encrypting the content:
>> ...
>
> So an open <div> after fig 100 that never gets closed.

The source HTML file contains:
(Continue reading)

Yaron Sheffer | 21 Nov 20:32 2014
Picon

xml2rfc HTML renderer breaks at Fig. 100?

Hi,

I am reviewing this draft-ietf-jose-cookbook-06. This is a very long document. The text version is fine, and so is the "HTMLized" version. But the nicely formatted HTML (http://tools.ietf.org/id/draft-ietf-jose-cookbook-06.html), my favorite format by far, is garbled exactly at Figure 100. I can reproduce the problem when running xml2rfc locally.

Thanks,
    Yaron
--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Carsten Bormann | 14 Nov 21:35 2014

Replaced active drafts

I just had a look at http://tools.ietf.org/wg/6lo/ to check the active drafts.
This is a very useful resource, so it is worth thinking about its usability.

Right now, the active drafts view is cluttered by this replaced-by information:



draft-ietf-6lowpan-btle
replaced by draft-ietf-6lo-btle -12 2013-02-12  
draft-ietf-6man-6lobac
replaced by draft-ietf-6lo-6lobac -01 2012-03-12  
draft-mariager-6lowpan-v6over-dect-ule
replaced by draft-ietf-6lo-dect-ule -03 2013-07-15  


This is probably useful as long as the replaced drafts are themselves not too old.
But a reminder that a 2012 draft used to have a different working group than the current draft is probably not needed here and reduces clarity.

Do other users of this page care about this?

Grüße, Carsten

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Adrian Farrel | 8 Nov 18:50 2014
Picon

I-D submissions bug? Fwd: I-D Action: draft-ietf-pce-stateful-pce-inter-domain-lsp-00.txt

Hi,

Not sure whether this is an AMS tool or a tools team tool...

It looks very much like the authors of
draft-ietf-pce-stateful-pce-inter-domain-lsp-00 were able to post it without
needing chair approval.

Some time back postings of draft-ietf-foo-bar were always held for approval by
the chairs of the foo working group. There was an email sent to the chairs and a
link they needed to go to for approval. There was also a facility or
pre-approval.

This I-D appears to have got through the net (although we still need to shine a
bright light into the eyes of the chairs to make sure they are telling the truth
;-)

Since, in this case, the I-D is misnamed and should not appear as a WG I-D, it
is a bit untidy (there was no malice involved, I think, and the chairs are
handling the situation).

Cheers,
Adrian

> -----Original Message-----
> From: Pce [mailto:pce-bounces <at> ietf.org] On Behalf Of
> julien.meuric <at> orange.com
> Sent: 07 November 2014 16:47
> To: draft-ietf-pce-stateful-pce-inter-domain-lsp <at> tools.ietf.org
> Cc: pce <at> ietf.org
> Subject: [Pce] Fwd: I-D Action: draft-ietf-pce-stateful-pce-inter-domain-lsp-
> 00.txt
> 
> Authors of the aforementioned document,
> 
> In file names posted into the datatracker, "draft-ietf-xxx" is a
> reserved string for internet drafts endorsed as a work item by IETF
> working groups. Your draft is *not a WG document*. As a result, we have
> marked it as dead. If you want to submit a proposal to the IETF, you
> should publish a file named "draft-<my individual name/string>-xxx".
> 
> Regards,
> 
> JP & Julien
> 
> 
> -------- Message transféré --------
> Date :     Mon, 27 Oct 2014 07:35:06 -0700
> De :     internet-drafts <at> ietf.org
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>   This draft is a work item of the Path Computation Element Working
> Group of the IETF.
> 
>          Title           : Cooperative Stateful Path Computation Element
> (PCE) for Inter-Domain Inter-Vendor PCE-initiated LSP Setup
>          Authors         : Xiaoping Zheng
>                            Nan Hua
>                            Wangyang Liu
>                            Bingkun Zhou
>                            Guoying Zhang
>      Filename        : draft-ietf-pce-stateful-pce-inter-domain-lsp-00.txt
>      Pages           : 12
>      Date            : 2014-10-27
> 
> Abstract:
>     A stateful Path Computation Element (PCE) maintains the information
>     of Label Switched Path (LSP) and resource availability within a
>     domain, so multiple stateful PCEs are able to provide traffic
>     engineering inter-domain routing through cooperating with each other.
>     This document introduces the applicability of cooperative stateful
>     PCE for establishing inter-domain inter-vendor LSP which is initiated
>     by PCE.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-inter-domain-lsp/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-pce-stateful-pce-inter-domain-lsp-00
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Pce mailing list
> Pce <at> ietf.org
> https://www.ietf.org/mailman/listinfo/pce
> 
> 
> 
> 
> 
> ______________________________________________________________
> ___________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
> message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete
this
> message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> Pce mailing list
> Pce <at> ietf.org
> https://www.ietf.org/mailman/listinfo/pce

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Michael Richardson | 3 Nov 21:21 2014
X-Face
Picon

http://sandbox.ietf.org


Hi, http://sandbox.ietf.org redirects to https://sandbox.ietf.org/
but:

Issued On       7/22/13
Expires On      8/11/14

it has an expired certificate.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr <at> sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Martin Thomson | 30 Oct 05:02 2014
Picon

Github template for drafts

I've been using github for managing my drafts for a while now.  Github
has been particularly successful in attracting and managing some
fairly broad collaboration in HTTP/2, and several other working groups
are now successfully using the model.

I've prepared a template that makes putting a repository together
extremely simple:

  https://github.com/martinthomson/i-d-template

This has now been used successfully by several people, some of whom
had no background in this at all.  Now I'm sharing this more widely,
since it seems to be pretty stable.

A feature of note is that it can integrate with a continuous
integration system, so you can't bust a draft without noticing
quickly.  It can also automatically generate a nice web page, e.g.,
https://unicorn-wg.github.io/sslv3-diediedie/

And it's on github, so of course it's open to new contributions.

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Chris Morrow | 29 Oct 14:49 2014
Picon

'edit shepherds document' link failure?

Say from this example:
  <http://datatracker.ietf.org/doc/draft-ietf-idr-as-migration/>

clicking on the little pencil by 'Shepherd Write-Up:' which is:

<http://datatracker.ietf.org/doc/draft-ietf-idr-as-migration/shepherdwriteup/?

and ... I get the empty shepherds document page with 'edit', clicking on
'edit' gets me:

"The server encountered an internal error and was unable to complete
your request. Either the server is overloaded or there was an error in a
script used to generate the requested page. In case this was an overload
problem or other temporary error, you may want to try again in a little
while.

A failure report with details about what happened has been sent to the
server administrators. It would be helpful if you would file a bug
report with additional information at the IETF database issue tracker, too"

guess it's back to the oldschool email-iesg-secretary path?

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Jeffrey (Zhaohui) Zhang | 28 Oct 16:36 2014
Picon

reply button on ietf mail archive

Hi,

For each archived message, could there be a button so that one could "reply" to a posted message? I don't keep
all mailing list messages, and sometimes I need to go back to an archived one and reply to it. Currently
there is no convenient way to do it.

I suppose this is not an uncommon situation people may run into. How do you deal with it?

Thanks.
Jeffrey

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Michael Richardson | 28 Oct 15:17 2014
X-Face
Picon

google thinks etherpad is phising


Several people (nomcom call yesterday, 6tisch security team this morning)
get this in the past day from etherpad.tools.ietf.org:
        http://www.sandelman.ca/tmp/mcrcapture/6969.2014-10-28/capture1.png

specifically, a warning that the site is a phising site.

I expect that it's a false positive, but in order to get the details, you
have to connect to the Google web site manager portal to find out.

--
Michael Richardson <mcr+IETF <at> sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please reports tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Gmane