From nobody Sat Jul 2 10:47:53 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17A6312D192 for ; Sat, 2 Jul 2016 10:47:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XhAqhcpruyYq for ; Sat, 2 Jul 2016 10:47:49 -0700 (PDT) Received: from formal.dehy.de (formal.dehy.de [81.169.166.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 448D212D189 for ; Sat, 2 Jul 2016 10:47:49 -0700 (PDT) Received: from hellers.localnet (cable-78-34-41-182.netcologne.de [78.34.41.182]) by formal.dehy.de (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id u62HlkmR021023; Sat, 2 Jul 2016 19:47:46 +0200 From: Antony Stone Organization: IETF To: tools-discuss@ietf.org Date: Sat, 2 Jul 2016 19:47:41 +0200 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <87poqy1v3l.fsf@alice.fifthhorseman.net> <201606301851.16934.Antony.Stone@tools.ietf.org> In-Reply-To: <201606301851.16934.Antony.Stone@tools.ietf.org> X-From: haelentor MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201607021947.41379.Antony.Stone@tools.ietf.org> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (formal.dehy.de [81.169.166.228]); Sat, 02 Jul 2016 19:47:46 +0200 (CEST) Archived-At: Subject: Re: [Tools-discuss] xml2rfc issues? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 17:47:52 -0000 On Thursday 30 June 2016 at 18:51:16, Antony Stone wrote: > On Thursday 30 June 2016 at 18:48:14, Daniel Kahn Gillmor wrote: > > On Thu 2016-06-30 12:30:00 -0400, Julian Reschke wrote: > > > Don't use xml.resource.org anymore. AFAIU, the recommended base URI for > > > references is http://xml2rfc.ietf.org/. > > > > hm, this doesn't work with https either. can we get this set up with > > https? > > Thanks for the comments. > > We're looking into it. http://xml2rfc.tools.ieft.org and https://xml2rfc.tools.ietf.org now point to the same resources. Please note 'tools' in both URLs there. http://xml.resource.org has been redirected for some time, however the https version was broken because of a certificate problem (which I've just fixed). Please let me know if anything remains not as expected. Thanks, -- Antony Stone, systems administrator Internet Engineering Task Force tools servers http://tools.ietf.org From nobody Sun Jul 3 09:22:14 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2A2812D0C3 for ; Sun, 3 Jul 2016 09:22:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MA06SKVZ-kz for ; Sun, 3 Jul 2016 09:22:10 -0700 (PDT) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66EE412B00A for ; Sun, 3 Jul 2016 09:22:10 -0700 (PDT) Received: by mail-yw0-x234.google.com with SMTP id l125so24148178ywb.2 for ; Sun, 03 Jul 2016 09:22:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RtAVaJaQEP1Nyn/eKCcsgkcVyfCUGOwhwXyiRf2Q1KA=; b=RZ6Vr7BRco+gA2Pc+d044ydRKVOzjq899Nv+2yY5WC5KbzF3wBPCjQCzmr0khp5JYq uTZwzPxGzsacPxrAtoKUwJt60zTE7KUZ8wwHgG98o1A0Oz69C9gt8ZP6OiX/MZFY5pBA M3XflUpLs6DWr1ExcfyG8v0JsF7xXmmOR5y2ehDcXzoEC/HxzWnooWHhT9xveMHwJ7wb 8UnflCgZejj0meikjqmU9zylrvBJFReVQcb7rtFQ5sVJDXGTEFj/+0WskfSNTnc3LkOE QjlTU1/sVKFLJwvMBRcc54L2MWyr1v/zXWnSWp6TzLrmTkhV6S7U+jM3OWVfHquTN6Tp OUtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RtAVaJaQEP1Nyn/eKCcsgkcVyfCUGOwhwXyiRf2Q1KA=; b=Bdices/gb49VucizJ35gnG4JDuxeOvO6BZYjfmZkyAHT2N44s8NanE/8WR8LOKVOGu 9DqEMEQFUf6libxdf6OF/z6+qXcoDWgm/r2lVbszCLqPztMoLlFGUMYu9UEMPl4gW11N K5eDw/C3ABdW09gKMUoBx0EdT4C5e2881Ozn2T6hI3Pdm0L+Ps125LU0bcLnFWQWp7Dh aKWNzEcOzGJoxDcGIElXcNThf5pju+f4uwVQwa9ZPoTRwvPJcO4oHg8hGqc4VqNTTTRR KJGKnNH0JwxNdlcBIENB+5F9vLgVF+2EEGTt3sWWeYmalOzuI6a/T6MXAiiSdmxuQRxZ +Z/g== X-Gm-Message-State: ALyK8tL0fHmMdPoxNIFiiq8zBh59IWDVovv1HlJJTVnQs9o2VUIMXtTyA1GjajvIzPYMqSItCEPAxMXNho7HKA== X-Received: by 10.129.46.87 with SMTP id u84mr5462218ywu.214.1467562929579; Sun, 03 Jul 2016 09:22:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.199.201 with HTTP; Sun, 3 Jul 2016 09:22:08 -0700 (PDT) In-Reply-To: <201607021947.41379.Antony.Stone@tools.ietf.org> References: <87poqy1v3l.fsf@alice.fifthhorseman.net> <201606301851.16934.Antony.Stone@tools.ietf.org> <201607021947.41379.Antony.Stone@tools.ietf.org> From: Richard Barnes Date: Sun, 3 Jul 2016 12:22:08 -0400 Message-ID: To: Antony Stone Content-Type: multipart/alternative; boundary=001a114140ba1a6c8c0536bd9fa3 Archived-At: Cc: Tools Team Discussion Subject: Re: [Tools-discuss] xml2rfc issues? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jul 2016 16:22:13 -0000 --001a114140ba1a6c8c0536bd9fa3 Content-Type: text/plain; charset=UTF-8 On Sat, Jul 2, 2016 at 1:47 PM, Antony Stone wrote: > On Thursday 30 June 2016 at 18:51:16, Antony Stone wrote: > > > On Thursday 30 June 2016 at 18:48:14, Daniel Kahn Gillmor wrote: > > > On Thu 2016-06-30 12:30:00 -0400, Julian Reschke wrote: > > > > Don't use xml.resource.org anymore. AFAIU, the recommended base URI > for > > > > references is http://xml2rfc.ietf.org/. > > > > > > hm, this doesn't work with https either. can we get this set up with > > > https? > > > > Thanks for the comments. > > > > We're looking into it. > > http://xml2rfc.tools.ieft.org and https://xml2rfc.tools.ietf.org now > point to > the same resources. > > Please note 'tools' in both URLs there. > So why are you leaving xml2rfc.ietf.org broken? I don't really care whether the "tools" is in there or not, but if you're going to have an A record for that domain, you need to answer for it properly or reject TLS connections. --Richard > > http://xml.resource.org has been redirected for some time, however the > https > version was broken because of a certificate problem (which I've just > fixed). > > Please let me know if anything remains not as expected. > > > Thanks, > > -- > Antony Stone, systems administrator > Internet Engineering Task Force tools servers > http://tools.ietf.org > > -- > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss > > Please report datatracker.ietf.org bugs at > http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org > > Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or > send email to webmaster@tools.ietf.org > --001a114140ba1a6c8c0536bd9fa3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sat, Jul 2, 2016 at 1:47 PM, Antony Stone <Antony.Stone@t= ools.ietf.org> wrote:
On Thursday 30 June 2016 at 18:51:16, Antony Stone wrote:

> On Thursday 30 June 2016 at 18:48:14, Daniel Kahn Gillmor wrote:
> > On Thu 2016-06-30 12:30:00 -0400, Julian Reschke wrote:
> > > Don't use xml.resource.org anymore. AFAIU, the recomme= nded base URI for
> > > references is http://xml2rfc.ietf.org/.
> >
> > hm, this doesn't work with https either.=C2=A0 can we get thi= s set up with
> > https?
>
> Thanks for the comments.
>
> We're looking into it.

http://xml2rfc.tools.ieft.org and https://xml2rfc.tool= s.ietf.org now point to
the same resources.

Please note 'tools' in both URLs there.

So why are you leaving xml2rfc= .ietf.org broken?=C2=A0 I don't really care whether the "tools= " is in there or not, but if you're going to have an A record for = that domain, you need to answer for it properly or reject TLS connections.<= br>

--Richard
=C2=A0

ht= tp://xml.resource.org has been redirected for some time, however the ht= tps
version was broken because of a certificate problem (which I've just fi= xed).

Please let me know if anything remains not as expected.


Thanks,

--
Antony Stone, systems administrator
Internet Engineering Task Force tools servers
http= ://tools.ietf.org

--
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discu= ss

Please report datatracker.ietf.org bugs at http://tools.ietf= .org/tools/ietfdb
or send email to datatracke= r-project@ietf.org

Please report tools.ietf.org bugs at http://tools.ietf.org/tools= /issues or
send email to webmaster@tools.i= etf.org

--001a114140ba1a6c8c0536bd9fa3-- From Antony.Stone@open.source.it Sun Jul 3 10:06:58 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CF812B054 for ; Sun, 3 Jul 2016 10:06:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GBY2rx4Mo_V for ; Sun, 3 Jul 2016 10:06:56 -0700 (PDT) Received: from formal.dehy.de (formal.dehy.de [81.169.166.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5CC0128E19 for ; Sun, 3 Jul 2016 10:06:55 -0700 (PDT) Received: from hellers.localnet (cable-78-34-41-182.netcologne.de [78.34.41.182]) by formal.dehy.de (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id u63H6qaW010325; Sun, 3 Jul 2016 19:06:53 +0200 From: Antony Stone Organization: Open Source IT To: tools-discuss@ietf.org Date: Sun, 3 Jul 2016 19:06:46 +0200 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201607021947.41379.Antony.Stone@tools.ietf.org> In-Reply-To: X-From: haelentor MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201607031906.47198.Antony.Stone@open.source.it> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (formal.dehy.de [81.169.166.228]); Sun, 03 Jul 2016 19:06:53 +0200 (CEST) Archived-At: Subject: Re: [Tools-discuss] xml2rfc issues? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jul 2016 17:51:54 -0000 On Sunday 03 July 2016 at 18:22:08, Richard Barnes wrote: > On Sat, Jul 2, 2016 at 1:47 PM, Antony Stone wrote: > > > > http://xml2rfc.tools.ieft.org and https://xml2rfc.tools.ietf.org now > > point to the same resources. > > > > Please note 'tools' in both URLs there. > > So why are you leaving xml2rfc.ietf.org broken? It's not broken as such, but the certificate presented by that server is for *.tools.ietf.org and therefore doesn't match xml2rfc.ietf.org > I don't really care whether the "tools" is in there or not Good to know, thanks. > but if you're going to have an A record for that domain, you need to answer > for it properly or reject TLS connections. I do not manage the main .ietf.org machines, and therefore I cannot adjust any DNS in that domain, but I shall request this. If it turns out that there are other links pointing to https://xml2rfc.ietf.org which cannot readily be changed, I shall request a certificate for that name and place it on the server. Regards, -- Antony Stone Systems admin IETF Tools servers From nobody Sun Jul 3 19:05:59 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C900212D1B3 for ; Sun, 3 Jul 2016 19:05:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.62 X-Spam-Level: X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i0agYnHikdFb for ; Sun, 3 Jul 2016 19:05:56 -0700 (PDT) Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 556D2128874 for ; Sun, 3 Jul 2016 19:05:56 -0700 (PDT) Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.11/8.16.0.11) with SMTP id u6424B9h009075; Sun, 3 Jul 2016 22:05:48 -0400 Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049287.ppops.net-00191d01. with ESMTP id 23y6ngpq6j-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 03 Jul 2016 22:05:48 -0400 Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u6425lSj024168; Sun, 3 Jul 2016 22:05:47 -0400 Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u6425ZIu024087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 3 Jul 2016 22:05:38 -0400 Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Mon, 4 Jul 2016 02:05:27 GMT Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.60]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0294.000; Sun, 3 Jul 2016 22:05:27 -0400 From: "HANSEN, TONY L" To: Antony Stone , "tools-discuss@ietf.org" Thread-Topic: [Tools-discuss] xml2rfc issues? Thread-Index: AQHR1InUHNKBRbNRZ0ehd7XvTE+pfKAHKBEAgAAMeACAAFOJgA== Date: Mon, 4 Jul 2016 02:05:26 +0000 Message-ID: References: <201607021947.41379.Antony.Stone@tools.ietf.org> <201607031906.47198.Antony.Stone@open.source.it> In-Reply-To: <201607031906.47198.Antony.Stone@open.source.it> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.110.240.246] Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-RSA-Inspected: yes X-RSA-Classifications: public X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-07-04_01:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1607040018 Archived-At: Subject: Re: [Tools-discuss] xml2rfc issues? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jul 2016 02:05:58 -0000 QW50aG9ueSwgdGhhbmtzIGZvciB5b3VyIGVmZm9ydHMgdG8gaGVscCByZXNvbHZlIHRoaXMuDQoN Ck5vdGUgdGhhdCB0aGUg4oCcb2ZmaWNpYWzigJ0gVVJMIGlzIHdpdGhvdXQgdGhlIHRvb2xzIHBy ZWZpeDsgdGhhdOKAmXMgd2h5IHdlIGhhZCB0aGUgQ05BTUUgZm9yIHhtbC5yZXNvdXJjZS5vcmcg cG9pbnQgYXQgeG1sMnJmYy5pZXRmLm9yZyBhbmQgTk9UIHhtbDJyZmMudG9vbHMuaWV0Zi5vcmcu IEF0IHNvbWUgcG9pbnQgaW4gdGhlIGZ1dHVyZSwgaXTigJlzIGVudGlyZWx5IGxpa2VseSB0aGF0 IHhtbDJyZmMgd2lsbCBtb3ZlIG9mZiBvZiB0aGUgdG9vbHMgc2VydmVycyBvbnRvIHRoZSBub24t dG9vbHMgc2VydmVycy4NCg0KCVRvbnkgSGFuc2VuDQoNCk9uIDcvMy8xNiwgMTowNiBQTSwgIlRv b2xzLWRpc2N1c3Mgb24gYmVoYWxmIG9mIEFudG9ueSBTdG9uZSIgPHRvb2xzLWRpc2N1c3MtYm91 bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgQW50b255LlN0b25lQG9wZW4uc291cmNlLml0PiB3 cm90ZToNCg0KDQo+IGJ1dCBpZiB5b3UncmUgZ29pbmcgdG8gaGF2ZSBhbiBBIHJlY29yZCBmb3Ig dGhhdCBkb21haW4sIHlvdSBuZWVkIHRvIGFuc3dlcg0KPiBmb3IgaXQgcHJvcGVybHkgb3IgcmVq ZWN0IFRMUyBjb25uZWN0aW9ucy4NCg0KSSBkbyBub3QgbWFuYWdlIHRoZSBtYWluIC5pZXRmLm9y ZyBtYWNoaW5lcywgYW5kIHRoZXJlZm9yZSBJIGNhbm5vdCBhZGp1c3QgYW55IA0KRE5TIGluIHRo YXQgZG9tYWluLCBidXQgSSBzaGFsbCByZXF1ZXN0IHRoaXMuICBJZiBpdCB0dXJucyBvdXQgdGhh dCB0aGVyZSBhcmUgDQpvdGhlciBsaW5rcyBwb2ludGluZyB0byBodHRwczovL3htbDJyZmMuaWV0 Zi5vcmcgd2hpY2ggY2Fubm90IHJlYWRpbHkgYmUgDQpjaGFuZ2VkLCBJIHNoYWxsIHJlcXVlc3Qg YSBjZXJ0aWZpY2F0ZSBmb3IgdGhhdCBuYW1lIGFuZCBwbGFjZSBpdCBvbiB0aGUgDQpzZXJ2ZXIu DQoNCg== From nobody Tue Jul 5 11:39:50 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA8C12D123 for ; Tue, 5 Jul 2016 11:39:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.534 X-Spam-Level: X-Spam-Status: No, score=-0.534 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eUIlLwm1gLyb for ; Tue, 5 Jul 2016 11:39:48 -0700 (PDT) Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C62E12B055 for ; Tue, 5 Jul 2016 11:39:48 -0700 (PDT) Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-09v.sys.comcast.net with SMTP id KVG7bl6zsAlI7KVG7b7GEg; Tue, 05 Jul 2016 18:39:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1467743987; bh=yJ3N5PcfSdPs6mU7te5lulA4a7QSy8wRXj1SmCHyRJw=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=HyyiCNz5UXHy9sEK2csgOJ7gHl10D2P7n2ilKo12BlJqNOGyulvbGAFIHL3po+okP 9J9BbIsQ0ChHT+ETfAp/e616YMmJ2/6SR2d3i0XD/c+c9dOpk3OpznzH2179ZmWY46 oC69dARkOq5Nll2nIDs3iif48IuRieG+DRjDlmMTa36EpPmCrhA+cdcDzCTmRZEMRP csurNYat4CkCPq/yfc1oLqh4iuLhYL68pg8DwMqo3BEDrnA4aDXdf1itlNPvsUGy29 93pr0lefi6o5W+VCPTh4vgFMmsSE6kbyjBXm2QZ432k8C0iKgRKhHxEMqpShLKoRXS S50KMQCYVrL8A== Received: from hobgoblin.ariadne.com ([73.143.237.82]) by comcast with SMTP id KVG5bLpH3t20pKVG6b6qUq; Tue, 05 Jul 2016 18:39:47 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u65IdjlI031602; Tue, 5 Jul 2016 14:39:45 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u65IdglL031594; Tue, 5 Jul 2016 14:39:42 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: Antony Stone In-Reply-To: <201607031906.47198.Antony.Stone@open.source.it> Sender: worley@ariadne.com (Dale R. Worley) Date: Tue, 05 Jul 2016 14:39:42 -0400 Message-ID: <87y45gc4k1.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfCwtFScF13P28rKXzzKvNnO4TZH+z+Kg0WB4lRhLkdHDcOQ3qBs/3bwlmtKw1CEfVtiKaD5cOYH6AL0Hyor63c9c66gL8PKlWYRE6BtXcaz1iaID9MQI tzaTEbh4ZKrJdD9L4kOp4U651C5KWWk9PVtNglOIvffhe6E/5TEdJYFo7Jh1rJIIzTFYt39gj2SXpW30qR48GXJvaxbVFZpusOevyYWT4266BSlrL9L73SFz Archived-At: Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] xml2rfc issues? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 18:39:49 -0000 Antony Stone writes: >> So why are you leaving xml2rfc.ietf.org broken? > > It's not broken as such, but the certificate presented by that server is for > *.tools.ietf.org and therefore doesn't match xml2rfc.ietf.org In regard to TLS, that sounds plenty broken to me! Dale From nobody Thu Jul 7 08:07:49 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D735012D097 for ; Sun, 3 Jul 2016 23:57:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Af9HR9e0WzzI for ; Sun, 3 Jul 2016 23:57:16 -0700 (PDT) Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com [IPv6:2a00:1450:4010:c07::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0F6712B013 for ; Sun, 3 Jul 2016 23:57:15 -0700 (PDT) Received: by mail-lf0-x243.google.com with SMTP id a2so16273364lfe.3 for ; Sun, 03 Jul 2016 23:57:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=G/RyWFDMYAsnrQfwIUj9ju/n1CvHDVcHy+zqIivbuM8=; b=PRzQGnRkdTYLUpe6NBn842v1kl6Wszcp9vqONJHifPTHy9o1SYpW8NIayKGfj4oX8d x6xpYjEoSHsO02QyHmnOTrW0w4Oj7sysPVgp2M/OF6ah6vPGjXa3hm4r6z5d4xDdTQ1u nDzYCauvRwm837mZk6b5drronbOvwSF2KgWZfJa+T7pmljvgcR/Qs5XNrP0amkAG3M5b 45hQHFUn+aFnfVsFnTZmLQNf1IiYaDirc4m7vze4VOS1q41/PiLFQBg3mbaEB9i8GInB xHfggM+2yQXllnocXh91O+NKtD3MDSRSwx6jXSwb/9ncu9/OMDN5ZUX5Q03PTrmvMo6n pZsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=G/RyWFDMYAsnrQfwIUj9ju/n1CvHDVcHy+zqIivbuM8=; b=WnLwM+4eUxLYTyCIMWyDjXxPNsjXHLpJXnw9yF0ga9aOv5/4C46/28S8uVk/LLBEnB 6TOVEP8cONCyYsJY/y6f9yEZaPMEwrou2Aw6oMCWKiNWR2z45Bfe+r1cAbN5d63sI/6/ kfR3V4003DhZY/YDdhjRAmwjCuVLwxd5coE0cTQjygm6O+YyDBfqVC00k8IrwpCRqPtm /WCANAZccB59/vJLGanMna7A+0KerAGE4tK3cumVSZNafWNLOuxY5L3WINhlW3OdGfbx 5wmZZxQhBQ8aGP5b/AxMOaRawyyMVLMfYNB4nvhgmUByQQ11zLi0MwwuPhBMK32NBB24 a7bA== X-Gm-Message-State: ALyK8tLgd0RzcSeXxz25n6j2/bi1FCzJvwssW4tVP7uHk3jQJADB+RFrgofjLlCTzyppgyMZH4+hP1RMYh8RDg== MIME-Version: 1.0 X-Received: by 10.25.160.75 with SMTP id j72mr2808941lfe.109.1467615433605; Sun, 03 Jul 2016 23:57:13 -0700 (PDT) Received: by 10.25.23.131 with HTTP; Sun, 3 Jul 2016 23:57:13 -0700 (PDT) Received: by 10.25.23.131 with HTTP; Sun, 3 Jul 2016 23:57:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 4 Jul 2016 11:57:13 +0500 Message-ID: From: Garri Djavadyan To: tools-discuss@ietf.org Content-Type: multipart/alternative; boundary=001a114116ae9649820536c9d8c0 Archived-At: X-Mailman-Approved-At: Thu, 07 Jul 2016 08:07:48 -0700 Subject: [Tools-discuss] Problems with HTML markup in RFC2328 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jul 2016 06:57:18 -0000 --001a114116ae9649820536c9d8c0 Content-Type: text/plain; charset=UTF-8 Dear IETF tools support team, The links to subsection number anchors are not work on page https://tools.ietf.org/html/rfc2328, although the links to main section number (w/o dots) works as expected. For example, https://tools.ietf.org/html/rfc2328#section-1.1 Many thanks in advance! Garri --001a114116ae9649820536c9d8c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Dear IETF tools support team,

The links to subsection number anchors are not work on page = https://tools.ietf.org/html= /rfc2328, although the links to main section number (w/o dots) works as= expected. For example, https://tools.ietf.org/html/rfc2328#section-1.1

Many thanks in advance!

Garri

--001a114116ae9649820536c9d8c0-- From nobody Thu Jul 7 10:38:13 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149A712B026 for ; Thu, 7 Jul 2016 10:38:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.9 X-Spam-Level: X-Spam-Status: No, score=-106.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oI3_-t_Ooxff for ; Thu, 7 Jul 2016 10:38:11 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25D2212D82B for ; Thu, 7 Jul 2016 10:38:05 -0700 (PDT) Received: from 81-235-150-134-no105.tbcn.telia.com ([81.235.150.134]:63562 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1bLDFU-0007hm-8m; Thu, 07 Jul 2016 10:38:04 -0700 Message-ID: <577E9374.2050803@levkowetz.com> Date: Thu, 07 Jul 2016 19:37:56 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Garri Djavadyan , tools-discuss@ietf.org References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Jx24DgtclwMrbKP0pgN0qAVS6tMbOI1JB" X-SA-Exim-Connect-IP: 81.235.150.134 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, g.djavadyan@gmail.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) Archived-At: Subject: Re: [Tools-discuss] Problems with HTML markup in RFC2328 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2016 17:38:13 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Jx24DgtclwMrbKP0pgN0qAVS6tMbOI1JB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Garri, On 2016-07-04 08:57, Garri Djavadyan wrote: > Dear IETF tools support team, >=20 > The links to subsection number anchors are not work on page > https://tools.ietf.org/html/rfc2328, although the links to main section= > number (w/o dots) works as expected. For example, > https://tools.ietf.org/html/rfc2328#section-1.1 This is a limitation of the automatic htmlization script. The formatting= of this RFC is such that the script doesn't recognise the subsection headings as such. Changing the script to recognise this breaks other documents in other ways. The current htmlization tool is based on regula= r expressions; in order to fix this a re-write which parses the document is= probably needed. Thanks for reporting this, and sorry that no quick fix is available. Best regards, Henrik --Jx24DgtclwMrbKP0pgN0qAVS6tMbOI1JB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJXfpN1AAoJEE6bV0uPuxcaCTUP/2kFoUNGt0D0YM/yLKpT4/nS Kxdi5c9SRz3Nu3c8l5cnnot5u9yraXIAC65OJS8oZIXwjWAGJ/jKakh5dcD4sv/3 v04wiG/YCmSiFN8hZ5ARV4UBiNvmwLmNGWRQh9xWLj+3ubayxEcu14XuZ68Gs0bH knYUn7MWNQ7vPkVCB+rK+GGIiuFLuqSclOKdEy7aQfJ6r+YWL6eLrO/x3LC6y2N1 7UMU3tbPYSHq+CD7YKdlJ5IeT5h4jPyAW6f/ojdsmyR94u7O7fMpKGQJ9GJ8FzNx 8sNZvLJXiZFWHVfh45vbrCVxeI1vlskaHOucCanGjsvj7UplNdC3nWoKDs8AUTS+ 4Dm2t4bzprhJfIRpqHDCN4cmz/viULnLcYraepjo1I8fU3nLrPzPaThX4a6s05S7 kUZ8zXS1iHKqP2FS81ZGk0s5k5yGxHRp7BtcL2kINuD2LibruRrwcDudlWg2IS1K vPaywqwW6tOYZ8BFKaGd8umJ1zhGaFYjHewYRIs+G/KM9PQaYClis2tHBwEe4jLJ ZI23B6hIeHYb4KOfKyiiPZDT5nNr6BnyBDI8hpiE93jNztQzW6dq/P2MARXK0gEu xvPGAmd76ojZmGKgIqjZTB1kcM0YBxELhvDGKAoTb28ZBZtK/wOR0qlEYcBkgkXM NdBdlesyAHYvvDp1dXXR =izCQ -----END PGP SIGNATURE----- --Jx24DgtclwMrbKP0pgN0qAVS6tMbOI1JB-- From nobody Wed Jul 13 12:43:20 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9205912D593 for ; Wed, 13 Jul 2016 12:43:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.934 X-Spam-Level: X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zw2mGqbaOXtz for ; Wed, 13 Jul 2016 12:43:16 -0700 (PDT) Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADE4112D580 for ; Wed, 13 Jul 2016 12:43:16 -0700 (PDT) Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-11v.sys.comcast.net with SMTP id NQ1cbyguvlSxsNQ3vbJ53Y; Wed, 13 Jul 2016 19:43:15 +0000 Received: from hobgoblin.ariadne.com ([73.143.237.82]) by comcast with SMTP id NQ3ubguG9yaD6NQ3ubsHWb; Wed, 13 Jul 2016 19:43:15 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u6DJhD3d028562; Wed, 13 Jul 2016 15:43:13 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u6DJhDeT028555; Wed, 13 Jul 2016 15:43:13 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: Michael Richardson In-Reply-To: <27629.1467212717@obiwan.sandelman.ca> (mcr+ietf@sandelman.ca) Sender: worley@ariadne.com (Dale R. Worley) Date: Wed, 13 Jul 2016 15:43:13 -0400 Message-ID: <87bn21xr1q.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfBBVx41yelRPg7qx57VxaB+/TAGsZC+B4iigQEF5nNnOfs/78NnPBhVzBOfv3ZPs1p+e0l5s1dD9HbJ91kPQc8JQDd44jpO0yHRVeZPQUnF0ZRw20I8s TnG1f+jMD8sbdL1gkyqmzVCtJagjb75W0osU5L2L9Ik1E1CmPWib0f0PYCNRlWq2y5yYppWuQre4vX7qD6RccCHZYrt3ALdQs5NzQOHIDFzaIrUct/xWWB/X Archived-At: Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 19:43:18 -0000 Michael Richardson writes: > Is there a suggested LICENSE.txt for internet-drafts repos that live on > github (or elsewhere)? I think the boilerplate of each I-D contains the copyright/licensing information for the I-D. For instance, draft-worley-sipcore-dual-stack-00 includes: Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. So it seems to me that the best approach is to have LICENSE.txt say to see in the contents of each file for the licensing information. Dale From nobody Sat Jul 16 05:02:30 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C865C12D53A for ; Sat, 16 Jul 2016 05:02:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LKhPI3rwwp5D for ; Sat, 16 Jul 2016 05:02:27 -0700 (PDT) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43DCE12D0AB for ; Sat, 16 Jul 2016 05:02:27 -0700 (PDT) Received: by mail-yw0-x22a.google.com with SMTP id i12so123116182ywa.1 for ; Sat, 16 Jul 2016 05:02:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to; bh=9vPq32Jdo4xZgaQVU7Gwe0YsXjkjM6TK1YcK7qIMS7M=; b=S0YITK9GxwTEdrW2TorX+fc3K4qjRWtn5f0GTKLx+A7RC9ReNw7pHJoIcfvEqZ0KTH 2YbNKy4MwZ97apW/BmV/D6CbBg2+1uV5YJ4cFdqs/0PDHL7I8KbPUykE8iXN9ExK3N41 J7h0reSzkS7VOqakoEq3SignvtbaWe97PQVXEHxrJcUOwYsriLj/BNmJvFrOBQO0kcY3 j+aQ7W+xrjsLm5T4iV1md5oaiGed5Ud4PlHurAnH4Hvjo0MvjyobsPW1bVpUUMrFF099 Ik8jzWrrMsYT0DD+JGs7fpiUYVRYF8yeFy0AFiMssTCFVZRdQnc+45iQgxxIT14oH2eg AZ1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=9vPq32Jdo4xZgaQVU7Gwe0YsXjkjM6TK1YcK7qIMS7M=; b=XQd8IImrQu7wwlYcAeAtzBzC0IwPlDDbBJGnsIQlSbQXC86FiHwzAt2yxSL/ITEp84 tlC3q1IuCoKiZY+kZiEK4/26tIxENsGYwaDa/HL6gznMfH58AwVrZe1vK8eYfKFmQ46U 9scfrEWiznFIZrk5oV3d1oWybQPICrXyLb3LH2jfqWrOtkP9Gvef1c+oeSCdaxsMA/QO 9Bv8taWQ+yMQvXeUecWuRBzeKUFj6jV2eBCiCdjkQYUV7QunmBMuj40jKN1dSXCv3P/b n7ISjjKSLB68xxgVm+z563rT9aMxfkjm6NRDPlGHa4xk/hRkSb/CvfC0Rn0iR+bCxsyK taJg== X-Gm-Message-State: ALyK8tIL4it4PYoQ2sF9n50g7rXCbdNv6Mm0vIYT7RnktHbyDbzSNXyFm2kYG0LYJb4lmuT3LfqC+EtgGLuo+w== X-Received: by 10.13.237.68 with SMTP id w65mr6590753ywe.128.1468670546451; Sat, 16 Jul 2016 05:02:26 -0700 (PDT) MIME-Version: 1.0 Sender: barryleiba@gmail.com Received: by 10.83.33.137 with HTTP; Sat, 16 Jul 2016 05:02:26 -0700 (PDT) From: Barry Leiba Date: Sat, 16 Jul 2016 08:02:26 -0400 X-Google-Sender-Auth: YpaE1hbKfgZLyWrL5cmLmRcNyEQ Message-ID: To: Tools Team Discussion Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2016 12:02:29 -0000 The tools agenda doesn't get session-sharing information, and so doesn't show any distinction when two sessions share a room in the same time slot. The session description is truncated, so the reader can't see the information either. Look at Potsdam III on Tuesday morning here: https://datatracker.ietf.org/meeting/96/agenda.txt ...and then compare that with here: https://tools.ietf.org/agenda/96/ I'm concerned that, for example, people who look only at the tools agenda will show up at 10:00 on Tuesday expecting the IMTG BoF, and will be surprised when SLIM starts. Barry From nobody Sat Jul 16 05:05:25 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18B812D54C for ; Sat, 16 Jul 2016 05:05:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMBXWfzakfJY for ; Sat, 16 Jul 2016 05:05:22 -0700 (PDT) Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FBA212B065 for ; Sat, 16 Jul 2016 05:05:22 -0700 (PDT) Received: from dhcp-b1e5.meeting.ietf.org (dhcp-b1e5.meeting.ietf.org [31.133.177.229]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 9272D13A5; Sat, 16 Jul 2016 07:56:54 -0400 (EDT) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_F227D8C9-C932-4A1C-88B5-E9A2F5876719"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Pgp-Agent: GPGMail 2.6b2 From: Tom Pusateri In-Reply-To: Date: Sat, 16 Jul 2016 14:05:18 +0200 Message-Id: References: To: Barry Leiba X-Mailer: Apple Mail (2.3124) Archived-At: Cc: Tools Team Discussion Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2016 12:05:24 -0000 --Apple-Mail=_F227D8C9-C932-4A1C-88B5-E9A2F5876719 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Jul 16, 2016, at 2:02 PM, Barry Leiba = wrote: >=20 > The tools agenda doesn't get session-sharing information, and so > doesn't show any distinction when two sessions share a room in the > same time slot. The session description is truncated, so the reader > can't see the information either. Look at Potsdam III on Tuesday > morning here: >=20 > https://datatracker.ietf.org/meeting/96/agenda.txt >=20 > ...and then compare that with here: >=20 > https://tools.ietf.org/agenda/96/ >=20 > I'm concerned that, for example, people who look only at the tools > agenda will show up at 10:00 on Tuesday expecting the IMTG BoF, and > will be surprised when SLIM starts. >=20 > Barry This affects the iPad grid view as well. The correct thing to do would = be to create two new timeslots (1000-1130, 1130-1230) and not overload a = timeslot. Tom --Apple-Mail=_F227D8C9-C932-4A1C-88B5-E9A2F5876719 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBCAAGBQJXiiL/AAoJEPk0GMVmUuYM4C0IAJkRQKfa+Q8WCMSCqidJF4gK Eq2fPnAvOYYikGhsW/aAVGiAB9vDmVHCspDFOrNutAsqReuo4zI/SvlmHjCQX+da Syw2u+odg4knb7RkeK7AjVAVoC1dfkKt7DEMDOn+2ByipT2C7T8zKIgoOpCeYMcm XnB5hQfm4dAduJrOdHxjPzueS18or1/6s6Wk9u5XccWWggxJZKlw24bBnApfD+Q+ Lyt7jWgzkHMepe+JZNpwRST1KZo4IJLbk/n5Jj1NM43ZAJPx8JpkTwC7VikVxByv QugVanMlfPg5yoomRoIsb4j46KwQgW0GvP/7oFJlF1gGdQwd/gwYhti5d901Xp0= =BdaD -----END PGP SIGNATURE----- --Apple-Mail=_F227D8C9-C932-4A1C-88B5-E9A2F5876719-- From nobody Sat Jul 16 05:07:33 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7E4412D0AB for ; Sat, 16 Jul 2016 05:07:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6aoI8uDcgNfS for ; Sat, 16 Jul 2016 05:07:30 -0700 (PDT) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7178512D0A1 for ; Sat, 16 Jul 2016 05:07:30 -0700 (PDT) Received: by mail-yw0-x22a.google.com with SMTP id w127so125010166ywf.3 for ; Sat, 16 Jul 2016 05:07:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=easz8jhKCEKGQubrpThJKfD+R09wqY/k8lUVu2uWo+E=; b=OTSAzFmRJ0FEuSfeIAs63qZVQbrhTNQOhWCAR+Cm7WqN1XrrjFtVkANNwcz/a3MN3Z 9zrntzlAbIHN7MH0YiXZN6lihOsTCfUKSWYAiqBjW2TxAu3CUrOSIxJ2Ie8+WQ1F8HSK 7e6ZHBKA5NHh3XlpVUNpRQSnP5ej0sML1Wk8Pl5x6MA4crQtCHGpil1npF7+y75p1JYW O2pA6AErKeQKnHECspvA1dd8fZ+WgBfoRgRc6BE41D0SKfyr+lENvmqUi+h1orJIJuht Whb1dWPD8FL/x7+zPgBz5/rOSO+3zQnmaaGIWFp7Y7iaBxePmHeS1VAPRwaZQEkAm9W3 0vhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=easz8jhKCEKGQubrpThJKfD+R09wqY/k8lUVu2uWo+E=; b=ObuEc95RnBki0SHBfA6VMLS97GFm9MxVPa5gcrOEjiYbtD8L1pRhFEujhuHNqew3CL 6sGxn7eHfUm5QyHsQbbp1174B8AYNc3B6nmex92E8mp4tD2Cv0qn1sypcCTENCy8O4Qv 59Gd8rHtGRzmMVmru3flFddDAUGJbOC8LmUOpZE+pXbAvqncLw1d6smH5S6eP54ts7xv rXTcPx2GXQRT48mQn02hRn9/aBHRw5woAe1PK4281rxdQzd/a5UwdyFiiCrVVyJktOWv F3Mzis0ziBZZS9F9rAtfrXrZUGiOyOLtUhjan14T1tgD+ShSQthnucgHx5CgegbX+PaM jjxA== X-Gm-Message-State: ALyK8tIkGhx5j6/cRSY/vUYm5S50vbIk0rImcTLrwpwD7LYaJFxg3fTRacTCuHKF3L/csPzznI1uLFREepaRWw== X-Received: by 10.129.104.9 with SMTP id d9mr17826314ywc.110.1468670849759; Sat, 16 Jul 2016 05:07:29 -0700 (PDT) MIME-Version: 1.0 Sender: barryleiba@gmail.com Received: by 10.83.33.137 with HTTP; Sat, 16 Jul 2016 05:07:28 -0700 (PDT) In-Reply-To: References: From: Barry Leiba Date: Sat, 16 Jul 2016 08:07:28 -0400 X-Google-Sender-Auth: oikvfe86K9XHNZ0mSO_XohkYjaA Message-ID: To: Tom Pusateri Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Tools Team Discussion Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2016 12:07:32 -0000 We can ask the Secretariat whether it's possible, with the tooling they have, to have overlapping time slots (1000-12:30, 1000-1130, 1130-1230, all in the system). Barry On Sat, Jul 16, 2016 at 8:05 AM, Tom Pusateri wrote: > >> On Jul 16, 2016, at 2:02 PM, Barry Leiba wrote: >> >> The tools agenda doesn't get session-sharing information, and so >> doesn't show any distinction when two sessions share a room in the >> same time slot. The session description is truncated, so the reader >> can't see the information either. Look at Potsdam III on Tuesday >> morning here: >> >> https://datatracker.ietf.org/meeting/96/agenda.txt >> >> ...and then compare that with here: >> >> https://tools.ietf.org/agenda/96/ >> >> I'm concerned that, for example, people who look only at the tools >> agenda will show up at 10:00 on Tuesday expecting the IMTG BoF, and >> will be surprised when SLIM starts. >> >> Barry > > > This affects the iPad grid view as well. The correct thing to do would be to create two new timeslots (1000-1130, 1130-1230) and not overload a timeslot. > > Tom From nobody Sun Jul 17 03:08:00 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB54412D558 for ; Sun, 17 Jul 2016 03:07:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.9 X-Spam-Level: X-Spam-Status: No, score=-106.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IzmrtjYOhT3D for ; Sun, 17 Jul 2016 03:07:57 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EC1712D507 for ; Sun, 17 Jul 2016 03:07:57 -0700 (PDT) Received: from [2001:67c:370:136:5041:2c13:6d7d:d80e] (port=60713) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1bOizM-0006P3-6e; Sun, 17 Jul 2016 03:07:56 -0700 Message-ID: <578B58FA.8040400@levkowetz.com> Date: Sun, 17 Jul 2016 12:07:54 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Barry Leiba , Tools Team Discussion References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="A2rOF5eFkHsC8fQVaqTWlulvkSbxJM21W" X-SA-Exim-Connect-IP: 2001:67c:370:136:5041:2c13:6d7d:d80e X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, barryleiba@computer.org X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) Archived-At: Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2016 10:07:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --A2rOF5eFkHsC8fQVaqTWlulvkSbxJM21W Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Barry, On 2016-07-16 14:02, Barry Leiba wrote: > The tools agenda doesn't get session-sharing information, and so > doesn't show any distinction when two sessions share a room in the > same time slot. The session description is truncated, so the reader > can't see the information either. Look at Potsdam III on Tuesday > morning here: >=20 > https://datatracker.ietf.org/meeting/96/agenda.txt >=20 > ...and then compare that with here: >=20 > https://tools.ietf.org/agenda/96/ >=20 > I'm concerned that, for example, people who look only at the tools > agenda will show up at 10:00 on Tuesday expecting the IMTG BoF, and > will be surprised when SLIM starts. I see what you mean. There's a tooltip which pops up with the full text, but that's not immediately noticeable. I decided on a text width cut-off in order to not make text extend too far to the right; maybe I could fold the comment text instead. I'll see what I can do. Best regards, Henrik --A2rOF5eFkHsC8fQVaqTWlulvkSbxJM21W Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJXi1j6AAoJEE6bV0uPuxca6YgP/16c9fTXyizh+XblEVtGpk2p OAx0AuvipYiGxgLgrXC7y2nSekm+7hV1CefF4jYciGI+NVeXSjjXCinA/PcMYTgq jNieTwKXYoNigcZkSg3ZBtMcwlkMkP/Fq3o8OQzUnd639PbHIpWV9UGvCegRa00y 4VaIqN6vzl639hLk5yGngEiWfRgPSICoETRc3luAgJ4o2JtDPPsUdMv12Uz63NgO zjYJl01UF3H4zqQoHtiCH3Ctgpa+nx3/EFjpJsZH66SJl73mPAy28GonAf7VQxp9 mW4d48W0c5DzXE48Z/FSaE5/JoRTR6KbGfcByNC2VMOl6CXozgdUoMzGWIQ1oxd3 g0nqnuhHHT0EmjP1QIFimBHUTF9Apy5POCFgGzJcr4j1lkQ9qYKOK5GXxGo7q32Y mPOohAB80VbHGy9dkjXilxagqY27UGWyx2WehrA8piFZ+aOVIHMBgZaRqEDgsZo/ QgQmGnDeAcWJ+8+JfC9KTT202XwOjw/O1V9dOTVJdDS9bDiv+YNSS79kX6xXNKXW 8xnXeTFcAT+JXDrx9sfhJQ5b+VfJ4goeo0W+S+MkbB3S653yPTrCTGsN2NZFfgmM FpR5hp7dKyxf7IQQcqGqN1FQpXg2d/DQzQWSBLcmg/5NF8SuKi7dM9B1Ms5YpyqA rS2+vN95t87C9UkctOZ1 =fJL1 -----END PGP SIGNATURE----- --A2rOF5eFkHsC8fQVaqTWlulvkSbxJM21W-- From nobody Sun Jul 17 06:02:29 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 617F412D08E for ; Sun, 17 Jul 2016 06:02:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.188 X-Spam-Level: X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqc2tht8ueVG for ; Sun, 17 Jul 2016 06:02:26 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B75912B05E for ; Sun, 17 Jul 2016 06:02:24 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E60892015D; Sun, 17 Jul 2016 09:11:43 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EA585638D1; Sun, 17 Jul 2016 09:02:22 -0400 (EDT) From: Michael Richardson To: Barry Leiba In-Reply-To: References: X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Cc: Tools Team Discussion Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2016 13:02:28 -0000 --=-=-= Content-Type: text/plain Barry Leiba wrote: > We can ask the Secretariat whether it's possible, with the tooling they > have, to have overlapping time slots (1000-12:30, 1000-1130, 1130-1230, > all in the system). Yes, as originally built, timeslots within a small delta (10 minutes I think was the default), can be combined into bigger slots for longer sessions. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBV4uB3ICLcPvd0N1lAQL0Cwf9FsyqG2huh5uBYXnolEr0OYtpKu3Cjpsc TLae0ZUXZkhOqSUl9+Uh5cKaf1KZiKcF4aJx2Ym+mI3kZaKDH3LQVp3NmEiH58E+ 5/iLg+PoZqlU5I27EmrJFtREnkqm2Wz01vzZgjUDpq0QhNTbPKHI1Ff1FEQ3eHxq wbcHPPlGUgcr07zInxo4CD8+a7/xgwSp5fGlkFGhmLngnjz3iMGghjZnPJr4/GJ9 LeaAWqIXyBO10frPwv99fYlhpCSiWnJXwl3s+eghmV8/2+zKnYqceVLVlXq9Kfch wzRHsP5O656KhYYzlPWbFkM92JBiN1ttCiFChx6mcHaPdiYwweSrFg== =ceXX -----END PGP SIGNATURE----- --=-=-=-- From nobody Sun Jul 17 08:54:32 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2EA212D0AC for ; Sun, 17 Jul 2016 08:54:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2P30NHCH_UQ for ; Sun, 17 Jul 2016 08:54:29 -0700 (PDT) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2663B12B007 for ; Sun, 17 Jul 2016 08:54:29 -0700 (PDT) Received: by mail-yw0-x231.google.com with SMTP id l125so141512147ywb.2 for ; Sun, 17 Jul 2016 08:54:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=gv/X4LnXgubNt0xMIiFRL309pA01xaMZQAPFyEQ+L9Q=; b=nykhDA3lVdm6Ca0CdU9N4BAuhtb8maVfislrCO48wH7I+J9UyGh4URB+bc40LgKD+C J6U6aY/TX8eF5O6e/1IdE6yDGwZl+iDguvJyA267qiPjV+jRTq5QY1H/eJdbgK7JJMft t0QSAKu4daJdHg82caPmEkv8u/BANU8ifoC7LmRCV/S6pJRdLj45CTDVuNugyvzgsYDk 4JgnIhIGgXRUUaOSm3FaX3r0tXMcBVbtslKvP7x2wmbv3grpnUMOxmqg5mhO8cBMueH7 zY4EXOlAsO/EAj/XhFSDBR3cNcVesgPKvTM/g2kHzhqR9lWV1Bxhs3qWruP9wwMZFlaj z+aQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=gv/X4LnXgubNt0xMIiFRL309pA01xaMZQAPFyEQ+L9Q=; b=N/whCwhXv0jM534hwP98fhmLoC3a46Zhnhr4UNs9JL50LAngeGVsQ4G9iqbHHCX4jk pBAoxcv+W36hxBRszqZUtwy5g4cIOQrUuDlL/+Q3HOB6qrvPUYp8ZKI9A1Z/Kdv+FxTz B0RasUEwQDzC88LOEtOk9lFqiNrjHd1mzcYNn/QT8lI12qaHA6Z3C/3dbHQQ0jbRbf+P xtMXaFzZARaeg4TrfNDAH8IZ5VhLRuJKQmSLuf55wrE5aOJcbcnws3mPFvTp31TFqXDz bPnFHLZEAw4kOxCVUfOb8PSnbbmGWRMHy0WU9E/sdA/jol3c4uxrbdPlsMXNSeDZzc6b L/nQ== X-Gm-Message-State: ALyK8tKwhrRMXMG+8bfFTF8DjgMEAQrxAYRKDUBmL8WD49d2QwpMRVJcmveFt18jipDreuO/gIN2ugTzS6q1zg== X-Received: by 10.37.78.133 with SMTP id c127mr19828267ybb.102.1468770868314; Sun, 17 Jul 2016 08:54:28 -0700 (PDT) MIME-Version: 1.0 Sender: barryleiba@gmail.com Received: by 10.83.33.137 with HTTP; Sun, 17 Jul 2016 08:54:27 -0700 (PDT) In-Reply-To: <24063.1468760542@obiwan.sandelman.ca> References: <24063.1468760542@obiwan.sandelman.ca> From: Barry Leiba Date: Sun, 17 Jul 2016 11:54:27 -0400 X-Google-Sender-Auth: jgxR5GVTV9LGmIMdh9L_BR_j1oY Message-ID: To: Michael Richardson Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Tools Team Discussion Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2016 15:54:31 -0000 > > We can ask the Secretariat whether it's possible, with the tooling they > > have, to have overlapping time slots (1000-12:30, 1000-1130, 1130-1230, > > all in the system). > > Yes, as originally built, timeslots within a small delta (10 minutes I think > was the default), can be combined into bigger slots for longer sessions. Ah, in other words, the right way to do it is not to split a long session, but to combine two shorter ones. Make the sessions be 10:00-11:30 and 11:30-12:30, and then schedule all the *other* groups in both. Barry From nobody Sun Jul 17 11:26:47 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8488912D504 for ; Sun, 17 Jul 2016 11:26:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7RYfjiAN4us for ; Sun, 17 Jul 2016 11:26:44 -0700 (PDT) Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD1312D508 for ; Sun, 17 Jul 2016 11:26:44 -0700 (PDT) Received: from butte-1844.fritz.box (p4FF77294.dip0.t-ipconnect.de [79.247.114.148]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 8B7221556; Sun, 17 Jul 2016 14:18:10 -0400 (EDT) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_AFC99079-E998-412E-8B1A-0EB11E149909"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Pgp-Agent: GPGMail 2.6b2 From: Tom Pusateri In-Reply-To: Date: Sun, 17 Jul 2016 20:26:37 +0200 Message-Id: <75571E58-452B-49CB-A746-2F2C085F1B88@bangj.com> References: <24063.1468760542@obiwan.sandelman.ca> To: Barry Leiba X-Mailer: Apple Mail (2.3124) Archived-At: Cc: Michael Richardson , Tools Team Discussion Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2016 18:26:46 -0000 --Apple-Mail=_AFC99079-E998-412E-8B1A-0EB11E149909 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jul 17, 2016, at 5:54 PM, Barry Leiba = wrote: >=20 >>> We can ask the Secretariat whether it's possible, with the tooling = they >>> have, to have overlapping time slots (1000-12:30, 1000-1130, = 1130-1230, >>> all in the system). >>=20 >> Yes, as originally built, timeslots within a small delta (10 minutes = I think >> was the default), can be combined into bigger slots for longer = sessions. >=20 > Ah, in other words, the right way to do it is not to split a long > session, but to combine two shorter ones. Make the sessions be > 10:00-11:30 and 11:30-12:30, and then schedule all the *other* groups > in both. >=20 > Barry To me, spanning multiple sessions makes the problem worse not better. I would like to see the scheduler handle arbitrary start and duration = times. Speaking with Robert and Henrik, it doesn=E2=80=99t sound like = that is going to happen. But everything else requires special case = handling by the various tools. Maybe the scheduling tool could handle splitting a session in two? = That=E2=80=99s somewhat of a tractable problem and would handle most of = the use cases where multiple working groups are meeting sequentially. Tom --Apple-Mail=_AFC99079-E998-412E-8B1A-0EB11E149909 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBCAAGBQJXi83dAAoJEPk0GMVmUuYMbDAH/RmdqXgl/Juy8iK5wbYq6iWZ X5bNSuM5eAfoBcQgpSa/+zgA1kZ5Dw4+DfR9DfLRDajYJpIggyo13+ULDXLWcvio nLM/WLPyExY1iLuVVpMwsm9h3bX7sWe3vd7puO+FDUpKj35Dt8jQQGcww+5HW+ye xs/h8cdgP/6gkWPPbP26t3LpWBPZ+lpfrgVTNC0XYy/KWNRxE62leXNMtBf9Ps9A SKzxKWUDkwsLdt32D8rWj+aDhoHAnD49/pMXp4qfGqNlLtf+7NET6szBdUDRmp+U xwN4svh5GGCe7QsZxtuUQxPKH4dLpX4cN/ZBgtWd4sYpZ4xQVCq+ECWM9hFiCV8= =YpXW -----END PGP SIGNATURE----- --Apple-Mail=_AFC99079-E998-412E-8B1A-0EB11E149909-- From nobody Sun Jul 17 15:02:28 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C1612D0D8 for ; Sun, 17 Jul 2016 15:02:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.188 X-Spam-Level: X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ADAU2SQ2pZOe for ; Sun, 17 Jul 2016 15:02:25 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A56612D0AD for ; Sun, 17 Jul 2016 15:02:25 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8B5DD200A7; Sun, 17 Jul 2016 18:11:46 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 49A20638D1; Sun, 17 Jul 2016 18:02:24 -0400 (EDT) From: Michael Richardson To: Barry Leiba In-Reply-To: References: <24063.1468760542@obiwan.sandelman.ca> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Date: Sun, 17 Jul 2016 18:02:24 -0400 Message-ID: <10105.1468792944@obiwan.sandelman.ca> Archived-At: Cc: Tools Team Discussion Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2016 22:02:27 -0000 Barry Leiba wrote: >> they > have, to have overlapping time slots (1000-12:30, 1000-1130, >> 1130-1230, > all in the system). >> >> Yes, as originally built, timeslots within a small delta (10 minutes I >> think was the default), can be combined into bigger slots for longer >> sessions. > Ah, in other words, the right way to do it is not to split a long > session, but to combine two shorter ones. Make the sessions be > 10:00-11:30 and 11:30-12:30, and then schedule all the *other* groups > in both. Yes, exactly. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ From nobody Mon Jul 18 02:27:00 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC46D12D641 for ; Mon, 18 Jul 2016 02:26:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.188 X-Spam-Level: X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4UvZoa0skyhB for ; Mon, 18 Jul 2016 02:26:55 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A002412D5B2 for ; Mon, 18 Jul 2016 02:26:24 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 78745200A7; Mon, 18 Jul 2016 05:35:47 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 94747638D1; Mon, 18 Jul 2016 05:26:23 -0400 (EDT) From: Michael Richardson To: Tom Pusateri In-Reply-To: <75571E58-452B-49CB-A746-2F2C085F1B88@bangj.com> References: <24063.1468760542@obiwan.sandelman.ca> <75571E58-452B-49CB-A746-2F2C085F1B88@bangj.com> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Cc: Barry Leiba , Tools Team Discussion Subject: Re: [Tools-discuss] Tools agenda error when sessions are shared X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 09:26:58 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Tom Pusateri wrote: > I would like to see the scheduler handle arbitrary start and duration > times. Speaking with Robert and Henrik, it doesn=E2=80=99t sound like= that is > going to happen. But everything else requires special case handling by > the various tools. Why it is good to do this? It makes it very hard (and disruptive) if people are entering and exiting rooms at random times. > Maybe the scheduling tool could handle splitting a session in two? yes, so perhaps it could better handle the splitting of a slot into two slots, and mark all the sessions as spanning the slot. > That=E2=80=99s somewhat of a tractable problem and would handle most = of the use > cases where multiple working groups are meeting sequentially. It sure sounds to me like we should simply have more slots that are shorter. I've suggest just defining 1 hour slots throughout the day, and when WGs wa= nt 2hrs, they get two slots. I've suggested that every WG get a 1hr slot th= at satisfies the maximum number of conflicts, and then additional time is added after everyone has been scheduled. Depending upon how it is done this could have some affect upon how lunch is scheduled; it could also provide some relief on lunch rush if not everyone takes lunch at the same time. Some arrangements could also be profoundly negative to organizing lunch meetings, and might be very negative towards a= ctually getting lunch for some people. =2D- Michael Richardson , Sandelman Software Works -=3D IPv6 IoT consulting =3D- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBV4ygvICLcPvd0N1lAQJZLggAonr5RUl71D2eDwkSYWWqaM7R81RpxhxF MKHZJs6TpZNB0/UY9aPNQAbn5ioDCLfX946G5ppb4MqySSxSkWmpKOQs1Hnib9rx sRo0fa5ySdz1bgfmSWcjsjlbMEH//erydJk0cTd4Y2M6CdMAutLCqTRXvuLmuaUk Mc5Bkbjbo436sLtlFft1140IlLV2U+BxrPRZ+RJ/nLz3qfcDi1ZtMIgd/i+zdSlj pvg6a8ejlIXz/Pnq6yeJfYINGnMzKHB/MxQ9eNeQ4x1IlXonDASFGYFrr77l+ICe 9/JWEvxWrImipdk1pRAHyQ8iRdIzB0iaYHlUU+WuYYi9biE7nrGOug== =i4sH -----END PGP SIGNATURE----- --=-=-=-- From nobody Mon Jul 18 06:56:35 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D15912DFF8 for ; Mon, 18 Jul 2016 06:56:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jitsi-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_m-1Sv5ASZY for ; Mon, 18 Jul 2016 06:56:28 -0700 (PDT) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 964B212DD5F for ; Mon, 18 Jul 2016 06:30:48 -0700 (PDT) Received: by mail-yw0-x22a.google.com with SMTP id c124so32189134ywd.3 for ; Mon, 18 Jul 2016 06:30:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jitsi-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=efVbNGYZZeO3SetSd5ZZvt/IWqYvX83u6CplqkTlJo0=; b=uMO9rOyGxKTyhr1QpUjxGxNEA2XGHy8wS3Av5kyq65eRMomaBG7x7oc5hfXZuFg6v6 9aFhk1FM5HScq1kX9iD/MJaldFEfHcwVYl8zRE4EtIp4qRTZlvDeph6dIk+7+RDnLYmU KZy0aPLnY/9fz2qbjt4I9FxdHo9utA/XJVNL4ACkZED5iWSIdfqJujJKQ1XbmMClKpdl SiNe57yHxc/PJGtmxJU+fhsYLRV3cCC4o2wZzR6n9JaBQuFUH/L9WX0dOa2XIYloGe4K mk6/lI3fo3IM5yBZjFdqteqRWtLVmOvqUj1Hmvl1gsSQ5CH1+a66cyjsnm/Jg9PcgVD0 q8bQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=efVbNGYZZeO3SetSd5ZZvt/IWqYvX83u6CplqkTlJo0=; b=MQWNLrJRu+3npyJ9D3J0+E11SmUo/0u7POhekzMRxgOMLFLZXFKZaAvjSDMzLdw/WS OHxXsFdsHqRIJESsX5xWu5pjTLcjKwMlFsgsdwqDKznf6ldb2RXhdJYW0cdqoLqNqZZX YtOBtWxKynvadI3XX5IeMB4HrDETEl2eh5AWt6mKkk9H4dI6+oCy0MhYF6LKI54rO2KE vqlno/291smm9x5o3wBeJnXHk2OGGHMIyzz3thIAM6XMnUBEB4u/bFMXgvdGfqc0FoXa UDnpMrYu/RvH1Aw2jDQGxX3rKhhx/sKNjFimOsGn1gOV0bhsQSvPS+fjOo+7qPHrkZ7C xljg== X-Gm-Message-State: ALyK8tJrMvNqyUGjeZK8Bzbz9b8o/isTL1dBfetNa92eRNMxXOVS+9h6HaJkDCYZ0jTqhw== X-Received: by 10.129.32.65 with SMTP id g62mr24972859ywg.126.1468848647759; Mon, 18 Jul 2016 06:30:47 -0700 (PDT) Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com. [209.85.161.174]) by smtp.gmail.com with ESMTPSA id t125sm3570741ywd.0.2016.07.18.06.30.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 06:30:47 -0700 (PDT) Received: by mail-yw0-f174.google.com with SMTP id i12so158344911ywa.1 for ; Mon, 18 Jul 2016 06:30:47 -0700 (PDT) X-Received: by 10.37.16.66 with SMTP id 63mr17605109ybq.29.1468848647275; Mon, 18 Jul 2016 06:30:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.83.17.204 with HTTP; Mon, 18 Jul 2016 06:30:27 -0700 (PDT) In-Reply-To: <31989.1467205298@obiwan.sandelman.ca> References: <31989.1467205298@obiwan.sandelman.ca> From: Emil Ivov Date: Mon, 18 Jul 2016 15:30:27 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Michael Richardson Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: tools-discuss Subject: Re: [Tools-discuss] etherpad in jitsi X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 13:56:33 -0000 Hey Michael, This one slipped through the cracks On Wed, Jun 29, 2016 at 3:01 PM, Michael Richardson wrote: > a) Is the etherpad in the jitsi accessible from outside JITSI? It is but not in an optimal way. Your conference pad would look something like this: https://jitsi.tools.ietf.org/etherpad/p/fa823d4ff3fe46e2b91d2be6a283fcb2 The part after "p" is generated in a random way for every new conference. > b) it's not the etherpad from etherpad.tools.ietf.org... could it be? Impossible is nothing ;). More below > c) could it persist across uses of the same room? At least, could it > persist for an hour or two, in case everyone gets disconnected, > and so we can capture it. Pads are removed every 6 hours. The reason you are not finding them is because when a new conference is created (even if it uses the name of a previous one) a new random pad name is generated. This is primarily meant for privacy reasons. I guess in IETF's case we can make sure we always use a pad name that corresponds to that of the conference. Something like: http://etherpad.tools.ietf.org:9000/p/rtcweb Would this work? We should meetup while in Berlin :) Emil From nobody Mon Jul 18 09:22:28 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAB212DACD for ; Mon, 18 Jul 2016 09:22:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.187 X-Spam-Level: X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdPoTJGxdGu8 for ; Mon, 18 Jul 2016 09:22:18 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71F5412DA8F for ; Mon, 18 Jul 2016 09:22:18 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 86679200A7; Mon, 18 Jul 2016 12:31:42 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B11F2638D1; Mon, 18 Jul 2016 12:22:17 -0400 (EDT) From: Michael Richardson To: Emil Ivov In-Reply-To: References: <31989.1467205298@obiwan.sandelman.ca> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Date: Mon, 18 Jul 2016 12:22:17 -0400 Message-ID: <20981.1468858937@obiwan.sandelman.ca> Archived-At: Cc: tools-discuss Subject: Re: [Tools-discuss] etherpad in jitsi X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 16:22:20 -0000 Emil Ivov wrote: > It is but not in an optimal way. Your conference pad would look > something like this: > https://jitsi.tools.ietf.org/etherpad/p/fa823d4ff3fe46e2b91d2be6a283fcb2 Maybe this URL could be available somewhere, as it might help some who are participating in a room. I.e. multiple people in a room with a single A/V, but they want to edit seperately... >> c) could it persist across uses of the same room? At least, could it >> persist for an hour or two, in case everyone gets disconnected, and so >> we can capture it. > Pads are removed every 6 hours. The reason you are not finding them is > because when a new conference is created (even if it uses the name of a > previous one) a new random pad name is generated. This is primarily > meant for privacy reasons. Good reason... > I guess in IETF's case we can make sure we always use a pad name that > corresponds to that of the conference. Something like: > http://etherpad.tools.ietf.org:9000/p/rtcweb > Would this work? This it would be awesome really! > We should meetup while in Berlin :) okay. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ From nobody Wed Jul 20 04:52:52 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D683612DB80 for ; Wed, 20 Jul 2016 04:52:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.002 X-Spam-Level: X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=kingsmountain.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YcWP0BKKbri2 for ; Wed, 20 Jul 2016 04:52:49 -0700 (PDT) Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by ietfa.amsl.com (Postfix) with SMTP id 727F712DB71 for ; Wed, 20 Jul 2016 04:52:48 -0700 (PDT) Received: (qmail 12929 invoked by uid 0); 20 Jul 2016 11:52:48 -0000 Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy4.mail.unifiedlayer.com with SMTP; 20 Jul 2016 11:52:48 -0000 Received: from box514.bluehost.com ([74.220.219.114]) by CMOut01 with id Lzsj1t00l2UhLwi01zsnvt; Wed, 20 Jul 2016 05:52:47 -0600 X-Authority-Analysis: v=2.1 cv=AL9Ak13q c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=NEAV23lmAAAA:8 a=IkcTkHD0fZMA:10 a=XYUc-DgfXtMA:10 a=cAmyUtKerLwA:10 a=48vgC7mUAAAA:8 a=ieNpE_y6AAAA:8 a=SSmOFEACAAAA:8 a=1Dj60IAEMv-XCBDv_b4A:9 a=UcyWouI77zYxtAOY:21 a=xM0v7T-wi30i-Gvo:21 a=QEXdDO2ut3YA:10 a=Bn2pgwyD2vrAyMmN8A2t:22 a=w1C3t2QeGrPiZgrLijVG:22 a=lOZzU2MLX5qQKtuoMSD9:22 a=zjWhRoSqWz9hl55Hdlzg:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default; h=MIME-Version:Content-Type:Subject:To:From: Message-ID:Date; bh=/Cr/14j5xZSWD8TgxlJReMsWDR7j6By5uQNE3vJW7U4=; b=dLKJSTWk8 xRodUUDCTalbF3nOM2h7o/LM5+eZczUb+l8Qxhej6GJyjQU4vI3dHSE8AFET/Pi959Rh29VLuVm8j PNiCFmzwtsfl9DUUeFrAJM/hYuK8WjJ6c68tOgCMSf; Received: from [127.0.0.1] (port=43980 helo=box514.bluehost.com) by box514.bluehost.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.86_2) (envelope-from ) id 1bPq3R-0008MM-43 for tools-discuss@ietf.org; Wed, 20 Jul 2016 05:52:45 -0600 Received: from 31.133.176.206 ([31.133.176.206]) by box514.bluehost.com (Horde Framework) with HTTP; Wed, 20 Jul 2016 05:52:39 -0600 Date: Wed, 20 Jul 2016 05:52:39 -0600 Message-ID: <20160720055239.Horde.tPCB8LMdkdBZg5rwwvoi4MP@box514.bluehost.com> From: jeff.hodges@kingsmountain.com To: IETF Tools List User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline X-Identified-User: {:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:program running on server} X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box514.bluehost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - kingsmountain.com X-Source-IP: 127.0.0.1 X-Exim-ID: 1bPq3R-0008MM-43 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (box514.bluehost.com) [127.0.0.1]:43980 X-Source-Auth: jeff.hodges@kingsmountain.com X-Email-Count: 0 X-Source-Cap: a2luZ3Ntb3U7a2luZ3Ntb3U7Ym94NTE0LmJsdWVob3N0LmNvbQ== Archived-At: Subject: Re: [Tools-discuss] integrating working group mailing lists with github.com? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 11:52:51 -0000 it would be nice to chat with ietf-tools folks, while here at IETF-96 berlin, about the below [ though I'm unsure who exactly to buttonhole ]... On 4/22/16, 3:48 PM, "Tools-discuss on behalf of =JeffH" wrote: fyi/fwiw, the W3C has pretty well worked out how to incorp github.com repos into their processes, including mailing lists. Here's some info that we IETF oughta at least look at and perhaps borrow/leverage -- it would be great if we could at least stand up a github-notify-mla instance.. mailing list integration w/github issues & pull requests & pushes, etc https://github.com/dontcallmedom/github-notify-ml/ note that https://github.com/dontcallmedom/github-notify-ml/index.py needs to be installed and configured on a internet-accessible web server, and registered with github.com as a webhook endpoint. how the W3C's instance is config'd is noted here: https://github.com/dontcallmedom/github-notify-ml#w3c-instance see also... Using GitHub for W3C specifications https://www.w3.org/2015/Talks/1217-github-w3c/#/1 From nobody Wed Jul 20 06:05:59 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 178C012D650 for ; Wed, 20 Jul 2016 06:05:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jitsi-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sf9WQlCZPqOK for ; Wed, 20 Jul 2016 06:05:55 -0700 (PDT) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE82412DBE2 for ; Wed, 20 Jul 2016 06:05:53 -0700 (PDT) Received: by mail-yw0-x22d.google.com with SMTP id u134so43854825ywg.3 for ; Wed, 20 Jul 2016 06:05:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jitsi-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=XMunP9P8QabTTtJMscDx3YEpGD4EfvhlYwT4re9Wo2A=; b=QVocC5QOKueTSfxLhijmLwc0OAABM+CHKLhSX6DDz9lsa89ZHuB3hQ7wu8SLqT5kIq cqSGIzML2eDtUkW0MYlgZwQSMrzPK4CIMjaQHq9bSq0owZL86UIYlJnijghxAp9qOViG vffxSLBbh6VbKHQcC0FKfkFaoqAKKD82QmmcQ7IqTZ3WHaNkO/9TpPM8UNvYPJRMuxGi azHgxApcYld2EHLL1LGg+GXNusrJMpJlLgtkE1/ZJ4e6qTYZvT1NtLrzHR0maOObL70L 0f2iT5HG6WFEjBhDABmWqNUEjAq0N1iL9msMJHT82EunT19oUjWIX42TD7TrSAMz6nLW tg0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=XMunP9P8QabTTtJMscDx3YEpGD4EfvhlYwT4re9Wo2A=; b=dvzYddVHEXbVVD/2D/BOl7p6foNPZXplloFcmqPtZM6jPty5LQofDctwUY6N/c8Lh8 rtmV899dfmxKUtQ5Z8hzQjEH2tvh6LsxkEbuPDMKA7srlMRiFTSx+/8/lZHMM3yewvQX CwncgXTzrRD6eD6OrU8Ks3ljSqoSaRODbu48L5vla3X0aGtyT/Fh6lnLMASPu5zEIqF3 kixOcWCQxi1sg4dOhlDq0x8l+6or3LzNlD+N7fPv89Au93Ge59OlpTLNmcIn+gH6ZQNk uxsXfqvg7trcpCZBrd589qOOKfagOqjJYtzU591pOjCHVE9qqRPLyemIYWQruqESfrij Z/fQ== X-Gm-Message-State: ALyK8tIf/3gwt6Y2D8Tic4glIWVFxWneQWNqzwmryRH8EVfUrqOC72wgdChXCYivoEc5nA== X-Received: by 10.129.84.193 with SMTP id i184mr28714906ywb.285.1469019952869; Wed, 20 Jul 2016 06:05:52 -0700 (PDT) Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com. [209.85.161.174]) by smtp.gmail.com with ESMTPSA id m189sm960596ywf.39.2016.07.20.06.05.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 06:05:52 -0700 (PDT) Received: by mail-yw0-f174.google.com with SMTP id j12so37385839ywb.2 for ; Wed, 20 Jul 2016 06:05:51 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.129.145.10 with SMTP id i10mr24693639ywg.263.1469019951672; Wed, 20 Jul 2016 06:05:51 -0700 (PDT) Received: by 10.83.17.204 with HTTP; Wed, 20 Jul 2016 06:05:51 -0700 (PDT) In-Reply-To: <20981.1468858937@obiwan.sandelman.ca> References: <31989.1467205298@obiwan.sandelman.ca> <20981.1468858937@obiwan.sandelman.ca> Date: Wed, 20 Jul 2016 15:05:51 +0200 X-Gmail-Original-Message-ID: Message-ID: From: Emil Ivov To: Michael Richardson Content-Type: multipart/alternative; boundary=94eb2c0929e06379dd053810dca5 Archived-At: Cc: tools-discuss Subject: Re: [Tools-discuss] etherpad in jitsi X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 13:05:58 -0000 --94eb2c0929e06379dd053810dca5 Content-Type: text/plain; charset=UTF-8 Done! The etherpad is now ietf's and the pads have the same name as the Jitsi Meet conference On Monday, 18 July 2016, Michael Richardson wrote: > Emil Ivov > wrote: > > It is but not in an optimal way. Your conference pad would look > > something like this: > > > > https://jitsi.tools.ietf.org/etherpad/p/fa823d4ff3fe46e2b91d2be6a283fcb2 > > Maybe this URL could be available somewhere, as it might help some who are > participating in a room. I.e. multiple people in a room with a single A/V, > but they want to edit seperately... > > >> c) could it persist across uses of the same room? At least, could > it > >> persist for an hour or two, in case everyone gets disconnected, and > so > >> we can capture it. > > > Pads are removed every 6 hours. The reason you are not finding them > is > > because when a new conference is created (even if it uses the name > of a > > previous one) a new random pad name is generated. This is primarily > > meant for privacy reasons. > > Good reason... > > > I guess in IETF's case we can make sure we always use a pad name that > > corresponds to that of the conference. Something like: > > http://etherpad.tools.ietf.org:9000/p/rtcweb > > > Would this work? > > This it would be awesome really! > > > We should meetup while in Berlin :) > > okay. > > -- > ] Never tell me the odds! | ipv6 mesh > networks [ > ] Michael Richardson, Sandelman Software Works | network > architect [ > ] mcr@sandelman.ca http://www.sandelman.ca/ | > ruby on rails [ > > -- sent from my mobile --94eb2c0929e06379dd053810dca5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Done!

The etherpad is now ietf's and the pads have t= he same name as the Jitsi Meet conference

On Monday, 18= July 2016, Michael Richardson <mcr@= sandelman.ca> wrote:
Emil Ivov <= ;emcho@jitsi.org> wrote:
=C2=A0 =C2=A0 > It is but not in an optimal way. Your conference pad wou= ld look
=C2=A0 =C2=A0 > something like this:

=C2=A0 =C2=A0 > https://jitsi.tools.ietf.org= /etherpad/p/fa823d4ff3fe46e2b91d2be6a283fcb2

Maybe this URL could be available somewhere, as it might help some who are<= br> participating in a room.=C2=A0 I.e. multiple people in a room with a single= A/V,
but they want to edit seperately...

=C2=A0 =C2=A0 >> c) could it persist across uses of the same room?=C2= =A0 At least, could it
=C2=A0 =C2=A0 >> persist for an hour or two, in case everyone gets di= sconnected, and so
=C2=A0 =C2=A0 >> we can capture it.

=C2=A0 =C2=A0 > Pads are removed every 6 hours. The reason you are not f= inding them is
=C2=A0 =C2=A0 > because when a new conference is created (even if it use= s the name of a
=C2=A0 =C2=A0 > previous one) a new random pad name is generated. This i= s primarily
=C2=A0 =C2=A0 > meant for privacy reasons.

Good reason...

=C2=A0 =C2=A0 > I guess in IETF's case we can make sure we always us= e a pad name that
=C2=A0 =C2=A0 > corresponds to that of the conference. Something like: =C2=A0 =C2=A0 > http://etherpad.tools.ietf.org:9000/p/rtcweb

=C2=A0 =C2=A0 > Would this work?

This it would be awesome really!

=C2=A0 =C2=A0 > We should meetup while in Berlin :)

okay.

--
]=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Never tell me the o= dds!=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| ipv6 me= sh networks [
]=C2=A0 =C2=A0Michael Richardson, Sandelman Software Works=C2=A0 =C2=A0 =C2= =A0 =C2=A0 | network architect=C2=A0 [
]=C2=A0 =C2=A0 =C2=A0mcr@sandelman.ca=C2=A0 http://www.sandelman.ca/=C2= =A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0ruby on rails=C2=A0 =C2=A0 [



--
sent from my mobile
--94eb2c0929e06379dd053810dca5-- From nobody Wed Jul 20 11:02:30 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2332912D991 for ; Wed, 20 Jul 2016 11:02:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.188 X-Spam-Level: X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oHeOjSrqxP7z for ; Wed, 20 Jul 2016 11:02:16 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE4DD12D9AC for ; Wed, 20 Jul 2016 11:02:15 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id A4BC0200A3; Wed, 20 Jul 2016 14:11:46 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D7D7F638D1; Wed, 20 Jul 2016 14:02:14 -0400 (EDT) From: Michael Richardson To: Emil Ivov In-Reply-To: References: <31989.1467205298@obiwan.sandelman.ca> <20981.1468858937@obiwan.sandelman.ca> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Cc: tools-discuss Subject: Re: [Tools-discuss] etherpad in jitsi X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 18:02:29 -0000 --=-=-= Content-Type: text/plain Emil Ivov wrote: > The etherpad is now ietf's and the pads have the same name as the > Jitsi Meet conference THANK YOU THANK YOU THANK YOU. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBV4+8oICLcPvd0N1lAQK1pggAuSTKcBmU4KIOJJ9xKzNR2inWsuKO5Nxu oHW7XVrz4QUly6viStegg0XQAKr4JD0aW1WDqGEGmWO/9llvK/Jld2nEJC5dDEGw MU7mnXQDJFDYdmVCjgDf2ocIhmO5fupx9BTCOVz9Oc2mS8Zzhb8ryetYv2GxGCUQ +HRN0qeAa5Qugc572sEwhC0CC+grg4o2vxX21ITU7Dl082WbjJXZFp9Sa9on4fxX Xnz0jRZJiIwsZ7DO/8YoqszVu5xB6ofqINsgMg4YN74alF7TOvBXPL8H6cqepOPQ OggC3UwkZ1B/2E/T6lCz+m/BsT8k93wnYE2DU+2BW5B+p8rZqSmx8w== =KE8n -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Jul 20 11:04:22 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4CE112D93B for ; Wed, 20 Jul 2016 11:04:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jitsi-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gwx7CooC4Ozh for ; Wed, 20 Jul 2016 11:04:18 -0700 (PDT) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEB5612B03F for ; Wed, 20 Jul 2016 11:04:17 -0700 (PDT) Received: by mail-yw0-x22c.google.com with SMTP id z8so30681211ywa.1 for ; Wed, 20 Jul 2016 11:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jitsi-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cFXQHC0V8GMLC3OiTZXamaon3JSIk2wO6l+QqVkTNdg=; b=wDeEwEPdpKfsO2uAAYd2y1Zez8uglgg16E5wG8395gBLdg+7eI0bkUkf7p84YRhuqh cZ1WTHff2XeOCpYm4mifbodWOV4HVdY4iUlaiiRGBF1NoC18tvxcmnKSrsnXZedrCDiI D2RHXfJWtW1uGI+xwk1iaysV+h347vwm/b2jqkCE3OjZugNB276xex6tf1ZBsH4qQV7T qAsWIZ8QbB38nlvVhI9ItFuKSY77FbJR/U+FIf6utuWekIfrXuy3JATvFeTlZGqBBPIi fXMJoVWUXsjqGA+pkNKSe/BJv6DpRxUK/qGZe1W1JGyXl8UNiAiecdeBry/vaHm4vPa1 biEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cFXQHC0V8GMLC3OiTZXamaon3JSIk2wO6l+QqVkTNdg=; b=bEi2zPzpUwqSTp+kVNtAjvbjFo0OwZ4K1QcBA1w1xL8R/TwtI1eGkiywHIX4jpu9BX 6a9OixJCgwtfvCvNz6mBcFkDRuHb6jzfkg8kVPWZU0aupvcTsImn7sBU8N8U5ZcdCsKa 5ElC3dSAg4oZZdyCXQON+AOTbg586Nrgct7Mc/GQIS9SnjGmTAz6b4LT+p6i07MBVBrK MG+JZBQjxtcfnpRDNTjnvDlBxwfYPIha7LCn0QFNQc2bEgbHPrxBGxNs4PxzKPZ9+2/0 RWrKZwC6fwXPSmSWO6qSznWQIzi8+hPw7AJiUIkEfBK8b95qcK/AUvyV+W5QsmnWUJjt D57w== X-Gm-Message-State: ALyK8tIdgkCVgzODOJAPHW+Kn3gDVJtHAyFX22oy8UZJY3txWQLxSZl1060KxYLT/gb2tg== X-Received: by 10.129.156.199 with SMTP id t190mr33071080ywg.186.1469037857190; Wed, 20 Jul 2016 11:04:17 -0700 (PDT) Received: from mail-yw0-f173.google.com (mail-yw0-f173.google.com. [209.85.161.173]) by smtp.gmail.com with ESMTPSA id 139sm1455833ywe.14.2016.07.20.11.04.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 11:04:17 -0700 (PDT) Received: by mail-yw0-f173.google.com with SMTP id u134so51943004ywg.3 for ; Wed, 20 Jul 2016 11:04:16 -0700 (PDT) X-Received: by 10.129.89.66 with SMTP id n63mr32261650ywb.239.1469037856612; Wed, 20 Jul 2016 11:04:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.83.17.204 with HTTP; Wed, 20 Jul 2016 11:03:57 -0700 (PDT) In-Reply-To: <16030.1469037734@obiwan.sandelman.ca> References: <31989.1467205298@obiwan.sandelman.ca> <20981.1468858937@obiwan.sandelman.ca> <16030.1469037734@obiwan.sandelman.ca> From: Emil Ivov Date: Wed, 20 Jul 2016 20:03:57 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Michael Richardson Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: tools-discuss Subject: Re: [Tools-discuss] etherpad in jitsi X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 18:04:21 -0000 Our pleasure entirely :) On Wed, Jul 20, 2016 at 8:02 PM, Michael Richardson wrote: > > Emil Ivov wrote: > > The etherpad is now ietf's and the pads have the same name as the > > Jitsi Meet conference > > THANK YOU THANK YOU THANK YOU. > > > -- > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > -- https://jitsi.org From nobody Thu Jul 21 12:55:36 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1497A12D8DF for ; Thu, 21 Jul 2016 12:55:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.488 X-Spam-Level: X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d_6Rxgm-rG6N for ; Thu, 21 Jul 2016 12:55:33 -0700 (PDT) Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu [18.9.25.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88CB412D8DB for ; Thu, 21 Jul 2016 12:55:33 -0700 (PDT) X-AuditID: 1209190c-b3fff70000003193-7c-579128b40847 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id EE.16.12691.4B821975; Thu, 21 Jul 2016 15:55:32 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id u6LJtVD0023620 for ; Thu, 21 Jul 2016 15:55:32 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u6LJtSeO032314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 21 Jul 2016 15:55:31 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u6LJtSUu002284; Thu, 21 Jul 2016 15:55:28 -0400 (EDT) Date: Thu, 21 Jul 2016 15:55:28 -0400 (EDT) From: Benjamin Kaduk To: tools-discuss@ietf.org Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPIsWRmVeSWpSXmKPExsUixG6nrrtFY2K4wfJP8hbbj8xldGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxty9bAVXWSvute1hbmDcx9LFyMkhIWAi0fZqPlMXIxeHkEAb k8SKno+sEM45Ron36/vYIJz7TBIbbjdClTUwSvRv/s4E0s8ioC3R/P41O4jNJqAiMfPNRjYQ W0RASmJa4yqwHcICRhKfGj6B1fAKOEjcfXkRzBYV0JFYvX8KC0RcUOLkzCdgNrOAlsTy6dtY JjDyzkKSmoUktYCRaRWjbEpulW5uYmZOcWqybnFyYl5eapGuoV5uZoleakrpJkZQ2HBK8uxg PPPG6xCjAAejEg+vwosJ4UKsiWXFlbmHGCU5mJREed9OBgrxJeWnVGYkFmfEF5XmpBYfYpTg YFYS4e1VmxguxJuSWFmVWpQPk5LmYFES593+rT1cSCA9sSQ1OzW1ILUIJivDwaEkwbtdHahR sCg1PbUiLTOnBCHNxMEJMpwHaPgBkBre4oLE3OLMdIj8KUZdjgU/bq9lEmLJy89LlRLnjQcp EgApyijNg5sDjvfdTKqvGMWB3hLmFQZGvxAPMFXATXoFtIQJaMkcgX6QJSWJCCmpBsZi3asb lnybUueb1HNrrT6rsdCc0quLPSdLnpU+cfFPfr2F9J8vXLZG3e/KVpxKYLBX9bJg3v5SSO/9 ltMXTStOxGyraOtI+nF/Yb705R2nnwpdf3d7mf55hxzGIqVfxqLdz08eE7N2Ytnt0cRzS9pr vbxTUuXKUuZuhzmOTMW616rOTPzstUuJpTgj0VCLuag4EQC/GNxi0gIAAA== Archived-At: Subject: [Tools-discuss] finding expired documents related to a WG X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 19:55:35 -0000 Hi all, Barry says that you want us to stop using the tools wg pages in favor of the datatracker. One thing that I currently use the tools page for is to find individual documents related to the kitten WG -- kitten tends to move rather slowly, so there are a lot of documents more than 6 months old that are still of interest. The tools page currently has a link "to see all kitten-related documents, go to kitten-related drafts in the ID-archive"), which works pretty well. Is there a similar thing on the datatracker, or could there be? (I have some vague memory that the tools page used to actually show more documents inline instead of that link, but can't really substantiate that.) Thanks, Ben From nobody Thu Jul 21 13:18:41 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86FD512D567 for ; Thu, 21 Jul 2016 13:18:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.9 X-Spam-Level: X-Spam-Status: No, score=-106.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGebmb1IickZ for ; Thu, 21 Jul 2016 13:18:39 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 173C712D69C for ; Thu, 21 Jul 2016 13:18:39 -0700 (PDT) Received: from [2001:67c:370:136:c867:e200:5356:7986] (port=64647) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1bQKQY-0002oH-2Y; Thu, 21 Jul 2016 13:18:38 -0700 Message-ID: <57912E1C.5050703@levkowetz.com> Date: Thu, 21 Jul 2016 22:18:36 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Benjamin Kaduk , tools-discuss@ietf.org References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nsJLxrwIXNKVlEOWhxC8uN0QBbC1Cctm1" X-SA-Exim-Connect-IP: 2001:67c:370:136:c867:e200:5356:7986 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, kaduk@MIT.EDU X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) Archived-At: Subject: Re: [Tools-discuss] finding expired documents related to a WG X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 20:18:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --nsJLxrwIXNKVlEOWhxC8uN0QBbC1Cctm1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ben, On 2016-07-21 21:55, Benjamin Kaduk wrote: > Hi all, >=20 > Barry says that you want us to stop using the tools wg pages in favor o= f > the datatracker. Well, I want to make the datatracker good enough that you don't feel a need to use the tools pages. I'm still happy to maintain them without having any sunset date, but I'd love to make the datatracker even better than what I made the tools pages. > One thing that I currently use the tools page for is to > find individual documents related to the kitten WG -- kitten tends to m= ove > rather slowly, so there are a lot of documents more than 6 months old t= hat > are still of interest. Aha; right. > The tools page currently has a link "to see all > kitten-related documents, go to kitten-related drafts in the ID-archive= "), > which works pretty well. Is there a similar thing on the datatracker, = or > could there be? Hah. That's a document search feature which isn't available in the data-= tracker yet. Ok! I'll see what I can do. This is the kind of feedback which is very valuable in bringing the data-= tracker forward :-) > (I have some vague memory that the tools page used to actually show mor= e > documents inline instead of that link, but can't really substantiate > that.) I think that I at some point changed things from showing all related documents going back 2 (or maybe 3) years, to only showing related active= and replaced documents. This was done on request, and I believe I added the link to all related documents at that time, to support people looking= for expired related documents. Best regards, Henrik --nsJLxrwIXNKVlEOWhxC8uN0QBbC1Cctm1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJXkS4cAAoJEE6bV0uPuxcaNWAQAJ6WKZYSk4LaSXjSz/qurbNy r6A0uu05FNl3XS0q3/yKzGLDwyonwcqmnij4P7yuI2hrGUdVl9MtFKYuUS3zb0oz 2SnTPQD72VxnU35qTf52F/6uyxoMK0Ywhi8byciYq3MF5jdFubEMYZGQ+FbzQZgu rgLL58ppfqSlFQ+KzbKkIEBL8KfzRMJgwkoY3hu2Y3mWbqJ7i5uy+oSXyTBpHsuu K8gpWihvBSzDWIWy8WKIvCKG/IqxAf05T60pzSlX2PVp9ryCHiRB8hgimIx9kbQJ kTx962W8t5h15waPkIjBHu6DB4Cvlz6qcPcXYtyFynli+PP3ptavj0pJ0T8nSxVY MYdlFsYfEVDn6VY4LoRbhdgz/NfKkVr+StcGEv5i8RAo0+oZ6okQB88HgRVLcVuJ 3xOTvjsBEU4sQ3/pjdMIn4QrgyqWyAiUYLnxdCZWjm2sdz3wjEG4MNiCTpWWHF/2 7Y6Lf4v0qBWN/p7zXhZk0leBNGw9fOYnKqf8JC5BtJku3sOpWWlYmRRSCmq3f9Y4 1nJ+wsjVDHq10rvtlVPhu5ZTRpqE/42XiBJq84HjeSZVdStW6KO5GxFPaiZTbRKH NQGBAjrrN8dz46bNzeD6M/hdMkT94lJ/Ms0WfOOz7ueIn0e0k7K6sezG36NezNHf whSEsAWsQhl7y3JwLrtB =0JgM -----END PGP SIGNATURE----- --nsJLxrwIXNKVlEOWhxC8uN0QBbC1Cctm1-- From nobody Thu Jul 21 16:52:06 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD3E512DAD3 for ; Thu, 21 Jul 2016 16:52:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.934 X-Spam-Level: X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QpBske_iAeGb for ; Thu, 21 Jul 2016 16:52:05 -0700 (PDT) Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E664F12DAB8 for ; Thu, 21 Jul 2016 16:52:04 -0700 (PDT) Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-10v.sys.comcast.net with SMTP id QNjhbw7h2RingQNl6bj6JB; Thu, 21 Jul 2016 23:52:04 +0000 Received: from hobgoblin.ariadne.com ([73.100.16.189]) by comcast with SMTP id QNl5b1laQTXV7QNl5bQSym; Thu, 21 Jul 2016 23:52:04 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u6LNq2YY016671 for ; Thu, 21 Jul 2016 19:52:02 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u6LNq2Vw016668; Thu, 21 Jul 2016 19:52:02 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: tools-discuss@ietf.org In-Reply-To: (kaduk@MIT.EDU) Sender: worley@ariadne.com (Dale R. Worley) Date: Thu, 21 Jul 2016 19:52:02 -0400 Message-ID: <87shv2ft25.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfHIuQz+Uq+7g/Hwi5APwNOlFcm7/0o5Di9zO9UDix6B0XKJdhtAS8YIY0i/0DA+SZ9ng6JpR11By7Jevllkm2hGWe10mQU87qOrZlwjsLJzVvVxVBz3R WYixUrioV7kTOu7MwH7eMMsx37PRv7hL2jlrkyqp0Kg4PUUMG3BljLpCEtMxJKA2HskvwjE1pUC5RA== Archived-At: Subject: Re: [Tools-discuss] finding expired documents related to a WG X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 23:52:06 -0000 Benjamin Kaduk writes: > Barry says that you want us to stop using the tools wg pages in favor of > the datatracker. I'd like to note that I find the above sentence incomprehensible. The reason is that while I realize that the IETF web site is somehow partitioned between "tools" and "datatracker" (or something like that) -- to the point that they have separate logins! -- I never *ever* remember what pages are in which part. And I don't see why I should. Indeed, that is the worst failing of the IETF web site, that the users are supposed to keep track of which pages are in which part. How did this user-unfriendliness get established? My vague impression is that the actual difference is that different groups of people maintain each part. Turf wars run amok! Dale From nobody Thu Jul 21 17:25:45 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DCE212DB8B for ; Thu, 21 Jul 2016 17:25:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.488 X-Spam-Level: X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VgbPntcPF-9X for ; Thu, 21 Jul 2016 17:25:42 -0700 (PDT) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD85F12DB80 for ; Thu, 21 Jul 2016 17:25:42 -0700 (PDT) X-AuditID: 12074423-c93ff70000003a34-ab-579168036244 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id F9.D2.14900.30861975; Thu, 21 Jul 2016 20:25:41 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id u6M0PdKm005546; Thu, 21 Jul 2016 20:25:39 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u6M0PVjb005398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 21 Jul 2016 20:25:38 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u6M0PVb7006730; Thu, 21 Jul 2016 20:25:31 -0400 (EDT) Date: Thu, 21 Jul 2016 20:25:31 -0400 (EDT) From: Benjamin Kaduk To: Henrik Levkowetz In-Reply-To: <57912E1C.5050703@levkowetz.com> Message-ID: References: <57912E1C.5050703@levkowetz.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIIsWRmVeSWpSXmKPExsUixCmqrcuaMTHc4O40RYvmtkNsFtuPzGV0 YPJYsuQnk8fy+TsYA5iiuGxSUnMyy1KL9O0SuDIW/Z/NWjCds2LR1quMDYyT2LsYOTkkBEwk dq++z9rFyMUhJNDGJHHswUVmCGcjo0TvxjdsEM4hJokdt3YzQTgNjBLbfpxiAulnEdCW6Hu4 lQ3EZhNQkZj5ZiOYLQISv/EHaC4HB7OAlETfYrB1wgJuEjNfHAMr4RTQlZj9ohFsDK+Ag8SZ R4tYQWwhgUSJ3w0PwGxRAR2J1funsEDUCEqcnPkEzGYW0JJYPn0bywRGgVlIUrOQpBYwMq1i lE3JrdLNTczMKU5N1i1OTszLSy3SNdPLzSzRS00p3cQICkl2F+UdjC/7vA8xCnAwKvHwnng6 IVyINbGsuDL3EKMkB5OSKO/byUAhvqT8lMqMxOKM+KLSnNTiQ4wSHMxKIrzH0yaGC/GmJFZW pRblw6SkOViUxHm3f2sPFxJITyxJzU5NLUgtgsnKcHAoSfCuBGkULEpNT61Iy8wpQUgzcXCC DOcBGn4MbHhxQWJucWY6RP4Uo6KUOO9RkIQASCKjNA+uF5wydjOpvmIUB3pFmPctSBUPMN3A db8CGswENHiOQD/I4JJEhJQUME3cO8ZqHPp3/t5PMz9t7trh2vxGbwHbuxBbB/lbGUE37z58 ov84p8azu2ZZ5eoPa2ZmfJJty/88y6Ujoll0BfMKVdZvaybwfv3PIyDQv+TPVGMJ5nk3tO2D 1A/EnXu2zHKz+bx7N87c/Bco98AljeVdRbXL1J2132O+BC9M+ty7cp7MmWVz9r1RYinOSDTU Yi4qTgQAiLiJh/QCAAA= Archived-At: Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] finding expired documents related to a WG X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 00:25:44 -0000 On Thu, 21 Jul 2016, Henrik Levkowetz wrote: > Hi Ben, > > On 2016-07-21 21:55, Benjamin Kaduk wrote: > > > The tools page currently has a link "to see all > > kitten-related documents, go to kitten-related drafts in the ID-archive"), > > which works pretty well. Is there a similar thing on the datatracker, or > > could there be? > > Hah. That's a document search feature which isn't available in the data- > tracker yet. Ok! I'll see what I can do. Thanks! > > (I have some vague memory that the tools page used to actually show more > > documents inline instead of that link, but can't really substantiate > > that.) > > I think that I at some point changed things from showing all related > documents going back 2 (or maybe 3) years, to only showing related active > and replaced documents. This was done on request, and I believe I added > the link to all related documents at that time, to support people looking > for expired related documents. Seems reasonable. The link is great for me, so no complaints from me. And thanks again for all the work you put into the tools; we could not do the work we do without them. -Ben From nobody Thu Jul 21 22:18:40 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD3B12DF24 for ; Thu, 21 Jul 2016 22:18:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hqiq312VKiLt for ; Thu, 21 Jul 2016 22:18:23 -0700 (PDT) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CA2912DF23 for ; Thu, 21 Jul 2016 22:18:23 -0700 (PDT) Received: by mail-qk0-x22f.google.com with SMTP id o67so92749678qke.1 for ; Thu, 21 Jul 2016 22:18:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=iOmgcGEvbUMMGEnSfNI5CkNvWw0dshcI4Cyir5QiHCk=; b=V/2CrxM6qaV1vCyjbkgo+EOsArRhTpL8vYGDQboLlOQ+Ga4zXNq9UbWrbZBsnYFHg+ r6vwFtCgzgaYgwD7ujnM8S2oW5tKF4oTicHFKoKuCwxUxzwQ3lqmmciQLnP2bqnuP8JV +JgaH02+VECcXKzxUCgFcalw4kAFgPS88nA//ZRcgvFp73f2XiuthwbyqfL4tjGMCkbv gDqZ5gOWzT5Cn0e37JrN3LTq5LHwp7s2O9ins+Cb7lx4VOzPh4pt4bn92gO9sHY2D+SD +7D0z9strLl9vuXsI/obeMdAzddsWAttC7NRFCdET5n8lKeSvbJzpdhcee+sFodZVuYk 2yng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=iOmgcGEvbUMMGEnSfNI5CkNvWw0dshcI4Cyir5QiHCk=; b=fl9aI606iaVoLpEAuhBfp5LE6+ceJzKRMxNtq3lGYB8ge+6SuUTGInMhniTwN5bnpx 8Kr9HBxqrqBojMj/8kUzvzwi1JK6Za498twPmzEOSDt5JCQYufcA5UGA7oenWy1cB3po TOMkjKvTD4ncfq1XFoWxaJdrmHAZzqIZYOvRr73FFxKxFnyWLwwtxSAYlGhunXMwiMiw Kq34xeDb4nbY+tgPdIQkdUHfijHzmSBgV29rDXkn/weB6M8vFziHIAzf/qIIurOkfRw2 bdQdMryn0/k4ZU1aPepmrclXAcIXkFJGxzpmJUaTuLRLgOrKcey0GBKj/ZciTs6+wBXw Jzrg== X-Gm-Message-State: AEkooutfx1ZPhswl2W8ozBuIrK4UR4T1hEFhA3AbEFKIs/CUIGdglOFCRL8QqVZEnHu2hA== X-Received: by 10.55.23.25 with SMTP id i25mr2592279qkh.142.1469164702652; Thu, 21 Jul 2016 22:18:22 -0700 (PDT) Received: from ?IPv6:2001:67c:370:136:28cc:dc4c:9703:6781? ([2001:67c:370:136:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 2sm6392587qta.2.2016.07.21.22.18.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jul 2016 22:18:22 -0700 (PDT) To: Henrik Levkowetz , Benjamin Kaduk , tools-discuss@ietf.org References: <57912E1C.5050703@levkowetz.com> From: Brian E Carpenter Organization: University of Auckland Message-ID: Date: Fri, 22 Jul 2016 17:18:29 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <57912E1C.5050703@levkowetz.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] finding expired documents related to a WG X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 05:18:32 -0000 What's wrong with this? https://datatracker.ietf.org/doc/search/?name=&sort=&rfcs=on&activedrafts=on&olddrafts=on&by=group&group=kitten In other words use the Additional search criteria in the tracker search Regards Brian Carpenter (Don't blame me, I voted Remain.) On 22/07/2016 08:18, Henrik Levkowetz wrote: > Hi Ben, > > On 2016-07-21 21:55, Benjamin Kaduk wrote: >> Hi all, >> >> Barry says that you want us to stop using the tools wg pages in favor of >> the datatracker. > > Well, I want to make the datatracker good enough that you don't feel a > need to use the tools pages. I'm still happy to maintain them without > having any sunset date, but I'd love to make the datatracker even better > than what I made the tools pages. > >> One thing that I currently use the tools page for is to >> find individual documents related to the kitten WG -- kitten tends to move >> rather slowly, so there are a lot of documents more than 6 months old that >> are still of interest. > > Aha; right. > >> The tools page currently has a link "to see all >> kitten-related documents, go to kitten-related drafts in the ID-archive"), >> which works pretty well. Is there a similar thing on the datatracker, or >> could there be? > > Hah. That's a document search feature which isn't available in the data- > tracker yet. Ok! I'll see what I can do. > > This is the kind of feedback which is very valuable in bringing the data- > tracker forward :-) > >> (I have some vague memory that the tools page used to actually show more >> documents inline instead of that link, but can't really substantiate >> that.) > > I think that I at some point changed things from showing all related > documents going back 2 (or maybe 3) years, to only showing related active > and replaced documents. This was done on request, and I believe I added > the link to all related documents at that time, to support people looking > for expired related documents. > > > Best regards, > > Henrik > > > > From nobody Fri Jul 22 00:45:11 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BC412DA6D for ; Fri, 22 Jul 2016 00:45:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.188 X-Spam-Level: X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5dpVnHk4zvPg for ; Fri, 22 Jul 2016 00:45:08 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF07C12DA5B for ; Fri, 22 Jul 2016 00:45:08 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id E5222200A5; Fri, 22 Jul 2016 03:54:44 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BCDDB638BE; Fri, 22 Jul 2016 03:45:07 -0400 (EDT) From: Michael Richardson To: worley@ariadne.com (Dale R. Worley) In-Reply-To: <87bn21xr1q.fsf@hobgoblin.ariadne.com> References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 07:45:10 -0000 --=-=-= Content-Type: text/plain Dale R. Worley wrote: > Michael Richardson writes: >> Is there a suggested LICENSE.txt for internet-drafts repos that live on >> github (or elsewhere)? > I think the boilerplate of each I-D contains the copyright/licensing > information for the I-D. For instance, Yes, but it's not physically in the .xml file until you run xml2rfc on it. So someone has a reasonable reason to be confused if they see a git repo that hasn't got a generated .txt file in it. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBV5HPAYCLcPvd0N1lAQLYOAf9GQ3DMCANfRf/VC0vYBTy+ST0MyB+625A nBDZXvtXKthL+IYqkJF5eeZBMG401okXAMi962cYnc3DZqdWCCj7xNSOKXfOhORv GZ9JvXeNdfJ4KCf/OLKVQSXuf+tAs+6AR/2gWDsDRvzMX6arCc9L33FY/J5ZAOYw jgLHpxWaKBDzykQxzUc/SSluEyq0l2wz3b99bNZEWx99G7tyfYlGZuWTrri1vf5P kigiUxytVKWrUoZ2xTfj3fUnlYL489MDDMLrgvlloPnbb4VxQXIAnq7FABmsx1Tk DUFmBDIk7PelMy8SVBkUMktgOdAPEaQGckorwxyCr7/XNSJg8lPF5A== =xRSh -----END PGP SIGNATURE----- --=-=-=-- From nobody Fri Jul 22 00:51:17 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 171F912DA6D for ; Fri, 22 Jul 2016 00:51:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzgjwnXlXNDR for ; Fri, 22 Jul 2016 00:51:03 -0700 (PDT) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F354912DA5B for ; Fri, 22 Jul 2016 00:51:02 -0700 (PDT) Received: by mail-lf0-x22a.google.com with SMTP id l69so79089742lfg.1 for ; Fri, 22 Jul 2016 00:51:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Rk9y550cs0YSGm77GV6CLCYvc+VC30yzAsh+aF87qP0=; b=y2C6Dwxs1fjR4K4wdmr9eRfaE81hPMa+w6s0/hkRU1nHZRXAH1uuOUicy1/lrz+/+S L2ktXQRC95vh+g4sKlyLJIourTjW6p7qAeRbGcwC2GnSmuOM7kh115eWCUJpTgdtBof9 5G1Dzue5EeW1KWacMC+esUI0eRb1wi29aEqM3oBSZmWcYBD9Z2OxtUsxlCYmLPol31ZV 8O1cxom5hsd4Kl20HaCwbRoh8F8/cM5EalvBhIf8edXCZ91gQLHNKjKCXIIp9UBFAIHS ONwAaD7HqJ3CLWH8PZ4goL1XJspLIweIyezlHPckop2iEYLvN6eziYNZ3GhTuJw+g/Bi k/aQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Rk9y550cs0YSGm77GV6CLCYvc+VC30yzAsh+aF87qP0=; b=JWqYDjKic8VOL/OwgL5qCJPrnWwgvFywX743Ve4cvhHSToQCbDBxPh63qjmwEH8nIZ Ok3yEnIbk5OVoo79g7ebGr1RWN0L7rrcH9XiYG/VUO6iFFsd8AXgSnN0FCmDf9pSHJaZ 7PG8br5k+/xR3jKewGWD6kPPulJalbTJlE801SqLe/OZSVMaSC4GG1r/4LAzBz5zo75Z haW6MlUkuHGR+oNH704FuUMIeoYU5beaTAU81iW95hsyqn6KjMy9QLNqAiJly7UjhYsS QiMSEHWflrltL12sYozSVXur7jCkwR7AY3Mb98QJqEAsYVTW4OIHWCrnm0y60POyfVcz NpPQ== X-Gm-Message-State: AEkoousqZXwOIDXlyv6iRc7l9kjrD4331hcytF54vwBvBFcolC2YFPfgiAf1CP5A3rw1Ng== X-Received: by 10.25.214.166 with SMTP id p38mr1953819lfi.168.1469173860820; Fri, 22 Jul 2016 00:51:00 -0700 (PDT) Received: from ?IPv6:2001:67c:370:176:28cc:dc4c:9703:6781? ([2001:67c:370:176:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id f139sm2670583lfb.11.2016.07.22.00.50.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 00:50:59 -0700 (PDT) To: tools-discuss@ietf.org References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> <27031.1469173507@obiwan.sandelman.ca> From: Brian E Carpenter Organization: University of Auckland Message-ID: <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> Date: Fri, 22 Jul 2016 19:51:08 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <27031.1469173507@obiwan.sandelman.ca> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 07:51:08 -0000 On 22/07/2016 19:45, Michael Richardson wrote: > > Dale R. Worley wrote: > > Michael Richardson writes: > >> Is there a suggested LICENSE.txt for internet-drafts repos that live on > >> github (or elsewhere)? > > > I think the boilerplate of each I-D contains the copyright/licensing > > information for the I-D. For instance, > > Yes, but it's not physically in the .xml file until you run xml2rfc on it. > So someone has a reasonable reason to be confused if they see a git repo > that hasn't got a generated .txt file in it. IANAL and YANAL either. So I suggest that LICENSE.txt should simply point to the IETF Trust legal provisions: http://trustee.ietf.org/trust-legal-provisions.html Brian From nobody Fri Jul 22 01:33:29 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9149012DA7E for ; Fri, 22 Jul 2016 01:33:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWTkUb1TdnqX for ; Fri, 22 Jul 2016 01:33:25 -0700 (PDT) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E92812DAAF for ; Fri, 22 Jul 2016 01:33:22 -0700 (PDT) Received: by mail-lf0-x22b.google.com with SMTP id f93so80176262lfi.2 for ; Fri, 22 Jul 2016 01:33:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=R1ipTD7NeMtUa5XpPHy1J7iZxgVZUJf9TSZUuihTkiY=; b=POtl0dRY1OZTTAADsR7NWg1jwLqTaJLBVyUPEIZqeAIQY2rHvScm1De+5RpjsLPJfn H3rfJI27NvnYTB6uhWER6zhbA8sEznFcOD/i1Pv7GXwZ74x2e9kQOeMd0x7SyoJYLTl+ JuNN4cp0S0Mhw6QSjCKDGtSh70ifpglc96xtJUgcaSScMJq5no5tHLRQPuH7V3EXVBbJ WlbgOLvJEK/Gu1KGH32e81hHEyZuNZPSeDpOtV73ZGZFO2q6Ehs1ZJ3xNJIN52o4cM9T JDG0DG00NNoqxPzbQ5zRUP84wWeay4I8XLrUPywb/b4WKWzpajrjuMox27fQWDMEVZmI iwug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=R1ipTD7NeMtUa5XpPHy1J7iZxgVZUJf9TSZUuihTkiY=; b=ihgnv4hiYHRIwsmI6QI04vpAnTvCXf72Q/OGEwVRi7MfIF7SAujT+2o41mAASnWnCK acm/7HPzhyL/0Urr7gtn8uXz8w5LjavIQtSuzgyqXeR7O2afDFRHP3l7s4knSKzULFro NejAOfZZ8UC1KxZLxRBdCM26uTImUn/D4fcBDqkJmoT/aHIJpfgQ53GSg/yeXize1eKR e2XNaAEAI+r7QJ01tR+JibDplDzKNO9scWmNdyljI9cBSUu5s71AGF0/bsoMbZeFOgL3 t2FOtWdSZSv5xqdY5Le2ZA3DC2JZPt6xA6mQQc+yvusRcnA0UFsPR81c4mlNUMpTnXfb aZyA== X-Gm-Message-State: AEkoouunSCzccdBunyek5KqJYLLUEjjLSUFYJ5Wz+iTgxwGfCslvHBWkAk/GuObsC6a8cQ== X-Received: by 10.25.16.212 with SMTP id 81mr1986413lfq.174.1469176400331; Fri, 22 Jul 2016 01:33:20 -0700 (PDT) Received: from [172.30.3.113] (ip5b423c2f.dynamic.kabel-deutschland.de. [91.66.60.47]) by smtp.gmail.com with ESMTPSA id f4sm2717420lji.41.2016.07.22.01.33.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 01:33:19 -0700 (PDT) To: Brian E Carpenter , tools-discuss@ietf.org References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> <27031.1469173507@obiwan.sandelman.ca> <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> From: Yaron Sheffer Message-ID: <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> Date: Fri, 22 Jul 2016 10:33:16 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 08:33:27 -0000 On 22/07/16 09:51, Brian E Carpenter wrote: > On 22/07/2016 19:45, Michael Richardson wrote: >> >> Dale R. Worley wrote: >> > Michael Richardson writes: >> >> Is there a suggested LICENSE.txt for internet-drafts repos that live on >> >> github (or elsewhere)? >> >> > I think the boilerplate of each I-D contains the copyright/licensing >> > information for the I-D. For instance, >> >> Yes, but it's not physically in the .xml file until you run xml2rfc on it. >> So someone has a reasonable reason to be confused if they see a git repo >> that hasn't got a generated .txt file in it. > > IANAL and YANAL either. So I suggest that LICENSE.txt should simply > point to the IETF Trust legal provisions: > http://trustee.ietf.org/trust-legal-provisions.html > > Brian > Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE.md I copied two sections from the current I-D boilerplate, Status and Copyright, with tiny editorial changes (plural documents instead of singular). I think it is important that "users" should know what I-Ds are, hence the Status. Thanks, Yaron From nobody Fri Jul 22 02:09:30 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40B4E12DAAB for ; Fri, 22 Jul 2016 02:09:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dyq7RZhnpmKA for ; Fri, 22 Jul 2016 02:09:26 -0700 (PDT) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7642212DA87 for ; Fri, 22 Jul 2016 02:09:26 -0700 (PDT) Received: by mail-qk0-x232.google.com with SMTP id o67so96130426qke.1 for ; Fri, 22 Jul 2016 02:09:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FCAdsDJpnK3vE5iPQybeweHWGZNWBBfo+Dtdy1i1O5o=; b=jdOglwk75EpQafKGoIzQDbdy5cWkd9L+0viwKlr/8whph4+epLxBjqQNkhsEH5GgJ1 z3UGVBcKR3G42OOL3cKWuPCJ4GaNvdqNQlpyEZoOzBSEeVt5RRYg7ADKz6NJZKhEBsUo YWg6DI2qpmaZeobaNB+ZCDSsABMeoahnqbv2gu2/TnuwWmUpu+MYbg3DQB82QMlBGTgw FKjjnSbv0TTQioQcuibzAAcBBGIYKAugZNiTzXTNbTsmLsOVzK4gc81bZaYAXPh4xV5g 2FnhHRVrjQAQSOUK/VWfZtzUk7DIbhulYxapGdvkVcH5X3bqbhKQCbV7QWT/hDH6Kc+E zaeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FCAdsDJpnK3vE5iPQybeweHWGZNWBBfo+Dtdy1i1O5o=; b=CG4WdPPvT7ZPwI9nmvcoBb+2e8L120+fs/1Cgmmsc17nICSItgn7PdeNpvmlOuC0uZ uVo+QN1hW7yyzphDe6KZsLibzXdAJ7P0Lhz426mmXxIr1jKb9GADnb40+59lJ98Y7YIr otvEFqI4jSmPXLG7dWDLeXIok7c9eIVdUVf9rUEM/uDDKgUALkC1ufV7bTq77xUfI/dF dVU04JI44hahc+50VvAjTV7DIXVJT2eO63+8Zw1mfgLgeU86God0fwFRh1wZKmlrvbAq igY1RX/jUls/0JeqqpFTR0vAHccv9M0i/5pWOHsSsrZVlDMsuWSTrw393lTQZHy23Q3G uMCA== X-Gm-Message-State: AEkoouvUSrS2m/+SeXEyDqwbvgTDRzUoPhvCQdUhcHHk6kdDB9XadOQLX8OylchOPBEdzLBbYVlDofNeKupNqw== X-Received: by 10.55.201.70 with SMTP id q67mr3320308qki.124.1469178565665; Fri, 22 Jul 2016 02:09:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.22.146 with HTTP; Fri, 22 Jul 2016 02:09:25 -0700 (PDT) In-Reply-To: <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> <27031.1469173507@obiwan.sandelman.ca> <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> From: Martin Thomson Date: Fri, 22 Jul 2016 11:09:25 +0200 Message-ID: To: Yaron Sheffer Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "tools-discuss@ietf.org Discussion" Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 09:09:29 -0000 If you manage to work this out, then I'd be interested in receiving a pull request. https://github.com/martinthomson/i-d-template On 22 July 2016 at 10:33, Yaron Sheffer wrote: > On 22/07/16 09:51, Brian E Carpenter wrote: >> >> On 22/07/2016 19:45, Michael Richardson wrote: >>> >>> >>> Dale R. Worley wrote: >>> > Michael Richardson writes: >>> >> Is there a suggested LICENSE.txt for internet-drafts repos that >>> live on >>> >> github (or elsewhere)? >>> >>> > I think the boilerplate of each I-D contains the >>> copyright/licensing >>> > information for the I-D. For instance, >>> >>> Yes, but it's not physically in the .xml file until you run xml2rfc on >>> it. >>> So someone has a reasonable reason to be confused if they see a git repo >>> that hasn't got a generated .txt file in it. >> >> >> IANAL and YANAL either. So I suggest that LICENSE.txt should simply >> point to the IETF Trust legal provisions: >> http://trustee.ietf.org/trust-legal-provisions.html >> >> Brian >> > > Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE.md > > I copied two sections from the current I-D boilerplate, Status and > Copyright, with tiny editorial changes (plural documents instead of > singular). I think it is important that "users" should know what I-Ds are, > hence the Status. > > Thanks, > Yaron > > > -- > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss > > Please report datatracker.ietf.org bugs at > http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org > > Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or > send email to webmaster@tools.ietf.org From nobody Fri Jul 22 02:42:50 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9693412DC51 for ; Fri, 22 Jul 2016 02:42:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.187 X-Spam-Level: X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMbmup7ibYme for ; Fri, 22 Jul 2016 02:42:46 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EEFB12D0A8 for ; Fri, 22 Jul 2016 02:42:45 -0700 (PDT) Received: from [10.133.69.117] (unknown [176.5.32.69]) by tuna.sandelman.ca (Postfix) with ESMTPSA id EAA34200A5; Fri, 22 Jul 2016 05:52:19 -0400 (EDT) User-Agent: K-9 Mail for Android In-Reply-To: References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> <27031.1469173507@obiwan.sandelman.ca> <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----ZJIRFLXW6L8NTILQCD4OKLJHBD3SLG" Content-Transfer-Encoding: 8bit From: Michael Richardson Date: Fri, 22 Jul 2016 11:42:37 +0200 To: Martin Thomson , Yaron Sheffer Message-ID: <088F2F5A-4F10-4877-B5CD-9AFFC23F5D93@sandelman.ca> Archived-At: Cc: "tools-discuss@ietf.org Discussion" Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 09:42:49 -0000 ------ZJIRFLXW6L8NTILQCD4OKLJHBD3SLG Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 i did what Joe suggested and pointed at IETF trust, but maybe I will adopt Brians suggestion instead. On 22 July 2016 11:09:25 CEST, Martin Thomson wrote: >If you manage to work this out, then I'd be interested in receiving a >pull request. > >https://github.com/martinthomson/i-d-template > >On 22 July 2016 at 10:33, Yaron Sheffer wrote: >> On 22/07/16 09:51, Brian E Carpenter wrote: >>> >>> On 22/07/2016 19:45, Michael Richardson wrote: >>>> >>>> >>>> Dale R. Worley wrote: >>>> > Michael Richardson writes: >>>> >> Is there a suggested LICENSE.txt for internet-drafts repos >that >>>> live on >>>> >> github (or elsewhere)? >>>> >>>> > I think the boilerplate of each I-D contains the >>>> copyright/licensing >>>> > information for the I-D. For instance, >>>> >>>> Yes, but it's not physically in the .xml file until you run xml2rfc >on >>>> it. >>>> So someone has a reasonable reason to be confused if they see a git >repo >>>> that hasn't got a generated .txt file in it. >>> >>> >>> IANAL and YANAL either. So I suggest that LICENSE.txt should simply >>> point to the IETF Trust legal provisions: >>> http://trustee.ietf.org/trust-legal-provisions.html >>> >>> Brian >>> >> >> Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE.md >> >> I copied two sections from the current I-D boilerplate, Status and >> Copyright, with tiny editorial changes (plural documents instead of >> singular). I think it is important that "users" should know what I-Ds >are, >> hence the Status. >> >> Thanks, >> Yaron >> >> >> -- >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss >> >> Please report datatracker.ietf.org bugs at >> http://tools.ietf.org/tools/ietfdb >> or send email to datatracker-project@ietf.org >> >> Please report tools.ietf.org bugs at >http://tools.ietf.org/tools/issues or >> send email to webmaster@tools.ietf.org > >-- >Tools-discuss mailing list >Tools-discuss@ietf.org >https://www.ietf.org/mailman/listinfo/tools-discuss > >Please report datatracker.ietf.org bugs at >http://tools.ietf.org/tools/ietfdb >or send email to datatracker-project@ietf.org > >Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues >or >send email to webmaster@tools.ietf.org -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ------ZJIRFLXW6L8NTILQCD4OKLJHBD3SLG Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit i did what Joe suggested and pointed at IETF trust, but maybe I will adopt Brians suggestion instead.

On 22 July 2016 11:09:25 CEST, Martin Thomson <martin.thomson@gmail.com> wrote:
If you manage to work this out, then I'd be interested in receiving a
pull request.

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

On 22 July 2016 at 10:33, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
 On 22/07/16 09:51, Brian E Carpenter wrote:

 On 22/07/2016 19:45, Michael Richardson wrote:


 Dale R. Worley <worley@ariadne.com> wrote:
 Michael Richardson
<mcr+ietf@sandelman.ca> writes:
 Is there a suggested LICENSE.txt for internet-drafts repos that
 live on
 github (or elsewhere)?

 I think the boilerplate of each I-D contains the
 copyright/licensing
 information for the I-D.  For instance,

 Yes, but it's not physically in
the .xml file until you run xml2rfc on
 it.
 So someone has a reasonable reason to be confused if they see a git repo
 that hasn't got a generated .txt file in it.


 IANAL and YANAL either. So I suggest that LICENSE.txt should simply
 point to the IETF Trust legal provisions:
 http://trustee.ietf.org/trust-legal-provisions.html

     Brian


 Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE.md

 I copied two sections from the current I-D boilerplate, Status and
 Copyright, with tiny editorial changes (plural documents instead of
 singular). I think it is important that "users" should know what I-Ds are,
 hence the Status.

 Thanks,
         Yaron


 --
 Tools-discuss mailing list

Tools-discuss@ietf.org
 https://www.ietf.org/mailman/listinfo/tools-discuss

 Please report datatracker.ietf.org bugs at
 http://tools.ietf.org/tools/ietfdb
 or send email to datatracker-project@ietf.org

 Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
 send email to webmaster@tools.ietf.org

--
Sent from my Android device with K-9 Mail. Please excuse my brevity. ------ZJIRFLXW6L8NTILQCD4OKLJHBD3SLG-- From nobody Fri Jul 22 02:52:55 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D844F12B005 for ; Fri, 22 Jul 2016 02:52:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UZUq4O_88gnZ for ; Fri, 22 Jul 2016 02:52:51 -0700 (PDT) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F4FE12DC49 for ; Fri, 22 Jul 2016 02:52:48 -0700 (PDT) Received: by mail-wm0-x236.google.com with SMTP id p129so7525041wmp.0 for ; Fri, 22 Jul 2016 02:52:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=g2zr2VWKOW4C8ULYIEoOxlkT7pGQ9RfygkDSceZywN0=; b=RgtNHRlqcwlEkjCfSbcCOTBmBaoBi56MVCJJcd994OEqIAdnpgi3LYo31/w0qVhHko L+agHKE3LAT60r8hB0k9D9pIoIkjZBmFlTQLexvVhVxcr3TExNbF7q2OOIYdcDuFR7GK /v/XlRscS6HZKqHJ+9KvcesVseagWvyDiY/JqECgcBctllx8mJWI/w8lMZd8BktNW3Ml yxGFtWP0A6EBnL7++yZ2nWBa3XlEkZnHFyp35J0ucF/FyEDyXdXkW/RX9AiLT9IY+aKx bsEuDH5oMG4FumyX5KllusJ0eVKqmYA8hiy+DXAHbmVDur6OOqc5HOeDLku9xxaP7iOY NfHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=g2zr2VWKOW4C8ULYIEoOxlkT7pGQ9RfygkDSceZywN0=; b=SHFCB91GoZxdIc7949DNSfRd5GF9r90N1Y7IigD3v/cH0JvqKEBOHMj93sFAg2sWt9 Sq090lBtyrZgxltwnOeDsBmyP4DYI6EQcQdrvQwnlG1MafKixhcPOKm0QUyvv2ijahLf /8QD7l3gkamegiwRILyVBnXICl+yD/sHmPyOF4dDrrnB+laZlxjCzvDadpXqpIwDJLcB 6Ovp3xpRaax9Ht2rmYgwuMvKfgcK/utTeolnfi8zdDA1qkk+2wdRVrn57hY5AQbYa/1z 4nv8+Pi8tgIEtzdjnU9TBW/UUDHdn11oDnXYbOgGP3nCTdCo8NiXMWC/umZJpS7/0DtR 7eCQ== X-Gm-Message-State: AEkoousa+nwlGv/euOXoQZLkPZBFQvfRtRw72xQ6l3XEAgEGbZ81kg37/t07XsG9v5u5Xw== X-Received: by 10.194.186.166 with SMTP id fl6mr88451wjc.44.1469181166863; Fri, 22 Jul 2016 02:52:46 -0700 (PDT) Received: from ?IPv6:2001:67c:370:176:28cc:dc4c:9703:6781? ([2001:67c:370:176:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id vr5sm83685wjc.29.2016.07.22.02.52.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 02:52:46 -0700 (PDT) To: Yaron Sheffer , tools-discuss@ietf.org References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> <27031.1469173507@obiwan.sandelman.ca> <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> From: Brian E Carpenter Organization: University of Auckland Message-ID: Date: Fri, 22 Jul 2016 21:52:55 +1200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 09:52:54 -0000 Yaron, That looks OK to my non-lawyer eyes but I suggest asking the IETF Trust to ask their lawyer (who I assure you is very geek-friendly) if it's OK. Regards Brian On 22/07/2016 20:33, Yaron Sheffer wrote: > On 22/07/16 09:51, Brian E Carpenter wrote: >> On 22/07/2016 19:45, Michael Richardson wrote: >>> >>> Dale R. Worley wrote: >>> > Michael Richardson writes: >>> >> Is there a suggested LICENSE.txt for internet-drafts repos that live on >>> >> github (or elsewhere)? >>> >>> > I think the boilerplate of each I-D contains the copyright/licensing >>> > information for the I-D. For instance, >>> >>> Yes, but it's not physically in the .xml file until you run xml2rfc on it. >>> So someone has a reasonable reason to be confused if they see a git repo >>> that hasn't got a generated .txt file in it. >> >> IANAL and YANAL either. So I suggest that LICENSE.txt should simply >> point to the IETF Trust legal provisions: >> http://trustee.ietf.org/trust-legal-provisions.html >> >> Brian >> > > Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE.md > > I copied two sections from the current I-D boilerplate, Status and Copyright, with tiny editorial changes (plural documents > instead of singular). I think it is important that "users" should know what I-Ds are, hence the Status. > > Thanks, > Yaron > From nobody Fri Jul 22 02:56:59 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FC412DF4C for ; Fri, 22 Jul 2016 02:56:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGx_1HFSewXl for ; Fri, 22 Jul 2016 02:56:55 -0700 (PDT) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3675E12DF4D for ; Fri, 22 Jul 2016 02:56:53 -0700 (PDT) Received: by mail-wm0-x236.google.com with SMTP id f65so50945140wmi.0 for ; Fri, 22 Jul 2016 02:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=7ECm8zD5ZzlP5yHD33a+yRFdMokoG3Y1/HW+AMz1Hec=; b=P8V7EaHsJp/paVe5TZAwtwGLfoDuyahCQr2IFwWVnmdeBVlWleMVD0XJtd6SHf1WFN Vag1152wcbvnmOkhIY+tPB2uJTTxuJwPsxe3aciPPI3cqSA6E1xjX5n0vNXOCy3FzbnC XabDFBoUPj7+0Eo7Q0BYw0B12oNjWNLF0319+X0gp6TcScZ2AVcVUOhmc5Toi2YlB4Mg pJZ3O04BiwuYEJIRlgzPyO+HLZnRqDzRFajp6XWtp4rOofDYtRgXN6jRLm+NJOTVtHbP 8+aoddvaCeJokaEA8pB+U9oj8rghZX1UcQQ3AqTY+/gAj7IdWgXk1vhKV5OdlGtoFjzq ubpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=7ECm8zD5ZzlP5yHD33a+yRFdMokoG3Y1/HW+AMz1Hec=; b=EjBtAFrTYvF10aoKjGqs22xKsKP+gvUtZHxSlcReCdD9LTmRfd/XsjtVdxTCvS113t 9Hp8NWmN/eHfK9A2SzjhQIdMnRdrv410BDqtO90DAqlMc+1SBmXzt66DdpyQTe6/trPP Ml/BCzu6IKGlAsSJxFDPYYTfG9E13ZwiWtn8N0idQbUfqTLSQ0Xm+HgNJvhzgZbIhpEO 3fdH+bkn4lEsQjqWysqsE31aQqoGc9PrZ7p9AeH1F83Y8SOBjWInht39Qylh3o3bc5kC rUgL2MgnyOAXHS/VaP17F93pgjWrJH+EeieqahWAP2xPMBzarVwo/4kDd0td2P0wCJUb VOUw== X-Gm-Message-State: AEkoout+TtpgICesc0Fh/sRIylZg/vrUHHnWkv/8I8wN5UmlmMAOXxwF8GAou2hLkVgHNw== X-Received: by 10.195.12.111 with SMTP id ep15mr100140wjd.124.1469181411567; Fri, 22 Jul 2016 02:56:51 -0700 (PDT) Received: from ?IPv6:2001:67c:370:176:b5f9:5d4c:a99c:7e15? ([2001:67c:370:176:b5f9:5d4c:a99c:7e15]) by smtp.gmail.com with ESMTPSA id u72sm11744439wmf.5.2016.07.22.02.56.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 02:56:50 -0700 (PDT) To: Brian E Carpenter , tools-discuss@ietf.org References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> <27031.1469173507@obiwan.sandelman.ca> <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> From: Yaron Sheffer Message-ID: <86d295de-d3bc-d574-9c97-70e0b622ee44@gmail.com> Date: Fri, 22 Jul 2016 11:56:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 09:56:58 -0000 Hi Brian, Could you please connect me to the relevant people? I will then share the outcome with this list. Thanks, Yaron On 22/07/16 11:52, Brian E Carpenter wrote: > Yaron, > > That looks OK to my non-lawyer eyes but I suggest asking the IETF Trust > to ask their lawyer (who I assure you is very geek-friendly) if it's OK. > > Regards > Brian > > On 22/07/2016 20:33, Yaron Sheffer wrote: >> On 22/07/16 09:51, Brian E Carpenter wrote: >>> On 22/07/2016 19:45, Michael Richardson wrote: >>>> >>>> Dale R. Worley wrote: >>>> > Michael Richardson writes: >>>> >> Is there a suggested LICENSE.txt for internet-drafts repos that live on >>>> >> github (or elsewhere)? >>>> >>>> > I think the boilerplate of each I-D contains the copyright/licensing >>>> > information for the I-D. For instance, >>>> >>>> Yes, but it's not physically in the .xml file until you run xml2rfc on it. >>>> So someone has a reasonable reason to be confused if they see a git repo >>>> that hasn't got a generated .txt file in it. >>> >>> IANAL and YANAL either. So I suggest that LICENSE.txt should simply >>> point to the IETF Trust legal provisions: >>> http://trustee.ietf.org/trust-legal-provisions.html >>> >>> Brian >>> >> >> Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE.md >> >> I copied two sections from the current I-D boilerplate, Status and Copyright, with tiny editorial changes (plural documents >> instead of singular). I think it is important that "users" should know what I-Ds are, hence the Status. >> >> Thanks, >> Yaron >> From nobody Fri Jul 22 03:09:36 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7BAA12DF5E for ; Fri, 22 Jul 2016 03:09:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=queuefull.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GTPpyonKpi1l for ; Fri, 22 Jul 2016 03:09:32 -0700 (PDT) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FF1E12DF5C for ; Fri, 22 Jul 2016 03:09:32 -0700 (PDT) Received: by mail-yw0-x231.google.com with SMTP id u134so98468791ywg.3 for ; Fri, 22 Jul 2016 03:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=queuefull.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nGKs0rVdxBGBXa/KHSPNGvX25DIUqGCkFxfC26KPpNI=; b=O/vrVLkPy913uR5oVCwa2w5J4rzT7ojxKik/WEmuDloDXM8iWcpxmL88UB09j+8voD EOWVNzQry644djAP8alY9m5HlO6/b//MwmCQwezYWqxdkiR3VLtPSlxABb5V5/6BqTS4 uimbkfO2iBvkH6aDBvF6X/5tNRT3C53uBRBbg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nGKs0rVdxBGBXa/KHSPNGvX25DIUqGCkFxfC26KPpNI=; b=JIi273BIjqTN9Ro3eYR5cLXRFWow9o6Uxyz0kw0xOlz/mGfbu37EAYawe1FRtHhox4 kPdtGtcJZkO+NMZDUPJe36cLfHuKgKhTAjqyrjcwk4UINCtJxh4aeyR2B+GD9KrYEhgS d8QycoMSFXt84PJoErm8wDMF4zuVgcPIJve800riEP9Cp9EEp0JQxP07lT70Haf90DT/ ZmYMo2vhZlNnZ8hGuyxViCqObobDQczo+dLYREXRpFrcr5sTgfCtxsziwOwgIaqy4Cts 1eiO+L2JbTGHdlakY7UM9guzHXny19Ds2yIP4D8eOwonDB13QEcQ6fohEjxFghf4MBTJ 3nyQ== X-Gm-Message-State: AEkoouvqr9cjlVEX4bZWdkK/9tffxieZDFb2ejjUNhSb2+wSe/CYY7fqOCOq6ID8p/eDVZbHt+nocM7+ZdOROQ== X-Received: by 10.37.229.65 with SMTP id c62mr2225291ybh.96.1469182171510; Fri, 22 Jul 2016 03:09:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.154.138 with HTTP; Fri, 22 Jul 2016 03:09:30 -0700 (PDT) In-Reply-To: <86d295de-d3bc-d574-9c97-70e0b622ee44@gmail.com> References: <87bn21xr1q.fsf@hobgoblin.ariadne.com> <27031.1469173507@obiwan.sandelman.ca> <7e3ec4d1-a77e-1820-cf09-fae9e188ed67@gmail.com> <30364262-3cb0-095c-87f9-e9f218d8b02b@gmail.com> <86d295de-d3bc-d574-9c97-70e0b622ee44@gmail.com> From: Benson Schliesser Date: Fri, 22 Jul 2016 12:09:30 +0200 Message-ID: To: Yaron Sheffer Content-Type: multipart/alternative; boundary=94eb2c0872c671ad84053836a14a Archived-At: Cc: "tools-discuss@ietf.org" Subject: Re: [Tools-discuss] LICENSE.txt file to IDs on github X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 10:09:35 -0000 --94eb2c0872c671ad84053836a14a Content-Type: text/plain; charset=UTF-8 Hi, Yaron - I'm a Trustee of the IETF Trust. (See http://trustee.ietf.org/members.html for the full list.) I'll bring this discussion to the attention of the Trust and our legal counsel, and get back to you and the list when we have something helpful to say. In the meantime please feel welcome to contact me (or any of the Trustees) with any questions or input. Cheers, -Benson On Friday, July 22, 2016, Yaron Sheffer wrote: > Hi Brian, > > Could you please connect me to the relevant people? I will then share the > outcome with this list. > > Thanks, > Yaron > > On 22/07/16 11:52, Brian E Carpenter wrote: > >> Yaron, >> >> That looks OK to my non-lawyer eyes but I suggest asking the IETF Trust >> to ask their lawyer (who I assure you is very geek-friendly) if it's OK. >> >> Regards >> Brian >> >> On 22/07/2016 20:33, Yaron Sheffer wrote: >> >>> On 22/07/16 09:51, Brian E Carpenter wrote: >>> >>>> On 22/07/2016 19:45, Michael Richardson wrote: >>>> >>>>> >>>>> Dale R. Worley wrote: >>>>> > Michael Richardson writes: >>>>> >> Is there a suggested LICENSE.txt for internet-drafts repos that >>>>> live on >>>>> >> github (or elsewhere)? >>>>> >>>>> > I think the boilerplate of each I-D contains the >>>>> copyright/licensing >>>>> > information for the I-D. For instance, >>>>> >>>>> Yes, but it's not physically in the .xml file until you run xml2rfc on >>>>> it. >>>>> So someone has a reasonable reason to be confused if they see a git >>>>> repo >>>>> that hasn't got a generated .txt file in it. >>>>> >>>> >>>> IANAL and YANAL either. So I suggest that LICENSE.txt should simply >>>> point to the IETF Trust legal provisions: >>>> http://trustee.ietf.org/trust-legal-provisions.html >>>> >>>> Brian >>>> >>>> >>> Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE.md >>> >>> I copied two sections from the current I-D boilerplate, Status and >>> Copyright, with tiny editorial changes (plural documents >>> instead of singular). I think it is important that "users" should know >>> what I-Ds are, hence the Status. >>> >>> Thanks, >>> Yaron >>> >>> > -- > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss > > Please report datatracker.ietf.org bugs at > http://tools.ietf.org/tools/ietfdb > or send email to datatracker-project@ietf.org > > Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or > send email to webmaster@tools.ietf.org > --94eb2c0872c671ad84053836a14a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Yaron -

I'm a=C2=A0Trustee of the I= ETF Trust. (See=C2=A0http:= //trustee.ietf.org/members.html=C2=A0for the full list.)

=
I'll bring this discussion=C2=A0to the attention of the Trus= t and our legal counsel, and get back to you and the list when we have some= thing helpful to say.=C2=A0

In the meantime please= feel welcome to contact me (or any of the Trustees)=C2=A0with any question= s or input.

Cheers,
-Benson

On Friday, July 22, 2016, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
Hi Brian,

Could you please connect me to the relevant people? I will then share the o= utcome with this list.

Thanks,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Yaron

On 22/07/16 11:52, Brian E Carpenter wrote:
Yaron,

That looks OK to my non-lawyer eyes but I suggest asking the IETF Trust
to ask their lawyer (who I assure you is very geek-friendly) if it's OK= .

Regards
=C2=A0 =C2=A0 Brian

On 22/07/2016 20:33, Yaron Sheffer wrote:
On 22/07/16 09:51, Brian E Carpenter wrote:
On 22/07/2016 19:45, Michael Richardson wrote:

Dale R. Worley <worley@ariadne.com> wrote:
=C2=A0 =C2=A0 > Michael Richardson <mcr+ietf@sandelman.ca> = writes:
=C2=A0 =C2=A0 >> Is there a suggested LICENSE.txt for internet-drafts= repos that live on
=C2=A0 =C2=A0 >> github (or elsewhere)?

=C2=A0 =C2=A0 > I think the boilerplate of each I-D contains the copyrig= ht/licensing
=C2=A0 =C2=A0 > information for the I-D.=C2=A0 For instance,

Yes, but it's not physically in the .xml file until you run xml2rfc on = it.
So someone has a reasonable reason to be confused if they see a git repo that hasn't got a generated .txt file in it.

IANAL and YANAL either. So I suggest that LICENSE.txt should simply
point to the IETF Trust legal provisions:
http://trustee.ietf.org/trust-legal-provisions.html

=C2=A0 =C2=A0 Brian


Here's a try: https://github.com/yaronf/I-D/blob/master/LICENSE= .md

I copied two sections from the current I-D boilerplate, Status and Copyrigh= t, with tiny editorial changes (plural documents
instead of singular). I think it is important that "users" should= know what I-Ds are, hence the Status.

Thanks,
=C2=A0 =C2=A0 Yaron


--
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report dat= atracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
or send email to datatracker-project@ietf.org

Please report tools.iet= f.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster@tools.ietf.org
--94eb2c0872c671ad84053836a14a-- From nobody Fri Jul 22 03:57:28 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F86C12DCA4 for ; Fri, 22 Jul 2016 03:57:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.9 X-Spam-Level: X-Spam-Status: No, score=-106.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pi_j921ObnH5 for ; Fri, 22 Jul 2016 03:57:22 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7162412DF6A for ; Fri, 22 Jul 2016 03:57:22 -0700 (PDT) Received: from [2001:67c:370:176:fdd5:400d:79a:ee58] (port=52238) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1bQY8u-0006ak-HD; Fri, 22 Jul 2016 03:57:21 -0700 Message-ID: <5791FC10.3080608@levkowetz.com> Date: Fri, 22 Jul 2016 12:57:20 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Brian E Carpenter , Benjamin Kaduk , tools-discuss@ietf.org References: <57912E1C.5050703@levkowetz.com> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dXMBF3hBHROIWucpvfiSR4PEWWIlrWq03" X-SA-Exim-Connect-IP: 2001:67c:370:176:fdd5:400d:79a:ee58 X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, kaduk@MIT.EDU, brian.e.carpenter@gmail.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) Archived-At: Subject: Re: [Tools-discuss] finding expired documents related to a WG X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 10:57:26 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dXMBF3hBHROIWucpvfiSR4PEWWIlrWq03 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-07-22 07:18, Brian E Carpenter wrote: > What's wrong with this? >=20 > https://datatracker.ietf.org/doc/search/?name=3D&sort=3D&rfcs=3Don&acti= vedrafts=3Don&olddrafts=3Don&by=3Dgroup&group=3Dkitten >=20 > In other words use the Additional search criteria in the tracker search= That gets you some matches, but not all that the draft-*-kitten- pattern finds. It misses drafts which haven't been marked as belonging to the kitten WG. A couple attempts gave me this, however: https://datatracker.ietf.org/doc/search/?name=3D-kitten-&sort=3D&rfcs=3Do= n&activedrafts=3Don&olddrafts=3Don&by=3Dgroup&group=3D To get there, use the search string "-kitten-" and ask for RFCs, drafts, and expired drafts in the Additional search criteria, Best regards, Henrik > Regards > Brian Carpenter > (Don't blame me, I voted Remain.) >=20 >=20 >=20 > On 22/07/2016 08:18, Henrik Levkowetz wrote: >> Hi Ben, >>=20 >> On 2016-07-21 21:55, Benjamin Kaduk wrote: >>> Hi all, >>> >>> Barry says that you want us to stop using the tools wg pages in favor= of >>> the datatracker. >>=20 >> Well, I want to make the datatracker good enough that you don't feel a= >> need to use the tools pages. I'm still happy to maintain them without= >> having any sunset date, but I'd love to make the datatracker even bett= er >> than what I made the tools pages. >>=20 >>> One thing that I currently use the tools page for is to >>> find individual documents related to the kitten WG -- kitten tends to= move >>> rather slowly, so there are a lot of documents more than 6 months old= that >>> are still of interest. >>=20 >> Aha; right. >>=20 >>> The tools page currently has a link "to see all >>> kitten-related documents, go to kitten-related drafts in the ID-archi= ve"), >>> which works pretty well. Is there a similar thing on the datatracker= , or >>> could there be? >>=20 >> Hah. That's a document search feature which isn't available in the da= ta- >> tracker yet. Ok! I'll see what I can do. >>=20 >> This is the kind of feedback which is very valuable in bringing the da= ta- >> tracker forward :-) >>=20 >>> (I have some vague memory that the tools page used to actually show m= ore >>> documents inline instead of that link, but can't really substantiate >>> that.) >>=20 >> I think that I at some point changed things from showing all related >> documents going back 2 (or maybe 3) years, to only showing related act= ive >> and replaced documents. This was done on request, and I believe I add= ed >> the link to all related documents at that time, to support people look= ing >> for expired related documents. >>=20 >>=20 >> Best regards, >>=20 >> Henrik >>=20 >>=20 >>=20 >>=20 >=20 --dXMBF3hBHROIWucpvfiSR4PEWWIlrWq03 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJXkfwQAAoJEE6bV0uPuxcaD9gP/0DbnYkp4qZUzxQ9LN8WCp9C wK0QZk3HKfS8NsDQfZtha0fwBBsrflBDHx5bVOtJRUu4V3X/gjAPgV21aVuNYcVX F3QKDIeteTp3SRmG05Q7OjMbmxnHDbOUDioe2vHHgXjyNFA6aHhHVFL2CAYxXwP9 d4e8BYDY4TIHiQnNV18F4P8OuhYBRGMQ72mrng04ypP5Igs/CrdUq23TuOarto1m Rtu3dZwHhdpQ2XZjgF6m7K0iQSlehSY6bl97ZciEEmqmTRB1bv8LQ7S6LIncgdjQ 2A3+YZjibJoyOLT5e0+AUl5Wqy8yu0TfnUIHMibr0nwaQg4Jwnpwd9kCdOzfWhqL 5v4Sg4SU/BfnBk1EvX+Y0scD59PkIAJstTdxjlxCTJXx6BOv9Xfk+bHnV0MRg+Lw 57yWbRBWZ+F2I5UOrZtuvOnGIWJDuRVvnYLThcGYnbA6EWhe+EYXggDiGTQGJGn3 bOOYQtbcCjaxTPXCuNDtK6SGQIWf0gCv1s38Xc0EUc4gZu1RPRG3lGtKpoassjk5 otPsAYKlAr1TA9xKqKSiwBVA76LX3TKf/8fxdKI1q6wTOxmCiBsoRglgEIj/Rflr US9ulE/B7tvkblUH+DDhC2j9R71rsJU/ijfJgI2+bu7XlARv2pWqvPr10TUgj1R5 gvKUZdEhFlBt6lcXctB5 =Ttxl -----END PGP SIGNATURE----- --dXMBF3hBHROIWucpvfiSR4PEWWIlrWq03-- From nobody Sun Jul 24 06:03:39 2016 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBFB812D185 for ; Sun, 24 Jul 2016 06:03:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKdxLVDctefy for ; Sun, 24 Jul 2016 06:03:34 -0700 (PDT) Received: from denver.dinauz.org (denver.dinauz.org [37.59.56.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 056BA12D0CD for ; Sun, 24 Jul 2016 06:03:33 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id D7E2B6047D for ; Sun, 24 Jul 2016 15:03:31 +0200 (CEST) Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-v0uAPLetHx for ; Sun, 24 Jul 2016 15:03:31 +0200 (CEST) Received: from macbook-pro-de-julien-elie.home (2a01cb080103c800446efa79e037a1e1.ipv6.abo.wanadoo.fr [IPv6:2a01:cb08:103:c800:446e:fa79:e037:a1e1]) by denver.dinauz.org (Postfix) with ESMTPSA id AE8536047C for ; Sun, 24 Jul 2016 15:03:31 +0200 (CEST) To: tools-discuss@ietf.org From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: Date: Sun, 24 Jul 2016 15:03:31 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: [Tools-discuss] Rfcmarkup-1.118 feedback X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 13:03:37 -0000 Hi, HTML markup does not work fine with multi-line titles. For instance: https://tools.ietf.org/html/draft-murchison-nntp-compress-05 the second line for Appendix B is not in the element: Appendix B. Document History (to be removed by RFC Editor before publication) While I'm at it, I noticed two other things: * Is the date normal? I thought it would be the publication date of the Internet-Draft. * How the text "commands from the client are indicated with [C]" (in Section 1.2) is supposed to be written? A reference is automatically put for [C] though there should not be any. Afterwards in the document, all the uses of "[C]" are converted to "[C]". Should I use HTML entities to write "[" and "]"? It wouldn't be convenient at all, though. And why the text "responses from the server are indicated with [S]" does not result in a similar reference for [S]? Incidentally, the URL of the tools-discuss ml archives does not work. https://www.ietf.org/mailman/listinfo/tools-discuss gives a link to www1.ietf.org in the first section (instead of www.ietf.org). -- Julien ÉLIE « – Tu n'as rien remarqué d'étrange chez cet Arverne ? – Oui, son accent. » (Astérix)