From nobody Mon Jun 1 19:19:36 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1062C1A89E9 for ; Mon, 1 Jun 2015 19:19:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 T9xFYFSyX3sn for ; Mon, 1 Jun 2015 19:19:32 -0700 (PDT) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (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 606CA1A89C6 for ; Mon, 1 Jun 2015 19:19:32 -0700 (PDT) Received: by pdbqa5 with SMTP id qa5so121603185pdb.0 for ; Mon, 01 Jun 2015 19:19:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=T9aYIWiMUWptW+OKVXyAbh0k7s3Qt4NuYm/NOJxFKJI=; b=MqNvWrwvLzFep7IMQ0gHBoKmHM/zQ0Ct1t5gMlzcZEbEGcUffqSaI+hfn9RQEgIACH T7M5Dk6PGhObzxtf6DWNGGiK8JzzWtcRwg4D8jCFEPl3/TvLzKhrWb8AxQIOkiKEVl5y Fs3wDT3VYYKkE9Q8m508N4+GK57HYLNm2cpOKryT1ruiRv3EfN3xxqUPN8+iZmiACDpx M+btQhwm6w/Zsl5R/jlkUUn//eMPs+/MdmVSw5l5pNEaRpYsd4/HSoBcNahlPTK35skj 7pmCapX2WaI+2w5QTTLAK7bJd8yToDwgd6YjHSntoyV9yI4fRjARBRlonA8uz79ESieA S7wg== X-Gm-Message-State: ALoCoQm6rYOzyMBIe4h+zfcadnou3NPPoyb/Vt34I5SrQu5Yo2ausIPkqRJITGiciyG3M4i0YPyR X-Received: by 10.68.68.175 with SMTP id x15mr8059283pbt.91.1433211571886; Mon, 01 Jun 2015 19:19:31 -0700 (PDT) Received: from fallout-2.local ([12.207.20.2]) by mx.google.com with ESMTPSA id mb4sm15901183pdb.63.2015.06.01.19.19.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jun 2015 19:19:30 -0700 (PDT) Message-ID: <556D12D4.4050208@queuefull.net> Date: Mon, 01 Jun 2015 19:20:04 -0700 From: Benson Schliesser User-Agent: Postbox 4.0.1 (Macintosh/20150514) MIME-Version: 1.0 To: "tools-discuss@ietf.org" References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [Tools-discuss] Proposed Statement on "HTTPS everywhere for the IETF" X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2015 02:19:34 -0000 Reading the IESG statement on HTTPS Everywhere (link forwarded below), something remains unclear to me. I'm hopeful that somebody on this list has an informed view of this question. Otherwise I can ask on the IETF list. My overall impression is that the IESG's intent is to go beyond simply making everything available via HTTPS, and to actually make everything *default* to HTTPS so that it is the preferred mechanism. In specific practice, I could imagine this as something like 1) redirect HTTP gets of the web root to the HTTPS equivalent, and 2) change tools and documents so that all embedded links are HTTPS. However the IESG statement also says that people and/or tools that wish to use HTTP will continue to be able to do so. Is this as simple as just making everything simultaneously available via HTTP? I note that this would potentially require the client to translate embedded links from HTTPS back to HTTP. Or is something more complicated required, such as a per-user setting (profile, cookie, or whatever), webhost regex, client request header, etc? It's not entirely clear to me how we are going to implement this. Has somebody already figured this out? I'd be glad to learn that the answer is obvious and simple, and that my question is naive. Thanks, -Benson ---------- Forwarded message ---------- From: *The IESG* > Date: Mon, Jun 1, 2015 at 12:43 PM Subject: Proposed Statement on "HTTPS everywhere for the IETF" To: IETF Announcement List > Hi All, The IESG are planning to agree an IESG statement on "HTTPS Everywhere for the IETF," please see [1] for the current text. We are seeking community feedback on this and welcome assistance from the community in identifying any cases where a change or additional guidance is needed to put this into effect. The IESG plans to finalise this statement just after IETF-93 in Prague. * Please send general feedback intended for discussion to ietf@ietf.org * Comments about specific issues arising can be sent to iesg@ietf.org or tools-discuss@ietf.org as appropriate (use iesg@ietf.org if not sure) Regards, Terry & Stephen (for the IESG) [1] https://trac.tools.ietf.org/group/iesg/trac/wiki/HttpsEverywhere From nobody Mon Jun 1 19:25:28 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAF21A8A39 for ; Mon, 1 Jun 2015 19:25:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.895 X-Spam-Level: X-Spam-Status: No, score=0.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 ZM13SjSNFFye for ; Mon, 1 Jun 2015 19:25:25 -0700 (PDT) Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id B5BC41A89F5 for ; Mon, 1 Jun 2015 19:25:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 9FCA41E16521; Mon, 1 Jun 2015 22:25:23 -0400 (EDT) X-Virus-Scanned: amavisd-new at sobco.com Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ByNKjjJiCdip; Mon, 1 Jun 2015 22:25:22 -0400 (EDT) Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id B608C1E16515; Mon, 1 Jun 2015 22:25:22 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: "Scott O. Bradner" In-Reply-To: <556D12D4.4050208@queuefull.net> Date: Mon, 1 Jun 2015 22:25:23 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556D12D4.4050208@queuefull.net> To: Benson Schliesser X-Mailer: Apple Mail (2.2098) Archived-At: Cc: "tools-discuss@ietf.org" Subject: Re: [Tools-discuss] Proposed Statement on "HTTPS everywhere for the IETF" X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2015 02:25:27 -0000 the statement seems contradictory if they are going to redirect http to https then the =E2=80=9Ccan keep using http=E2=80=9D does not make much sense Jari? Scott > On Jun 1, 2015, at 10:20 PM, Benson Schliesser = wrote: >=20 > Reading the IESG statement on HTTPS Everywhere (link forwarded below), = something remains unclear to me. I'm hopeful that somebody on this list = has an informed view of this question. Otherwise I can ask on the IETF = list. >=20 > My overall impression is that the IESG's intent is to go beyond simply = making everything available via HTTPS, and to actually make everything = *default* to HTTPS so that it is the preferred mechanism. In specific = practice, I could imagine this as something like 1) redirect HTTP gets = of the web root to the HTTPS equivalent, and 2) change tools and = documents so that all embedded links are HTTPS. >=20 > However the IESG statement also says that people and/or tools that = wish to use HTTP will continue to be able to do so. Is this as simple as = just making everything simultaneously available via HTTP? I note that = this would potentially require the client to translate embedded links = from HTTPS back to HTTP. Or is something more complicated required, such = as a per-user setting (profile, cookie, or whatever), webhost regex, = client request header, etc? >=20 > It's not entirely clear to me how we are going to implement this. Has = somebody already figured this out? I'd be glad to learn that the answer = is obvious and simple, and that my question is naive. >=20 > Thanks, > -Benson >=20 >=20 >=20 > ---------- Forwarded message ---------- > From: *The IESG* > > Date: Mon, Jun 1, 2015 at 12:43 PM > Subject: Proposed Statement on "HTTPS everywhere for the IETF" > To: IETF Announcement List > >=20 >=20 > Hi All, >=20 > The IESG are planning to agree an IESG statement on "HTTPS Everywhere > for the IETF," please see [1] for the current text. >=20 > We are seeking community feedback on this and welcome assistance > from the community in identifying any cases where a change or > additional guidance is needed to put this into effect. >=20 > The IESG plans to finalise this statement just after IETF-93 in = Prague. >=20 > * Please send general feedback intended for discussion to = ietf@ietf.org >=20 > * Comments about specific issues arising can be sent to iesg@ietf.org = > or tools-discuss@ietf.org = as appropriate = (use iesg@ietf.org if = not sure) >=20 > Regards, > Terry & Stephen (for the IESG) >=20 > [1] https://trac.tools.ietf.org/group/iesg/trac/wiki/HttpsEverywhere >=20 >=20 > --=20 > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 > Please report datatracker.ietf.org bugs at = http://tools.ietf.org/tools/ietfdb > Please report tools.ietf.org bugs at = http://tools.ietf.org/tools/issues or > send email to webmaster@tools.ietf.org From nobody Tue Jun 2 12:59:50 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 545C71A1B86 for ; Tue, 2 Jun 2015 12:59:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham 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 Iehn1QTM8SNP for ; Tue, 2 Jun 2015 12:59:45 -0700 (PDT) Received: from mail-yk0-x236.google.com (mail-yk0-x236.google.com [IPv6:2607:f8b0:4002:c07::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 47FBD1B2BE4 for ; Tue, 2 Jun 2015 12:58:54 -0700 (PDT) Received: by ykfl8 with SMTP id l8so57179873ykf.1 for ; Tue, 02 Jun 2015 12:58:53 -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 :cc:content-type:content-transfer-encoding; bh=wWE7jNI+6opR0UuUyo5jEpgTJG1q+qeEA/BnPf0gaw8=; b=FYo8GghNa9ThZmwJJjmvGAKb4CQmss+uP2sD1wjnTh1qHaJPNsdN48BrylaeYhYqct +LiKoh3bqqn8kOP5knST6XoR7VzcQj5U2O2Z/O2dRcGZewSSporIEqLtYzZeX8L/9l0h 6tp60uCqa1P4SXx44+5l/pLX5QVGFGgYno6RXlReVVx5xDUOVCcBtuKGrxc5+sh8pBqE 0Sn7xTDzgYwQjs7iKH6urcp0O4zWBlPaB1wgD0a5nozGATw/oci/lyI7++UEYUuulDd+ zZ/66hd3EbMovdZAASJHLBtFc3GqA1vNzb08fn5q9hVTeEa+I/V8l4329tq4cYyCDT5T Fliw== MIME-Version: 1.0 X-Received: by 10.236.28.75 with SMTP id f51mr31268506yha.93.1433275133681; Tue, 02 Jun 2015 12:58:53 -0700 (PDT) Received: by 10.129.110.138 with HTTP; Tue, 2 Jun 2015 12:58:53 -0700 (PDT) In-Reply-To: References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556D12D4.4050208@queuefull.net> Date: Tue, 2 Jun 2015 12:58:53 -0700 Message-ID: From: Martin Thomson To: "Scott O. Bradner" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Archived-At: Cc: "tools-discuss@ietf.org" Subject: Re: [Tools-discuss] Proposed Statement on "HTTPS everywhere for the IETF" X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2015 19:59:49 -0000 On 1 June 2015 at 19:25, Scott O. Bradner wrote: > the statement seems contradictory > > if they are going to redirect http to https > then the =E2=80=9Ccan keep using http=E2=80=9D does not make much sense My understanding was: a) all services will be provided over https b) "public" services will be provided over http (for some definition of public that probably needs extra work) From nobody Tue Jun 2 14:13:10 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B73BD1B3094 for ; Tue, 2 Jun 2015 14:13:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 imE6wdFPsoNe for ; Tue, 2 Jun 2015 14:13:03 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 89A121B2F55 for ; Tue, 2 Jun 2015 14:13:03 -0700 (PDT) Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t52LD17A026007 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 2 Jun 2015 16:13:02 -0500 (CDT) (envelope-from adam@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local Message-ID: <556E1C5D.4010503@nostrum.com> Date: Tue, 02 Jun 2015 16:13:01 -0500 From: Adam Roach User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Benson Schliesser , "tools-discuss@ietf.org" References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556D12D4.4050208@queuefull.net> In-Reply-To: <556D12D4.4050208@queuefull.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] Proposed Statement on "HTTPS everywhere for the IETF" X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2015 21:13:07 -0000 On 6/1/15 21:20, Benson Schliesser wrote: > 2) change tools and documents so that all embedded links are HTTPS Incidentally, you can have constructs like this: Submit a draft This link will use https: if it is in an https: page, and http: if it is in an http: page. /a From nobody Tue Jun 2 17:08:43 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F6C51B322B for ; Tue, 2 Jun 2015 17:08:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 GVyrtqqsRkgN for ; Tue, 2 Jun 2015 17:08:40 -0700 (PDT) Received: from webspace.isi.edu (webspace.isi.edu [128.9.64.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B3B01B321A for ; Tue, 2 Jun 2015 17:08:40 -0700 (PDT) Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id t53089pb014579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 2 Jun 2015 17:08:10 -0700 (PDT) Message-ID: <556E4567.8030902@isi.edu> Date: Tue, 02 Jun 2015 17:08:07 -0700 From: Joe Touch User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Adam Roach , Benson Schliesser , "tools-discuss@ietf.org" References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556D12D4.4050208@queuefull.net> <556E1C5D.4010503@nostrum.com> In-Reply-To: <556E1C5D.4010503@nostrum.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Archived-At: Subject: Re: [Tools-discuss] Proposed Statement on "HTTPS everywhere for the IETF" X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 00:08:41 -0000 On 6/2/2015 2:13 PM, Adam Roach wrote: > On 6/1/15 21:20, Benson Schliesser wrote: >> 2) change tools and documents so that all embedded links are HTTPS > > Incidentally, you can have constructs like this: > > Submit a draft > > This link will use https: if it is in an https: page, and http: if it is > in an http: page. It's known as a "protocol relative URL", and referred to in RFC3986 as a network-path reference. It's a variant of relative reference (e.g., "/goo.html" or "bah/goo.html", except that it also includes the network path too. Joe From nobody Tue Jun 2 18:12:20 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E3ED1B2F04 for ; Tue, 2 Jun 2015 18:12:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 X6Zc3n0jPqqh for ; Tue, 2 Jun 2015 18:12:17 -0700 (PDT) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) (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 73C0A1A8737 for ; Tue, 2 Jun 2015 18:12:17 -0700 (PDT) Received: by qczw4 with SMTP id w4so42845361qcz.2 for ; Tue, 02 Jun 2015 18:12:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=j8L5fL/QmMcj5QXE7u8k+KoqB+QfIA63CPTtg/YT+L4=; b=OakMHO0YVhrjAVlKPa8oq9YWneb27gsRQ0zdaLll32UR9CR/lPuvhj266wQuJD71/d Q1auGst7KTeuMdAy+emJXjkccAnmmx84mC0fnG+GJf8H0ZE4aMy7eT8uAWw9aInMAfCD 5lkoeV1EyVqKnRfh3yrEE40jXqcTUcy7MP6QFYpDU6TeCxVjZ+2EjbPiBCRPnPGCYSWN 7k+UvoiThqH36t9E1HVT4BonQyRBQJoln73tgUlqFy/GXBkLVEQaUWXt74fOA4MJFrDY GeLjKbFsCVemTCaqiohso4XxXSXIylcrCjyhbrokJ9/SFDtETineP3mU+yEXZflg2XIf KO7w== X-Gm-Message-State: ALoCoQlbG0nK6gOfpzTVNa7FeuZ8FeYDfegqX4hFRgHPkSiv3tthe+/NwYaYxYRv5sbACF/ETUM2 X-Received: by 10.140.36.137 with SMTP id p9mr32001028qgp.16.1433293936740; Tue, 02 Jun 2015 18:12:16 -0700 (PDT) Received: from fallout-2.local ([12.207.20.2]) by mx.google.com with ESMTPSA id 9sm8193530qhy.1.2015.06.02.18.12.15 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Jun 2015 18:12:16 -0700 (PDT) Message-ID: <556E5490.2030409@queuefull.net> Date: Tue, 02 Jun 2015 18:12:48 -0700 From: Benson Schliesser User-Agent: Postbox 4.0.1 (Macintosh/20150514) MIME-Version: 1.0 To: Adam Roach , "tools-discuss@ietf.org" , Stephen Farrell References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556D12D4.4050208@queuefull.net> <556E1C5D.4010503@nostrum.com> In-Reply-To: <556E1C5D.4010503@nostrum.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] Proposed Statement on "HTTPS everywhere for the IETF" X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 01:12:19 -0000 Adam Roach wrote: > On 6/1/15 21:20, Benson Schliesser wrote: >> 2) change tools and documents so that all embedded links are HTTPS > > Incidentally, you can have constructs like this: > > Submit a draft > > This link will use https: if it is in an https: page, and http: if it is > in an http: page. Yes. Off the cuff, I sort of feel like we should generally be using relative links anyway. I suspect that the #2 in my previous message (which is quoted above) would probably break stuff. Use of relative links seem like a better choice. Building on this, would it be safe to redirect some set of HTTP requests to HTTPS? I'm thinking specifically of things like the web root where users might naturally navigate, and I'm assuming that we wouldn't want to do this for more specific URLs. Further, I personally don't know nearly enough about these technologies, but I imagine that we should look into the use of upgrade-insecure-requests [1] and HSTS [2]. Finally, I noticed a message on the IETF list [3] in which Stephen Farrell says he's keeping a list of things we should do... So now I'm looking forward to seeing that list and hearing more feedback from this community. Cheers, -Benson [1] - http://www.w3.org/TR/upgrade-insecure-requests/ [2] - http://tools.ietf.org/html/rfc6797 [3] - https://www.ietf.org/mail-archive/web/ietf/current/msg93300.html From nobody Wed Jun 3 01:11:35 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6659A1B361F for ; Wed, 3 Jun 2015 01:11:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 M_n1cwYFn1V0 for ; Wed, 3 Jun 2015 01:11:31 -0700 (PDT) Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD7B41B3616 for ; Wed, 3 Jun 2015 01:11:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 33DF0BF02; Wed, 3 Jun 2015 09:11:28 +0100 (IST) Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3vIhlCVA6-PS; Wed, 3 Jun 2015 09:11:28 +0100 (IST) Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id F3F49BEFE; Wed, 3 Jun 2015 09:11:27 +0100 (IST) Message-ID: <556EB6AD.7050509@cs.tcd.ie> Date: Wed, 03 Jun 2015 09:11:25 +0100 From: Stephen Farrell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Benson Schliesser , Adam Roach , "tools-discuss@ietf.org" References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556D12D4.4050208@queuefull.net> <556E1C5D.4010503@nostrum.com> <556E5490.2030409@queuefull.net> In-Reply-To: <556E5490.2030409@queuefull.net> OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Tools-discuss] Proposed Statement on "HTTPS everywhere for the IETF" X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 08:11:34 -0000 Hiya, (note: I'm not on tools-discuss. I've read this thread in the archive, but please do cc me if needed) On 03/06/15 02:12, Benson Schliesser wrote: > > Adam Roach wrote: >> On 6/1/15 21:20, Benson Schliesser wrote: >>> 2) change tools and documents so that all embedded links are HTTPS >> >> Incidentally, you can have constructs like this: >> >> Submit a draft >> >> This link will use https: if it is in an https: page, and http: if it is >> in an http: page. > > Yes. Off the cuff, I sort of feel like we should generally be using > relative links anyway. I suspect that the #2 in my previous message > (which is quoted above) would probably break stuff. Use of relative > links seem like a better choice. Yep. > > Building on this, would it be safe to redirect some set of HTTP requests > to HTTPS? I'm thinking specifically of things like the web root where > users might naturally navigate, and I'm assuming that we wouldn't want > to do this for more specific URLs. > > Further, I personally don't know nearly enough about these technologies, > but I imagine that we should look into the use of > upgrade-insecure-requests [1] and HSTS [2]. Right, there's a bit of figuring out to be done wrt HSTS and the various (sub)domains we operate. > Finally, I noticed a message on the IETF list [3] in which Stephen > Farrell says he's keeping a list of things we should do... So now I'm > looking forward to seeing that list and hearing more feedback from this > community. Yep, I'll do that in a few days. Right now I just have the raw comments, but I'll try organise 'em a bit before making that list available. Cheers, S. > > Cheers, > -Benson > > [1] - http://www.w3.org/TR/upgrade-insecure-requests/ > [2] - http://tools.ietf.org/html/rfc6797 > [3] - https://www.ietf.org/mail-archive/web/ietf/current/msg93300.html > From nobody Wed Jun 10 06:46:20 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6154E1B2A32; Wed, 10 Jun 2015 06:46:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.911 X-Spam-Level: X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 s6OOnmxD_3Sy; Wed, 10 Jun 2015 06:46: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 229071B2A31; Wed, 10 Jun 2015 06:46:17 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8DBA3E00C; Wed, 10 Jun 2015 10:00:38 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 228A763B10; Wed, 10 Jun 2015 09:46:16 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 0F2BB637FE; Wed, 10 Jun 2015 09:46:16 -0400 (EDT) From: Michael Richardson To: tools-discuss@ietf.org, netconf@ietf.org X-Attribution: mcr X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2 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 Sender: mcr@sandelman.ca Archived-At: Subject: [Tools-discuss] extracting yang models from RFC X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 13:46:19 -0000 --=-=-= Content-Type: text/plain Please excuse me if this is a FAQ, but a scan of 6020 didn't reveal any advice. I'm also mostly ignorant of MIB or YANG authoring, I'm just trying to help get a more consistent experience. I know that we have tools to extract MIBs from RFCs, and I assume that we have the same for YANG models. I also googled for "how to format yang model in rfc", and I looked at: https://tools.ietf.org/wg/netconf/trac/wiki, and looked at: https://mailarchive.ietf.org/arch/search/?q=netconf+how+to+format+yang+in+internet-draft&f_list=netconf What is the recommended way to embed the YANG definition into an ID? Should it be as a single section, with a single
, or should/can it be split up into multiple figures? I'm writing a makefile/sed pipeline to insert the raw .yang file into the XML to reduce editing errors. <> must be escaped as < in , but I'm unaware of any other stuffing that must be done. Probably this is a solved problem... -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEVAwUBVXg/p4CLcPvd0N1lAQITpgf+LeBPoWNqPyjnoBhEvFR8JITF2HDRhi3I NoGFaxXtFoEXrpBFsNZ3/RgUgAGW816CCkN+l/eL0LbRpzUgvakZKRaoG9d5ged8 xW8JsRYh2K5NFfa8u0zuIOJ4SjW9pI8gKNqDVVui+M9W0MNrwnvr5XIjCvWW2XUI aig2udlacZF/iQ7FO5nKes+ko4RUEk2hcVi4TEkKCAG77N15Xanx9KuhwwtndoUC 6K6SN9YAqitrDhsVwftuzaeF/Utv7aItIxYzdsbmmkIqFc49ZFpU5E4D6EiosOx8 hxZEz/Ze3Kavdwo1KVyKalob3kgPzLkUcYGfBRLmvfCZPhp6+KTdgQ== =vUzq -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Jun 10 12:26:31 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 151641A87E7; Wed, 10 Jun 2015 12:26:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.911 X-Spam-Level: X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 YyibOla1d75e; Wed, 10 Jun 2015 12:26:27 -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 5CAC01A8827; Wed, 10 Jun 2015 12:26:27 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C665820098; Wed, 10 Jun 2015 15:40:48 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 24B8263B10; Wed, 10 Jun 2015 15:26:26 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 0B452637FE; Wed, 10 Jun 2015 15:26:26 -0400 (EDT) From: Michael Richardson To: Kent Watsen In-Reply-To: References: <30608.1433943976@sandelman.ca> X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2 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 Sender: mcr@sandelman.ca Archived-At: Cc: "netconf@ietf.org" , "tools-discuss@ietf.org" Subject: Re: [Tools-discuss] [Netconf] extracting yang models from RFC X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 19:26:29 -0000 Kent Watsen wrote: > See rfcstrip located here: > http://www.yang-central.org/twiki/pub/Main/YangTools/rfcstrip > Just do 'rfcstrip ' and you'll get the extracted YANG > modules (and more). okay, sure, I knew such things existed (but I hadn't found it) But, what should I do on the input side of things to make rfcstrip work better? I guess I can round trip it until I get it right... let's try. okay, back to my original question. rfcstrip results in empty output from the ID in question, so I'm back to my original question: what do I put in to make rfcstrip work? (and where is that documented?) -- ] 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 Jun 10 12:29:35 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1F8E1A884C; Wed, 10 Jun 2015 12:29:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.911 X-Spam-Level: X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 flZ0HuQbB0bH; Wed, 10 Jun 2015 12:29:33 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 613FC1A882A; Wed, 10 Jun 2015 12:29:33 -0700 (PDT) Received: from [172.20.10.5] (h194.viagenie.ca [206.123.31.194]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E4A99403C2; Wed, 10 Jun 2015 15:29:34 -0400 (EDT) From: "Marc Blanchet" To: "Michael Richardson" Date: Wed, 10 Jun 2015 15:29:31 -0400 Message-ID: <5BB95C2D-7D3E-439E-AC0E-16493D611560@viagenie.ca> In-Reply-To: <9126.1433964386@sandelman.ca> References: <30608.1433943976@sandelman.ca> <9126.1433964386@sandelman.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate Trial (1.9.1r5084) Archived-At: Cc: Kent Watsen , "netconf@ietf.org" , "tools-discuss@ietf.org" Subject: Re: [Tools-discuss] [Netconf] extracting yang models from RFC X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 19:29:35 -0000 On 10 Jun 2015, at 15:26, Michael Richardson wrote: > Kent Watsen wrote: > > See rfcstrip located here: > > http://www.yang-central.org/twiki/pub/Main/YangTools/rfcstrip > > > Just do 'rfcstrip ' and you'll get the extracted > YANG > > modules (and more). > > okay, sure, I knew such things existed (but I hadn't found it) > But, what should I do on the input side of things to make rfcstrip > work better? > I guess I can round trip it until I get it right... let's try. > > okay, back to my original question. rfcstrip results in empty > output from the ID in question, so I'm back to my original question: > what do > I put in to make rfcstrip work? > (and where is that documented?) interesting. During the discussion on the new RFC format, I stated specifically on the mike that those should be well handled for extraction and formatting (no page headers in the middle…). I haven’t looked at the new proposed format, but I hope it should be « simpler » than now. Marc. > > -- > ] 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 [ > > > > -- > 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 > Please report tools.ietf.org bugs at > http://tools.ietf.org/tools/issues or > send email to webmaster@tools.ietf.org From nobody Wed Jun 10 12:48:47 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF801A87EA; Wed, 10 Jun 2015 12:48:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.911 X-Spam-Level: X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 1AjfnkEq4BXb; Wed, 10 Jun 2015 12:48:43 -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 4C7861A8775; Wed, 10 Jun 2015 12:48:43 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2117FE00C; Wed, 10 Jun 2015 16:03:05 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 6BCDE63B10; Wed, 10 Jun 2015 15:48:42 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 549AC637FE; Wed, 10 Jun 2015 15:48:42 -0400 (EDT) From: Michael Richardson To: "Marc Blanchet" In-Reply-To: <5BB95C2D-7D3E-439E-AC0E-16493D611560@viagenie.ca> References: <30608.1433943976@sandelman.ca> <9126.1433964386@sandelman.ca> <5BB95C2D-7D3E-439E-AC0E-16493D611560@viagenie.ca> X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2 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 Sender: mcr@sandelman.ca Archived-At: Cc: Kent Watsen , "netconf@ietf.org" , "tools-discuss@ietf.org" Subject: Re: [Tools-discuss] [Netconf] extracting yang models from RFC X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 19:48:45 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Marc Blanchet wrote: >> okay, back to my original question. rfcstrip results in empty >> output from the ID in question, so I'm back to my original question: >> what do >> I put in to make rfcstrip work? >> (and where is that documented?) > interesting. During the discussion on the new RFC format, I stated > specifically on the mike that those should be well handled for > extraction and > formatting (no page headers in the middle=E2=80=A6). I haven=E2=80= =99t looked at the new > proposed format, but I hope it should be =C2=AB=C2=A0simpler=C2=A0=C2= =BB than now. I don't know if
is what's in the new format or not. In any case, I'm not at the new format... I'm dealing with the xml2txt workflow. So I wouldn't say there is either success or failure of what you asked for at this point. I'm using xml2rfc 2.4.7 (probably not the absolute latest, but it has worked up to now). I'm assuming, looking at the awk script in the middle of the rfcstrip shell code, that it is looking for "module FOO {" to start. Hmm. I note that this code is not terminated with a } at the exactly same level in the ID.... aha the last line of original file had a }, and no trailing new line, so that very last line was never included. rfcstrip now works, and the round trip is the same except for some extra blank lines added, and slightly different indent on descriptions that cross multiple lines. =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.4.12 (GNU/Linux) iQEVAwUBVXiUmoCLcPvd0N1lAQKk4gf/Y4xZGKGZcKuHUG0o37mweOToyYRBY3v3 UnYT4b1vyaDZtcgRvYzCW1ekmcgnxMKnp/ojjn2LB+pzg35Uvei+DNw70IDShcCf hNzFSphxGO/M96In/90p8VPel/iudjMRB36TImU6yZ1qNkuyxvZ9XgucfFTWAYCo USaWxxuCXlt7/DRYSQdGkmFRduAmFz0FSsVUtJ+pJ6E1MHoG9yoHfqTy1wReu9yD 8MzTPM+M8j0fRWrtFlh+G9laTNSqvc1bOIgr9fiP5gErjGVIPpsh8AR3FGhFM4Yd XAycwlMYh6MQN452U3vBgcOKjDKTEVqQM9gXSp0StrZqjuCNDPEzPQ== =0b59 -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Jun 10 12:54:26 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A008B1A896F; Wed, 10 Jun 2015 12:54:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.347 X-Spam-Level: X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=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 Y48M9_3IY4Br; Wed, 10 Jun 2015 12:54:24 -0700 (PDT) Received: from proper.com (Opus1.Proper.COM [207.182.41.91]) (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 7F6EF1A895B; Wed, 10 Jun 2015 12:54:24 -0700 (PDT) Received: from [10.20.30.109] (142-254-17-100.dsl.dynamic.fusionbroadband.com [142.254.17.100]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t5AJsNNw056839 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Jun 2015 12:54:23 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) X-Authentication-Warning: hoffman.proper.com: Host 142-254-17-100.dsl.dynamic.fusionbroadband.com [142.254.17.100] claimed to be [10.20.30.109] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Paul Hoffman In-Reply-To: <5BB95C2D-7D3E-439E-AC0E-16493D611560@viagenie.ca> Date: Wed, 10 Jun 2015 12:54:22 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <30608.1433943976@sandelman.ca> <9126.1433964386@sandelman.ca> <5BB95C2D-7D3E-439E-AC0E-16493D611560@viagenie.ca> To: Marc Blanchet X-Mailer: Apple Mail (2.2098) Archived-At: Cc: Kent Watsen , "tools-discuss@ietf.org" , "netconf@ietf.org" Subject: Re: [Tools-discuss] [Netconf] extracting yang models from RFC X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 19:54:25 -0000 On Jun 10, 2015, at 12:29 PM, Marc Blanchet = wrote: > interesting. During the discussion on the new RFC format, I stated = specifically on the mike that those should be well handled for = extraction and formatting (no page headers in the middle=E2=80=A6). I = haven=E2=80=99t looked at the new proposed format, but I hope it should = be =C2=AB simpler =C2=BB than now. Much simpler: see the element in = . --Paul Hoffman= From nobody Tue Jun 16 04:46:20 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4AA1A6EE7 for ; Tue, 16 Jun 2015 04:46:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.51 X-Spam-Level: X-Spam-Status: No, score=-9.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham 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 9u00zmkEHwM6 for ; Tue, 16 Jun 2015 04:46:16 -0700 (PDT) Received: from bgl-iport-3.cisco.com (bgl-iport-3.cisco.com [72.163.197.27]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BCBC1A1B74 for ; Tue, 16 Jun 2015 04:46:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4915; q=dns/txt; s=iport; t=1434455176; x=1435664776; h=message-id:date:from:mime-version:to:subject; bh=7Z7F0+8eHSeWb1+uqSIw1LMfBlThQBVu833I5UgaPM8=; b=eQa3SN4xMVDiK9CtVjK0xcJ7y4EvmzhOA2rMZo1eJHuQwM8Mr1YqBZor DO9zq/yh7Ix2MD1IExoEtUSJld5SJRlGzjJpCTSTLwJTJVtk6SQVks7Lm dKm7uRf+7wqm79YUyqIManwevURTw2lhVkDMLctN6FEQc96bVyTAABvOI U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CmBABqC4BV/xjFo0hbg2Rfgx67CYFhh3ESAQEBAQEBAYEKhExLJAYdIQIRAjAQDA0IAQEFiCYNmEqNOo9flnMBAQgBAQEBAR2PeAEBgz+BRQWTX4RShnOBdIYviGiHDSaDezwxAYELgTsBAQE X-IronPort-AV: E=Sophos; i="5.13,626,1427760000"; d="scan'208,217"; a="18307519" Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([72.163.197.24]) by bgl-iport-3.cisco.com with ESMTP; 16 Jun 2015 11:46:13 +0000 Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by bgl-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t5GBkB7d013184 for ; Tue, 16 Jun 2015 11:46:11 GMT Message-ID: <55800C7C.70805@cisco.com> Date: Tue, 16 Jun 2015 13:46:04 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Tools Team Discussion Content-Type: multipart/alternative; boundary="------------000902000909030003000204" Archived-At: Subject: [Tools-discuss] rsync help X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2015 11:46:18 -0000 This is a multi-part message in MIME format. --------------000902000909030003000204 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Dear all, I try to download only the .txt drafts and RFCs. As mentioned at http://www.rfc-editor.org/rsync-help.html, I'm using: * rsync -avz --delete ftp.rfc-editor.org::rfcs-text-only my-rfc-mirror* The issue is that the results contain some .txt.p7s, some .xml extension. What do I do wrong? rsync ftp.rfc-editor.org:: everything-ftp Everything FTP refs References rfcs Contents of in-notes including subdirectories std, bcp, fyi, and ien rfcs-text-only Only the text files from the directories in [rfcs] rfc-ed-all Entire repository (excluding internet-drafts) internet-drafts Internet Drafts ids-text-only Only text files from the Internet Drafts mirror rfcs-pdf-only PDF versions of ASCII RFCs to ensure correct page breaks, etc rsync.ietf.org apparently doesn't help for my request $ rsync rsync.ietf.org:: charter - Repository of WG Charters concluded-wg-ietf-mail-archive - Older list text archives conflict-reviews - Repository of Conflict Review documents everything-ftp - The entire IETF FTP Archive iana - IANA assignments iana-timezone - IANA Time Zone Datatbase (see also http://www.iana.org/time-zones) id-archive - The Internet Draft Archive (both active and expired drafts) iesg-minutes - IESG Minutes internet-drafts - The Internet Draft Repository (currently active drafts) legacy-files - Legacy material supporting long-lived URLs mailman-archive - Repository of Mailing List Text Archives proceedings - Repository of Proceedings rfc - Repository of RFCs slides - Repository of Slide Documents status-changes - Repository of Status Change Documents $ Regards, Benoit --------------000902000909030003000204 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Dear all,

I try to download only the .txt drafts and RFCs.
As mentioned at http://www.rfc-editor.org/rsync-help.html, I'm using:
    rsync -avz --delete ftp.rfc-editor.org::rfcs-text-only my-rfc-mirror

The issue is that the results contain some .txt.p7s, some .xml extension.
What do I do wrong?

rsync ftp.rfc-editor.org::
everything-ftp     Everything FTP
refs               References
rfcs               Contents of in-notes including subdirectories std, bcp, fyi, and ien
rfcs-text-only     Only the text files from the directories in [rfcs]
rfc-ed-all         Entire repository (excluding internet-drafts)
internet-drafts    Internet Drafts
ids-text-only      Only text files from the Internet Drafts mirror
rfcs-pdf-only      PDF versions of ASCII RFCs to ensure correct page breaks, etc

rsync.ietf.org apparently doesn't help for my request

$ rsync  rsync.ietf.org::
charter            - Repository of WG Charters
concluded-wg-ietf-mail-archive    - Older list text archives
conflict-reviews    - Repository of Conflict Review documents
everything-ftp     - The entire IETF FTP Archive
iana               - IANA assignments
iana-timezone      - IANA Time Zone Datatbase (see also http://www.iana.org/time-zones)
id-archive         - The Internet Draft Archive (both active and expired drafts)
iesg-minutes       - IESG Minutes
internet-drafts    - The Internet Draft Repository (currently active drafts)
legacy-files       - Legacy material supporting long-lived URLs
mailman-archive    - Repository of Mailing List Text Archives
proceedings        - Repository of Proceedings
rfc                - Repository of RFCs
slides             - Repository of Slide Documents
status-changes     - Repository of Status Change Documents
$


Regards, Benoit
--------------000902000909030003000204-- From nobody Tue Jun 16 20:11:19 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EFEC1B37A7 for ; Tue, 16 Jun 2015 20:11:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.235 X-Spam-Level: X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=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 3Bc9JDsYZUND for ; Tue, 16 Jun 2015 20:11:16 -0700 (PDT) Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C7C01B37A6 for ; Tue, 16 Jun 2015 20:11:15 -0700 (PDT) Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-04v.sys.comcast.net with comcast id hFB51q0012GyhjZ01FBEC3; Wed, 17 Jun 2015 03:11:14 +0000 Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-09v.sys.comcast.net with comcast id hFBD1q00H1KKtkw01FBESY; Wed, 17 Jun 2015 03:11:14 +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 t5H3BDgJ028596; Tue, 16 Jun 2015 23:11:13 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t5H3BDcD028593; Tue, 16 Jun 2015 23:11: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: Benoit Claise In-Reply-To: <55800C7C.70805@cisco.com> (bclaise@cisco.com) Sender: worley@ariadne.com (Dale R. Worley) Date: Tue, 16 Jun 2015 23:11:12 -0400 Message-ID: <87h9q7qban.fsf@hobgoblin.ariadne.com> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1434510674; bh=I92KaO7kseJdlKJXYbN6cIXeuzfJKLCxognEwKxTz9k=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=E4X9AZ0efPHCmimJKw5bv2M+YSUj0uY5uE8fajfMBuu5SP3UcaKGhBxrLNp/B+F3m O5fD8bqNAggizxG5g1n92bgcKKzywBMNrpJIX4Arr5XpN6qttWv8eTpSZSafDgj5Cq VzGxNiEKyDH+4YcoZy24uFH0EMJYwM8JyTXRyVkkHLdv1hkpIN3ffe+zK/gr5HBR8J uJfz4Nvz+BrP72BqL4zPoczwQ18mUGcveEKsYoLOyVQCRzOzz8lI/5p1NvNPMMEyH/ Y/GJwYTK3l7AGv3Q5nsh9Ac8gdeziWkthgioe7v7cPZIkUDq5gOEcj/LkMGlG1csoE 9yQnHLkWzInZQ== Archived-At: Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] rsync help X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 03:11:17 -0000 Benoit Claise writes: > I try to download only the .txt drafts and RFCs. > As mentioned at http://www.rfc-editor.org/rsync-help.html, I'm using: * > rsync -avz --delete ftp.rfc-editor.org::rfcs-text-only my-rfc-mirror* > > The issue is that the results contain some .txt.p7s, some .xml extension. > What do I do wrong? Just now, I executed that command. None of the files it retrieved had ".txt.p7s" extensions, and only one had an ".xml" extension (rfc-index.xml). Of course, the command retrieves whatever is in the directory "rfcs-text-only". If you want to ensure that you retrieve only files with a certain extension, you'll have to use the --include and --exclude options to rsync. Dale From nobody Tue Jun 16 22:41:49 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 802F41B3C7D for ; Tue, 16 Jun 2015 22:41:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.038 X-Spam-Level: X-Spam-Status: No, score=-1.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 NSrLLfze7Bqd for ; Tue, 16 Jun 2015 22:41:47 -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 32E501B3C7C for ; Tue, 16 Jun 2015 22:41:46 -0700 (PDT) Received: from [172.16.25.102] (69-77-155-155.static.skybest.com [69.77.155.155]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 9F31519A5F; Wed, 17 Jun 2015 01:36:51 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3054\)) From: Tom Pusateri In-Reply-To: <87h9q7qban.fsf@hobgoblin.ariadne.com> Date: Wed, 17 Jun 2015 01:41:44 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <2FE717A9-ED6B-4845-A88C-976F4A8955E8@bangj.com> References: <87h9q7qban.fsf@hobgoblin.ariadne.com> To: "Dale R. Worley" X-Mailer: Apple Mail (2.3054) Archived-At: Cc: Benoit Claise , tools-discuss@ietf.org Subject: Re: [Tools-discuss] rsync help X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 05:41:48 -0000 > On Jun 16, 2015, at 11:11 PM, Dale R. Worley = wrote: >=20 > Benoit Claise writes: >> I try to download only the .txt drafts and RFCs. >> As mentioned at http://www.rfc-editor.org/rsync-help.html, I'm using: = * >> rsync -avz --delete ftp.rfc-editor.org::rfcs-text-only = my-rfc-mirror* >>=20 >> The issue is that the results contain some .txt.p7s, some .xml = extension. >> What do I do wrong? >=20 > Just now, I executed that command. None of the files it retrieved had > ".txt.p7s" extensions, and only one had an ".xml" extension > (rfc-index.xml). >=20 > Of course, the command retrieves whatever is in the directory > "rfcs-text-only". If you want to ensure that you retrieve only files > with a certain extension, you'll have to use the --include and = --exclude > options to rsync. >=20 > Dale Here=E2=80=99s some examples of =E2=80=94-include and =E2=80=94-exclude. = This is what I use for drafts: % rsync -Pavlz --delete --delete-excluded --exclude=3Ddummy.txt = --include=3D"*.txt" --include=3D"*.ps" --include=3D"*.pdf" = --include=3D"*.html" --include=3D"*.xml" --exclude=3D"*" = www1.ietf.org::internet-drafts internet-drafts and for RFCs: % rsync -Pavlz --delete --delete-excluded --exclude=3Ddummy.txt = --include=3D"*.txt" --include=3D"*.ps" --include=3D"*.pdf" = --include=3D"*.html" --include=3D"*.xml" --exclude=3D"*" = ftp.rfc-editor.org::rfcs rfc Tom= From nobody Wed Jun 17 00:39:03 2015 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 049F71A1B8E for ; Wed, 17 Jun 2015 00:39:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham 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 ejCIgtosEhUc for ; Wed, 17 Jun 2015 00:39:00 -0700 (PDT) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B1DE1A1B8A for ; Wed, 17 Jun 2015 00:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1477; q=dns/txt; s=iport; t=1434526740; x=1435736340; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=wq/MEAMT9sbVlSLaekqyqS77YT06N0SkfP3DWjEYh0E=; b=FyIZQwP2M+5Xxbe4UXNc1VEUa6dQPLh/+Kx6QEjbZWxla6W6sAO+XwbV 1WdIbfUMbj1vCK3CM2b71lWewjA9JKTZIRMkQJAEXEHSTN015M9IqLKNr ZZtx2W9iC4HSDwtSQYcavWXpxahqnPAoCqbmlZwggIpCHs0DLIleiuQ+Z Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AyBAB3I4FV/xbLJq1bg2Rfgx66cQmBZ4V4AoIGFAEBAQEBAQGBCoQjAQEEIw8BBUABEAsYAgIFFgsCAgkDAgECAUUGAQwBBQIBAYgrDbZ1lkwBAQEBAQEBAQEBAQEBAQEBAQEBARiBIYojhQYHgmiBQwEEk2iLR4E0hnKMH4NbJoN7PDEBgkcBAQE X-IronPort-AV: E=Sophos;i="5.13,631,1427760000"; d="scan'208";a="548773174" Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 17 Jun 2015 07:38:59 +0000 Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t5H7cw11028778; Wed, 17 Jun 2015 07:38:58 GMT Message-ID: <55812412.6030701@cisco.com> Date: Wed, 17 Jun 2015 09:38:58 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Tom Pusateri , "Dale R. Worley" References: <87h9q7qban.fsf@hobgoblin.ariadne.com> <2FE717A9-ED6B-4845-A88C-976F4A8955E8@bangj.com> In-Reply-To: <2FE717A9-ED6B-4845-A88C-976F4A8955E8@bangj.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] rsync help X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 07:39:02 -0000 Thank you all for your private and public answers. Regards, Benoit >> On Jun 16, 2015, at 11:11 PM, Dale R. Worley wrote: >> >> Benoit Claise writes: >>> I try to download only the .txt drafts and RFCs. >>> As mentioned at http://www.rfc-editor.org/rsync-help.html, I'm using: * >>> rsync -avz --delete ftp.rfc-editor.org::rfcs-text-only my-rfc-mirror* >>> >>> The issue is that the results contain some .txt.p7s, some .xml extension. >>> What do I do wrong? >> Just now, I executed that command. None of the files it retrieved had >> ".txt.p7s" extensions, and only one had an ".xml" extension >> (rfc-index.xml). >> >> Of course, the command retrieves whatever is in the directory >> "rfcs-text-only". If you want to ensure that you retrieve only files >> with a certain extension, you'll have to use the --include and --exclude >> options to rsync. >> >> Dale > Here’s some examples of —-include and —-exclude. This is what I use for drafts: > > % rsync -Pavlz --delete --delete-excluded --exclude=dummy.txt --include="*.txt" --include="*.ps" --include="*.pdf" --include="*.html" --include="*.xml" --exclude="*" www1.ietf.org::internet-drafts internet-drafts > > and for RFCs: > > % rsync -Pavlz --delete --delete-excluded --exclude=dummy.txt --include="*.txt" --include="*.ps" --include="*.pdf" --include="*.html" --include="*.xml" --exclude="*" ftp.rfc-editor.org::rfcs rfc > > Tom. >