From nobody Wed Jan 4 17:27:01 2017 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 E6CC11294C8 for ; Wed, 4 Jan 2017 17:26:59 -0800 (PST) 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 r5BBQPC_Vuw6 for ; Wed, 4 Jan 2017 17:26:58 -0800 (PST) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 B722E1294C2 for ; Wed, 4 Jan 2017 17:26:58 -0800 (PST) Received: by mail-yw0-x232.google.com with SMTP id t125so330157305ywc.1 for ; Wed, 04 Jan 2017 17:26:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=9c4Qayh11dYjCY1ZUEBOITidGd5tTKIxI5UarIAoiSM=; b=tXiD1RFWVctDntN64b4qtfSeEeyLcGcHc8NEgotd5Ermp7jtiJ3h4jWwjHGCzI59nS 665bt/Ggt6zkdFnM6mJ+PbR7HhV6DaUCQObkk1kxJ76tGSDSINcl5eMX0chj+RTrgpMm hTeJ7uLokpVjKfEDorYSabaiPxgBDPvL2IdGMxAlcXmktPQWF9wxk0YDf97nocSgEIft Q9eTuBdT5Az9WOpaT+qDrKEU/b53h1E/8MtVss7S+nGpoWSmfScANtS2fWcG1Dx83Zix qhHZWY6CT2cFL+UtvktTmLGGDwkg2FyXCQ7zFKIbzAV3vv8/SwR7yThA2oDZONHd9jXm JfAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9c4Qayh11dYjCY1ZUEBOITidGd5tTKIxI5UarIAoiSM=; b=P7i65phXIU8iQ0qdM7/U8d/Ra+ylFk+HPsu6GXZJ+QqlzEdnNsNmrh6Kn6OFnblpjk 3SxxaDDUBetVuYeYnDTqc+o5LjaXlSJqd2qTZjdM8p3bcpulyOTXajCv4v/s39OCzhCC iJFj05X4UKPQeXl+azNLXcTb5OIin/igR2ZbNQqlXbI3rMZrMoPdRMzUv0g91y218O4b ExWZwv+ivAvexssDoQijBgkXvAxkqRZKGTAasGyk+kJuvGVUFV2OZ9cnQ57IG73EuibC xLxKd+Q54g/9VlAJMfNy8zdr5i4RvqoH3GgRd9inT0nkaDvcPj8omWyxU2yxJjqmWMMv 95Lg== X-Gm-Message-State: AIkVDXLjfiV7PFJcjD++U104dk93aJDzysl0ePlAlr5v5L4YNF3RsQqoBoBfirI9AS7ih1ZbCG57oyjpXNr+bg== X-Received: by 10.13.231.194 with SMTP id q185mr64048702ywe.141.1483579617891; Wed, 04 Jan 2017 17:26:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.177.65 with HTTP; Wed, 4 Jan 2017 17:26:57 -0800 (PST) From: Alia Atlas Date: Wed, 4 Jan 2017 20:26:57 -0500 Message-ID: To: tools-discuss@ietf.org Content-Type: multipart/alternative; boundary=94eb2c07cbda1edac105454ecccd Archived-At: Subject: [Tools-discuss] easy way to restrict access to a wiki page? 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, 05 Jan 2017 01:27:00 -0000 --94eb2c07cbda1edac105454ecccd Content-Type: text/plain; charset=UTF-8 Hi, What is the an easy way to restrict read access to a wiki page? In this case, I'm looking for something for just Routing ADs.... Thanks, Alia --94eb2c07cbda1edac105454ecccd Content-Type: text/html; charset=UTF-8
Hi,

What is the an easy way to restrict read access to a wiki page?
In this case, I'm looking for something for just Routing ADs....

Thanks,
Alia

--94eb2c07cbda1edac105454ecccd-- From mackyle@gmail.com Wed Jan 4 21:20:32 2017 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 EE87E129A96 for ; Wed, 4 Jan 2017 21:20:32 -0800 (PST) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 PUi8bQEnjCzt for ; Wed, 4 Jan 2017 21:20:31 -0800 (PST) Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::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 6FCD9129A8D for ; Wed, 4 Jan 2017 21:20:31 -0800 (PST) Received: by mail-pg0-x22f.google.com with SMTP id i5so170966210pgh.2 for ; Wed, 04 Jan 2017 21:20:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:from:to:content-transfer-encoding:subject:mime-version :date; bh=wXxy4g8qGqYBPScroTEphrBvFlzcf5/r6l5oZ0MCkPs=; b=FCsyAzZND3LPJbV3zkSqQndnjPggqAaTMYIGu5rx4D2m7yPKKs2Bni7AJ3pYjRh6js z2xluwV79KUK8Qim0yKBQA7KACUrWCzlweKv8QF1AiCSM0WpU383x4JzM7LmIqr4o2Vy aksNqCtwQOFFksKoZ6DRMr9k84F+JdCZyXQvuyb3rkVdJFMyAge3m2o4lrxx7SaiVaRd stp5+6+mw+5cTfSSLqN66KlRhdGPdQUVsC3ntoVuT/AP9lDM6Q9ANFbt3UHExtztO5/K p1PnlKg87pqtkmA5VL4iSjiwoUI+pPTXiCU5XNnUIwVAu+gdty/0yB0oaaiBv9SwG6Dq dzmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:from:to:content-transfer-encoding :subject:mime-version:date; bh=wXxy4g8qGqYBPScroTEphrBvFlzcf5/r6l5oZ0MCkPs=; b=gdA8BhS6XFED9+7ZNkKTcPGziLgs6V22SIEK2FzS5o5BKm/020LAH3IKIOWwlAqCGH A6asPU4QI2LimE/vBXEMvvEaGWAKXKtXJogbqjQxG3h8bcw9Bm75VuM2HtrYpjI24NWS 7ShkQDDxEfiZiFmUx9wiDrIWxxHaXzd4Zswrc0hA1HQwh4Z/O4wY6JnSQ+iSWRaAH1ay 5bh2im1VPktlRSYZ9DuWnhX2AwHJdPFC7ZCnPqdIAW25bE3ouKeNZ/rkk9+DB0FnUHzC Y4Sk0o+/67sWjD3vl2v8soNDnsNQZ0mlqNgoDHk2ApD0nkIlUgVomLDRJnPlDN3ZhKgN 0uUw== X-Gm-Message-State: AIkVDXKYxrlOYHKOaYEtiXZcAnkLopJ0vROQf6RpVATGA1gK4QpKmNZPxhpgG3xcnefNsQ== X-Received: by 10.84.217.5 with SMTP id o5mr152048185pli.85.1483593631018; Wed, 04 Jan 2017 21:20:31 -0800 (PST) Received: from ?IPv6:2002:46b5:ad14::223:12ff:fe05:eebd? ([2002:46b5:ad14:0:223:12ff:fe05:eebd]) by smtp.gmail.com with ESMTPSA id e6sm132696597pgf.4.2017.01.04.21.20.29 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 04 Jan 2017 21:20:30 -0800 (PST) Message-Id: From: "Kyle J. McKay" To: tools-discuss@ietf.org, Henrik Levkowetz Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Wed, 4 Jan 2017 21:20:28 -0800 X-Mauler: Craptastic (2.936) Archived-At: Subject: [Tools-discuss] rfcmarkup source code? 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, 05 Jan 2017 05:23:07 -0000 Is the current rfcmarkup source code available somewhere? Going to a page such as the one for RFC 1123: https://tools.ietf.org/html/rfc1123 Shows this info at the bottom (in very small letters): > Html markup produced by rfcmarkup 1.120, available from > https://tools.ietf.org/tools/rfcmarkup/ But when I visit that tools link the only option I can find is the "Code" link and it brings up a colorized page of outdated version 1.96 that shows a GPL license yet the "Copyright" link shows a different license. It's not a very helpful link as you have to copy and paste what it shows from the browser page to get anything useful (or use something like lynx -dump on the URL) and then all you end up with is a version that's 5 1/2 years out of date. The Changelog link () shows revision numbers that suggest the source is stored in CVS. Is anonymous read-only access available to that repository somewhere? Or better yet is there a Git clone of it somewhere? Thanks for the help, Kyle From nobody Tue Jan 31 09:10:04 2017 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 42E3C129FD5 for ; Tue, 31 Jan 2017 09:10:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.1 X-Spam-Level: X-Spam-Status: No, score=-5.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, 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 XGm6H0ZJez2u for ; Tue, 31 Jan 2017 09:10:01 -0800 (PST) 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 6CE6B1299BC for ; Tue, 31 Jan 2017 09:10:01 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 70DA82009E for ; Tue, 31 Jan 2017 12:30:38 -0500 (EST) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7C5F96381A for ; Tue, 31 Jan 2017 12:10:00 -0500 (EST) From: Michael Richardson To: tools-discuss X-Attribution: mcr 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: Subject: [Tools-discuss] emailing authors of RFC 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, 31 Jan 2017 17:10:03 -0000 --=-=-= Content-Type: text/plain looking at: https://datatracker.ietf.org/doc/rfc8032/ I see that the email author links goes to: mailto:draft-irtf-cfrg-eddsa@ietf.org?subject=Mail... rather than to either 1) cfrg WG, or 2) some rfc8032-authors@ietf.org address. I don't know if that's an ommission or commission. Also, will the RFC-editor pages eventually link back to the datatracker page for a document that has one? I wouldn't mind of the document itself had that link too. If only to push the SEO of the datatracker. Also, could: IESG IESG state RFC 8032 (Informational) link to the rfc-editor page for 8032? -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAliQxOcACgkQgItw+93Q 3WWEnAgAmzkvKv/VNIoU/dJAAMG/h0FtFpfACaKc1GVs/niv44NRWvaYA2mi2ylm jQ3+pGGQsPZ2e8q1bcdYX3WVf5cDJln7szh4cLo8un04Prl/boEEKLZWedvc3RTT PPGOi+2zsT5DTxWAIKLP3kWXkwZnfzuswDW63iZrtqHk4H9z5Ectkjv1l9jiE2cf yiMyJjjzwLzGJy9RLOguw2DoG8j8fq5zqnmqyBH8/+ogjAJaY+57Hg9z7Zklk7Da BrAo2t+x/lXJm+DXlqBNYuzUtbinSITQr3mzL55xXXwCt21p9vJvhrVwXJqR6KZl MfPQl7YtbNlYLb8IWmHKehgoG5fQqw== =lejB -----END PGP SIGNATURE----- --=-=-=--