Martin Thomson | 22 Mar 17:34 2015
Picon

Missing 's' on week-view

https://datatracker.ietf.org/meeting/92/week-view.html

Includes an inline dump of the sessions.  The links in here are all
http://, which causes the agenda to fail to render on some browsers.

--

-- 
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

Glen | 20 Mar 02:59 2015

Glen (AMS IT) in Dallas

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.

For those of you who -do- know me, well, sadly, I've missed quite a few meetings, but I'm excited to report that I'm going to be in Dallas for the early part of the meeting next week!

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 in Dallas!

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

Google Plus:  https://plus.google.com/113536982200502888028  (Circle me or send me an email or a hangout at glenams <at> gmail.com )

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

Email:   glen <at> amsl.com

I'll be in Dallas from Saturday morning through Tuesday noon, and, with Matt Larson (also from AMS IT), 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 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
Fred Baker (fred | 10 Mar 23:20 2015
Picon

internet draft notifications

I imagine you are seeing the thread on ietf <at>  about draft announcements. Here’s a thought.

What if some tool at AMS, instead of instantly posting an email saying “we got another draft”, added the
name and abstract of the draft to some file somewhere associated with a mailing list (ietf <at> , work group
list, or whatever else), and at the end of the day (by some definition - 5:00 PM on the east side of the date
line perhaps) sent all of the emails, one per list? That would give people the batching effect they mention...
--

-- 
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
Robert Sparks | 9 Mar 23:10 2015

Fwd: Details about where the tracker is currently sending mail

Hrmm - that went into moderation.
The attachments are also at
http://www.nostrum.com/~rjsparks/email-analysis.xlsx
and
http://www.nostrum.com/~rjsparks/email-analysis.pdf

Moderator - feel free to nuke the original message


-------- Forwarded Message -------- Subject: Date: From: To:
Details about where the tracker is currently sending mail
Mon, 09 Mar 2015 17:01:02 -0500
Robert Sparks <rjsparks <at> nostrum.com>
Tools-discuss <at> ietf.org


All - The attached spreadsheet (and a pdf printout from it) summarize when mail comes out of the tracker and who that mail goes to. The solid dots in the matrix mean mail is always sent. The open dot means mail is conditionally sent (and the condition is explained in the notes). There is one row (about ballots) that has a checkbox symbol - that means the AD can select or unselect that destination (an alias in this case), before sending. The notes call out the other places that the sender has an opportunity to change the destinations before the message is sent. I took one shortcut that doesn't align with the above to make the chart less messy. When you see solid dots for group chairs and shepherds, know that if a document has no group, or no shepherd has been assigned, then those destinations aren't used. I also haven't included a few messages that the tracker sends. Specifically, I didn't list the messages related to the community tracker (subscribing to changes for a draft and getting the mail for those changes). The destination addresses there are always the person subscribing. I didn't include the messages that are sent only to the secretariat by robots (such as the iana sync report, the rfc-editor queue message, or when the tracker lets the secretariat know that a message tried to go out with a bad email address in it). I didn't include the messages sent to verify email when setting up a datatracker account. If you're interested, you can see a code-oriented view that _does_ include all those cases at <http://www.nostrum.com/~rjsparks/email-analysis/>. If you see something in the spreadsheet or in the web page above that you don't think is right, ask me. This was a brutal compilation effort - the odds that I didn't get something wrong are small. RjS

--

-- 
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
Robert Sparks | 9 Mar 22:52 2015

For tomorrows call: Email handling in the datatracker

All -

As I hope you've seen on ietf <at> ietf.org, there is some pain around how 
email is currently being sent through the aliases and from the tracker.
Here is some background for discussion tomorrow. Please read through 
this before we get to the meeting.

Henrik and I have both been studying this, and have several steps we are 
going to take right away. I've also been discussing how draft ballot 
email is handled with Pete to prepare a proposal for the IESG to agree on.

I will send a separate message with more detail than you want (but you 
need it) about where the tracker is sending mail right now.

In short, we have these factors primarily contributing to the pain:

1) In November, we started adding the working group list to the .notify 
alias by default at the request of the IESG. This was driven by the IESG 
wanting the group to see ballot positions, and make it likely that 
responses to those positions would be in-thread.

2) Shortly after, we started migrating to  <at> ietf.org aliases instead of 
tools.ietf.org alias.

3) 10-11 days ago (depending on when you read this message), we started 
forwarding the aliases  <at> tools.ietf.org to use the aliases at  <at> ietf.org 
instead of expanding them on the tools server.

Now, there were several things related to those 3 changes that have 
rough edges:

a) Adding the working group list to .notify had an unintended 
consequence. What we didn't account for is that the contents of .notify 
get expanded into the .all alias, so people sending mail to .all for 
some draft end up sending to the list.

b) When tools.ietf.org was expanding aliases, it added Resent-To and 
Resent-From headers. The expansion at ietf.org does not currently do 
that, and we are working to fix it. Some people were filtering on these 
headers. It's also likely (we haven't confirmed this yet) that Mailman 
was using the headers to bypass putting mail to .all into moderation for 
having an implicit destination.

c) The aliases at ietf.org are _NOT THE SAME_ as the aliases at 
tools.ietf.org! The datatracker allows addresses to be marked active or 
inactive. If an address that's in a draft is marked inactive, then the 
ietf.org alias will not use it - it will find the most recently changed 
active address for that person instead and use that. The tools.ietf.org 
aliases are not aware of these bits, and used the address in the draft 
always. Further, when addresses are learned from drafts by the submit 
tool, with the currently deployed code, they are marked inactive (the 
idea at the time was that we didn't want mail to start going to a 
different address for a person each time they submitted a draft using a 
different email address - several years ago we had a big problem with 
people being surprised by such automatic changes. Instead, they could 
activate each address they wanted the tracker to use.)

So, we are making the following changes right away:

Now - i) We are teaching the tracker about a "preferred" address to use 
whenever context doesn't indicate a better choice (often context will 
say to use the address attached to a chair role for instance). The 
address the tracker is preferring now (specifically the last active 
address that's been touched) will be marked "preferred".

Now - ii) We are marking the addresses that are in drafts that are 
current as active. If someone with an account has an addresses active 
state changed by this, we will send mail to the affected address and all 
other active addresses for them letting them know it happened (in case 
they really _wanted_ that address to be inactive). As new drafts go 
through the submit tool, any learned addresses will be marked active 
(but note that the "preferred" address will not be automatically changed).

After that release, most of the addressing that has been surprising 
people in the last 10 days will be resolved. The ietf.org aliases will 
much more closely match what had been being generated at tools.ietf.org.

We (primarily Glen and Matt) are also continuing to work on getting 
Resent-To and Resent-From into mail forwarded through the aliases at 
ietf.org. We should set the priority for this on tomorrows call (I 
suggest it that it's priority should be high).

Now, early discussions with Pete and Henrik lead to this rough proposal 
that will be sent to the IESG. This is a draft idea, and we won't 
execute on it until the IESG says to (Pete, note this is slightly 
different than what we discussed last). I expect the discussion with the 
IESG to change this some.

Soon - i) The "Save and Send Email" page in the ballot editing workflow 
currently offers the content of the .notify field with a checkbox 
(selected by default). We plan to add another row, with the group's list 
address, also with a checkbox selected by default. If the AD sending the 
message doesn't want the list copied, they unselect the box next to the 
list address. (We might, instead, have to turn this into a bit that 
lives on the document that the sponsoring AD manages, making it their 
choice rather than the balloting ADs choice).

Soon - ii) We will scrub all the documents and remove the list address 
from the .notify field. We'll send notes to the document personnel of 
each affected document so they can verify that the result is what they want.

Soon - iii) We'll add a .group alias for people to use to copy the WG 
list for a draft without having to look it up. The contents of this 
alias would not be included when sending to .all

Sorry for the long message, but there's a lot involved here. Hopefully 
I've teased it apart into easier to follow chunks.

Talk to you all tomorrow,

RjS

--

-- 
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

Carlos Pignataro (cpignata | 25 Feb 21:56 2015
Picon

Change on the draft aliases

Hi,

There seems there has been a recent change on how draft aliases are expanded — maybe related to moving the aliases and the changes at https://datatracker.ietf.org/release/5.11.1/ [9083] [9070], maybe not?

draft-kumarkini-mpls-spring-lsp-ping: draft-kumarkini-mpls-spring-lsp-ping <at> ietf.org


One implication is that the Resent-to header does not include individual email addresses expanded:
From:
Resent-To: Carlos Pignataro Hannes Gredler Mach Chen Nagendra Kumar Nobo Akiya Sri Kini George Swallow // addresses removed
To: 

This broke filters that rely on finding individual email addresses in this header. This is not the case on the “WG alias file” (yet?).

Could we have the individual addresses added back to this Header?

Thanks!

— Carlos.

--

-- 
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
Benoit Claise | 24 Feb 23:34 2015
Picon

www.ietf.org/rt #73576] charters difference


Hi,

As mentioned below, this one is for you.

Regards, Benoit


-------- Forwarded Message -------- Subject: Date: From: Reply-To: To:
[www.ietf.org/rt #73576] charters difference
Tue, 24 Feb 2015 13:42:40 -0800
Naveen Khan via RT <ietf-info <at> ietf.org>
ietf-info <at> ietf.org
bclaise <at> cisco.com


Hi Benoit, As the secretariat does not manage the tools page, please email tools <at> ietf.org in order to get this changed. Sincerely, Naveen Khan IETF Secretariat On Tue Feb 24 12:56:19 2015, bclaise <at> cisco.com wrote: > Hi, > > I see a difference between > https://tools.ietf.org/wg/radext/charters > https://datatracker.ietf.org/wg/radext/charter/ > > https://datatracker.ietf.org/wg/radext/charter/ is the right one, with > Kathleen as the correct area director. > > Regards, Benoit >



--

-- 
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
Richard Barnes | 24 Feb 20:44 2015

New account -> Chair

Hey tools team,

I'm trying to add Mo Zanaty <mzanaty <at> cisco.com> as co-chair of CODEC.
http://datatracker.ietf.org/wg/codec/edit/

Mo tells me that he's created an account, but the "Chairs" box can't seem to find him.  Any ideas why this might be?  Is there some propagation delay?

Thanks,
--Richard
--

-- 
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
Bjoern Hoehrmann | 11 Feb 01:49 2015
Picon
Picon

http://tools.ietf.org/list/<listname> directory listings

Hi,

  E.g. http://tools.ietf.org/list/ietf-privacy/ contains a directory
listing of `<message id>.eml` files with mailing list messages up to
mid-2012. For some lists like http://tools.ietf.org/list/tap/ I get a
`404` response, but Google Search still shows similar results. That
does not seem right.

regards,
-- 
Björn Höhrmann · mailto:bjoern <at> hoehrmann.de · http://bjoern.hoehrmann.de
D-10243 Berlin · PGP Pub. KeyID: 0xA4357E78 · http://www.bjoernsworld.de
 Available for hire in Berlin (early 2015)  · http://www.websitedev.de/ 

--

-- 
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

Benoit Claise | 9 Feb 19:01 2015
Picon

Re: Online YANG validation

Dear all,

I have not seen any reply to this one.
Since I provided this mailer to Carl, I'm wondering: is this the right one?

Regards, Benoit
> Tools Team,
>
>   As part of our efforts ongoing in the YANG model coordination group we're looking at putting together an
online YANG module validation tool. We're looking to likely leverage the pyang YANG validator and
converter in python (https://code.google.com/p/pyang/) with a simple web ui. It will likely end up
looking something like the venerable web interface to libsmi (https://www.ibr.cs.tu-bs.de/projects/libsmi/tools/).
>
>   My initial thought is be to see if we can host it on the tools.ietf.org infrastructure if appropriate. It
this something that would fit in there?
>
> Regards,
> --
> Carl Moberg
>
>
>
> .
>

--

-- 
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

Tony Hansen | 6 Feb 21:58 2015
Picon

conditional query in draft submission for draft-i*-00 drafts

When a draft-ietf-....-00 draft is submitted, and often when a 
draft-iab-...-00 or draft-irtf-...-00 draft is submitted, it's a 
WG/IAB/RG-accepted revision of a previous individual submission.

There is a field in the datatracker database for this to be populated, 
which allows various tools, including the datatracker and 
tools.ietf.org/html/draft.... to provide proper linkage across versions. 
(For example, the tools.ietf.org/html version will show you a pointer to 
the previous individual submission and let you do a diff from the -00 
against the individual submission as well.)

However, this ONLY works when that pointer is populated. Right now, it 
almost always requires a manual poke at ietf-action or ietf-secretariat 
to get the linkage fixed up.

I know of several documents recently added to the draft-iab track (that 
were previously individual submissions) where the manual poke took 
significant time.

I'd like to propose that, when the file being submitted is named 
draft-ietf-...-00, draft-iab-...-00 or draft-irtf-...-00, another text 
box becomes visible that lets the author fill in the previous individual 
submission's filename. This information would be sent directly to the 
proper address at the secretariat for verification, and then the link 
can be added to the database by the secretariat.

Another additional enhancement would be tool support for the secretariat 
to use make easier the verification that the individual submission 
listed really is the previous version. (For example, show an iframe 
displaying the tools.ietf.org version of the individual-submission 
document and another iframe displaying the draft-i*-00 document, and a 
button that can be clicked to add the pointer data to the database.)

     Tony Hansen

--

-- 
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