Martin Vigoureux | 24 Jul 19:09 2015

heritage through replacement?

Hi,

as Shepherd of draft-ietf-l2vpn-spbm-evpn-02 I had prepared the write-up 
for the document. I had also done a review of the doc.
The author decided to republish as draft-ietf-bess-spbm-evpn-00.
I had no opposition to that since the item is being handled by BESS 
since the closure of L2VPN.
However when I marked draft-ietf-l2vpn-... as replaced by 
draft-ietf-bess-... I realized that the latter did not inherit the 
characteristics of the former (intended status, state, write-up, 
shepherd, ...).

I had no precise expectation regarding that rather I was curious to know 
what would be the result.

Now that I know, I wonder if some characteristics shouldn't be copied 
from one to the other, or even ideally that we be given the choice of 
what to replicate.

Thoughts?

-m

--

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

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
(Continue reading)

Stephen Farrell | 24 Jul 11:59 2015
Picon
Picon

weird tokbind wg page results


Hiya,

Yoav (cc'd) and I are accessing [1] and his browser shows
this as a concluded wG, whereas mine correctly shows this
as an active WG. Using wget both of us see it as active.

I guess this is some weird scripting thing somewhere. Yoav
can tell you browser details. (Mine's FF-latest/ubuntu-latest).

Any ideas?

Ta,
S.

[1] https://tools.ietf.org/wg/tokbind/

--

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

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

Tony Hansen | 19 Jul 12:49 2015
Picon

question on datatracker access to particular I-D version

I'm working on generating bibxml3 (bibxml for internet drafts) via
django and the datatracker database.

Is there a way to pull up a >particular version< of an I-D on the
datatracker via the URL?

That is, URLs such as

http://datatracker.ietf.org/doc/draft-hansen-rfc-use-of-pdf-02
http://datatracker.ietf.org/doc/draft-hansen-rfc-use-of-pdf?version=02
http://datatracker.ietf.org/doc/draft-hansen-rfc-use-of-pdf-02.txt
http://datatracker.ietf.org/doc/draft-hansen-rfc-use-of-pdf/02

as opposed to

http://datatracker.ietf.org/doc/draft-hansen-rfc-use-of-pdf

which pulls up the final document and lets you get at the earlier
versions after additional clicks.

    Tony Hansen

Full discussion:

I'm also looking at the possibility of making an update to remove the
<format> entries and replacing them with a target on the <reference>
element.

I had *thought* that I could do this using a reference to the
datatracker copy of the internet drafts. But there is an issue.
(Continue reading)

Glen | 17 Jul 14:51 2015

Glen (AMS IT) In Prague

Greetings!

For those of you who may not know me, I'm Glen Barney, the IT Director at AMS, which is the company that provides secretariat and IT services to the IETF. I'm just emailing to let you know that I'd love to say Hi to, or chat with, any of you, here at IETF 93 in Prague.

One of the main reasons I come to the meetings, when I can, is to make myself available to you, members of the IETF leadership, ADs, Working Group chairs, and volunteers, in the event that you want to talk about anything related to AMS IT stuff.  If you have questions, or comments, or suggestions, just want to talk, have a beer, or throw food at me, I absolutely want to talk to you and meet you here in Prague!

I may be moving around quite a bit this meeting, but you can easily reach me in any of the following ways:

Google Hangouts or Email:  glenams <at> gmail.com  (Most reliable way, text, voice or video!)

Google Plus:  https://plus.google.com/113536982200502888028  (Circle me or send me a message)

Twitter:  <at> glenamstweets (Follow and DM or send me a <at> mention)

I'm here in Prague through the end of Tuesday, and I will be present and available and hoping to meet as many of you as possible!

Thanks!

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)
--

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

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Stephen Farrell | 16 Jul 12:35 2015
Picon
Picon

mail archives without JS


Hiya,

Carlo (cc'd) has told me that he's having problems with a discussion
in which he's participating as folks are using archive links like [1]
that require JS to follow. And his browser has JS turned off for
security reasons. In my case, I allow JS from ietf.org, but he's not
as regular a participant so it's reasonable that he does not.

There are non-JS archives for all lists still, (in this case [2] I
guess) but finding those is hard for folks who don't know where to
go. I think in some cases the WG page archive pointer only goes to
mailarchive.ietf.org, whereas in others (including rtcweb) you get
a pointer to the mhonarc archive. And of course finding the right
message in [2] when given [1] is time consuming, esp. if the message
is not on page 1 of [2].

Is there something we can do to make this better/easier for folks
who have JS always-off or disallowed for ietf.org?

I'm not sure there's a great answer here as mailarchive.ietf.org
does provide nice new features, and any good answer might end up
with "folks should look out for this and jump in sending a link
to the mhonarc archive" but I thought I'd ask as it is good
practice for people to not trust JS from what is to them just
some random web site when they're participating in an email
discussion on a particular issue but perhaps not following the
WG in all detail. (And that's inevitable for a WG like rtcweb:-)

One probably stupid suggestion might be a form where I could
paste in [1] and get a link to that message in mhonarc maybe,
or a link on [1] to the message in mhonarc somewhere on the
page displayed when one de-references [1]?

Thanks,
S.

[1]
https://mailarchive.ietf.org/arch/search/?email_list=rtcweb&gbt=1&index=VnStGD7Emmvc1-QOPRtY2cFF79E
[2] https://www.ietf.org/mail-archive/web/rtcweb/current/maillist.html

--

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

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

Robert Sparks | 10 Jul 18:00 2015

Raw 1st draft: SoW for improvements to the manual submission process

The transparency of the ID submission process needs to be improved,
particularly for those submissions that are handled directly by the
secretariat ("manual" and "forced" submissions).

When an author uses the datatracker submission tool, SubmissionEvents
are captured, noting when the draft was submitted, when it was approved
by previous authors (and by who), when it was approved by a WG chair if
such approval was necessary, and when it was posted into the
repository. Currently, the document’s history shows only that a new
version is available.

The submission tool presents an option to authors to request that the
secretariat finish the submission process. The datatracker captures the
candidate document and sends email to the secretariat. Often the
request is made because the submission tool was unable to extract the
correct meta-data from the document. In this case, the secretariat
populates the meta-data, and forces the post. In other cases, there are
issues identified by id-nits that the secretariat helps diagnose, and
the author is guided through fixing the issues and restarting the
submission process with a repaired document. Again, SubmissionEvents
are captured as the document goes through this process, but for drafts
that are forced, the document history does not reflect these events.

The secretariat also receives requests to post a draft by direct email,
bypassing the submission tool altogether. (Currently, the secretariat
receives around 10 such requests each meeting cycle). The secretariat
operates the submission tool on behalf of the author. The
SubmissionEvents currently captured do not reflect that this was a
manual submission request.

The secretariat currently relies on a combination of RT and personal
email archives to keep track of the outstanding manual submission
requests.

This project will make the following improvements:

When a document is posted via the normal submission process, DocEvents
reflecting the SubmissionEvents for the initial submission, the
approval of previous authors, and the approval of a stream authority
(such as WG chairs for a WG -00) will be added to the document. That
is, where documents currently typically have a first history entry of
"New version available: whatever-00", The first entries will be "New
version submitted", "New version approved by previous author: (name)",
"WG -00 approved by (name)", "New version available: whatever-00". The
entries for subsequent versions are analogous.

When manual submission is requested via the submission tool, and the
document is posted by the secretariat, DocEvents reflecting that the
manual posting was requested, any approvals obtained, and that the
document was forced will be added to the document.  An example of the
entries would be  "Manual submission requested by (name)", "Meta-data
set to <metadata> by (name)", "WG -00 approved by (name)", "New version
available: whatever -00".

When manual submission is requested by direct email, the secretariat
will have the ability to tell the tracker that the request was received
and upload the document from the email request, but not handle the
request immediately. After this indication, the document will be in the
same condition as a document requesting manual submission via the
submission tool.

However the secretariat should not be forced to take that extra step if
the request will be processed immediately. The submission tool should
be modified to allow the secretariat to indicate they are submitting
the document on behalf of an author at their request for manual
submission. SubmissionEvents indicating that manual submission was
requested will be created. Once the document is posted, DocEvents
reflecting the history of the submission (as described for the above
cases) will be created.

A page will be created (readable by anyone) that shows the set of
outstanding manual submission requests. Each entry will either show, or
provide navigation to a separate page that shows, the SubmissionEvent
history for the outstanding submission. When logged in as the
secretariat, there will be easy navigation from each entry to the page
that allows processing the request.

Note that as of release 6.0.4, the manual submission process results in
a DocEvent that says simple "New version available" without providing a
link to the version that became available.  This project will ensure
that all paths that produce a "New version available" DocEvent include
a link to the new version in the event’s description.

--

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

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Tom Pusateri | 9 Jul 20:32 2015

time required to retrieve drafts has increased

Lately, it seems like it takes much longer to retrieve the redirection for an HTML version of a draft and then
for the draft itself.

butte-2% time curl http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp   
<html>	
<body>
   <p>
      The document is available here: <a href="http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp-01">http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp-01</a>.
   </p>
</body>
</html>
curl http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp  0.01s user 0.01s system 0% cpu 30.849 total
butte-2% time curl http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp
<html>	
<body>
   <p>
      The document is available here: <a href="http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp-01">http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp-01</a>.
   </p>
</body>
</html>
curl http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp  0.01s user 0.01s system 0% cpu 36.465 total

It’s taking on average around 33 seconds to get the redirect to the appropriate version and then another 6
seconds on average to get the draft:

curl http://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp-01  0.01s user 0.01s system 0% cpu 6.673 total

This seems much longer than it used to be. Any insight?

Thanks,
Tom
--

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

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Eggert, Lars | 8 Jul 10:30 2015
Picon

W3C Validator Suite

Hi,

do we have access to the W3C Validator Suite (https://validator-suite.w3.org/) for validating IETF
pages? If not, could we set up a friendly deal with them?

(Want to check during codesprint that the various facelifted datatracker pages are valid HTML5.)

Lars
--

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

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Chris Rebert | 8 Jul 08:36 2015

Idnits-2.13.02 feedback: Apostrophe bug in helpmsg

Hello,

Part of the message output by `idnits --help` reads:
>         --nowarn        Don\047t issue warnings, only ID-nits violations

There should obviously be an apostrophe instead of the 4 characters
"\047".

Presumably this was a minor oversight from when the usage() AWK
function was copied and translated into bash as the helpmsg()
function.
Line 3528 of the helpmsg() bash function can and should just use a
literal apostrophe in its source code.

Cheers,
Chris

--

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

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

Tom Pusateri | 8 Jul 00:47 2015

TLS Forward Secrecy

I am working on an update for the IETF app and testing it in a pre-release of iOS 9. Apple has enabled much
stricter TLS default settings in iOS 9 and OSX El Capitan. Currently, I have to set
NSTemporaryExceptionRequiresForwardSecrecy to NO in order to make a TLS connection to any of the tools
or datatracker IETF sites. From the Apple docs, this appears to mean that the site I am connecting to
doesn’t support Forward Secrecy and so I have to put in an exception to not require this. If I don’t, the
TLS connection fails.

Does anyone know if the current TLS settings are intentional with respect to forward secrecy?

An example URL that I am talking about is:  https://tools.ietf.org/wg/v6ops/charter.txt

Thanks,
Tom

--

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

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Fred Baker (fred | 8 Jul 00:38 2015
Picon

Odd Datum

I'm looking at http://datatracker.ietf.org/doc/search/?sort=status&activedrafts=on&name=v6ops.

Let me point you to two drafts in it.

draft-ietf-v6ops-siit-eam-01 is listed as a "WG Document".

draft-ietf-v6ops-design-choices, which is also a WG Document, is listed as being "in WGLC", but not as a WG
document (a WG can do a last call on a non-working-group draft).

This is new. Looks like a bug.
--

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

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

Gmane