
From root@core3.amsl.com  Mon Oct 19 14:45:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: pppext@ietf.org
Delivered-To: pppext@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 278073A691B; Mon, 19 Oct 2009 14:45:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091019214502.278073A691B@core3.amsl.com>
Date: Mon, 19 Oct 2009 14:45:02 -0700 (PDT)
Cc: pppext@ietf.org
Subject: [Pppext] I-D ACTION:draft-ietf-pppext-trill-protocol-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 21:45:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF.

	Title		: PPP TRILL Protocol Control Protocol
	Author(s)	: J. Carlson
	Filename	: draft-ietf-pppext-trill-protocol-00.txt
	Pages		: 6
	Date		: 2009-10-12
	
   The Point-to-Point Protocol (PPP) [1] defines a Link Control Protocol
   (LCP) and a method for negotiating the use of multi-protocol traffic
   over point-to-point links.  This document describes support for
   Transparent Interconnection of Lots of Links (TRILL) Protocol,
   allowing direct communication between Routing Bridges (RBridges) via
   PPP links.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-trill-protocol-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pppext-trill-protocol-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-10-19143414.I-D@ietf.org>


--NextPart--


From carlsonj@workingcode.com  Mon Oct 19 16:31:23 2009
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AEA728C111 for <pppext@core3.amsl.com>; Mon, 19 Oct 2009 16:31:23 -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=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nj71bYMqKWM2 for <pppext@core3.amsl.com>; Mon, 19 Oct 2009 16:31:22 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 4688C28C0E7 for <pppext@ietf.org>; Mon, 19 Oct 2009 16:31:22 -0700 (PDT)
Received: from [192.168.254.190] (dhcp-190 [192.168.254.190]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.3) with ESMTP id n9JNVR7f027925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pppext@ietf.org>; Mon, 19 Oct 2009 19:31:28 -0400 (EDT)
Message-ID: <4ADCF6E8.3020703@workingcode.com>
Date: Mon, 19 Oct 2009 19:31:52 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090818)
MIME-Version: 1.0
To: pppext@ietf.org
References: <20091019214502.278073A691B@core3.amsl.com>
In-Reply-To: <20091019214502.278073A691B@core3.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-dmv.com-Metrics: carlson 1181; Body=1 Fuz1=1 Fuz2=1
Subject: Re: [Pppext] I-D ACTION:draft-ietf-pppext-trill-protocol-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 23:31:23 -0000

> 	Title		: PPP TRILL Protocol Control Protocol
> 	Author(s)	: J. Carlson
> 	Filename	: draft-ietf-pppext-trill-protocol-00.txt
> 	Pages		: 6
> 	Date		: 2009-10-12

A bit backwards, probably, but I'd like to propose this draft to be
adopted as a working group document.  Obviously, if there's a lack of
consensus, I'll rename it appropriately.

The draft was written to flesh out the operation of TRILL on
point-to-point links, since these links lack the addressing information
on which the 'native' packet formats are based.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From web-usrn@ISI.EDU  Thu Oct 22 13:16:57 2009
Return-Path: <web-usrn@ISI.EDU>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA5BF3A6861 for <pppext@core3.amsl.com>; Thu, 22 Oct 2009 13:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.111
X-Spam-Level: 
X-Spam-Status: No, score=-17.111 tagged_above=-999 required=5 tests=[AWL=0.488, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C296b2JhhWst for <pppext@core3.amsl.com>; Thu, 22 Oct 2009 13:16:56 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id D36453A659B for <pppext@ietf.org>; Thu, 22 Oct 2009 13:16:56 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n9MKGKX6012997; Thu, 22 Oct 2009 13:16:21 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n9MKGJmB012996; Thu, 22 Oct 2009 13:16:19 -0700 (PDT)
Date: Thu, 22 Oct 2009 13:16:19 -0700 (PDT)
Message-Id: <200910222016.n9MKGJmB012996@boreas.isi.edu>
To: gwz@acm.org, rdroms@cisco.com, jari.arkko@piuha.net, james.d.carlson@sun.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
Cc: pppext@ietf.org, alexey.melnikov@isode.com, rfc-editor@rfc-editor.org
Subject: [Pppext] [Technical Errata Reported] RFC2759 (1924)
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2009 20:16:57 -0000

The following errata report has been submitted for RFC2759,
"Microsoft PPP CHAP Extensions, Version 2".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=2759&eid=1924

--------------------------------------
Type: Technical
Reported by: Alexey Melnikov <alexey.melnikov@isode.com>

Section: 8.3

Original Text
-------------
   NtPasswordHash(
   IN  0-to-256-unicode-char Password,
   OUT 16-octet              PasswordHash )
   {
      /*
       * Use the MD4 algorithm [5] to irreversibly hash Password
       * into PasswordHash.  Only the password is hashed without
       * including any terminating 0.
       */
   }

Corrected Text
--------------
   NtPasswordHash(
   IN  0-to-256-unicode-char Password,
   OUT 16-octet              PasswordHash )
   {
      /*
       * Use the MD4 algorithm [5] to irreversibly hash Password
       * encoded in UTF-16-LE into PasswordHash.
       * Only the password is hashed without
       * including any terminating 0.
       */
   }

Notes
-----
Section 8.3 is silent on Unicode encoding used for passwords.
Section 9.2 seem to imply that the Unicode encoding used in UTF-16-LE.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC2759 (draft-ietf-pppext-mschap-v2-04)
--------------------------------------
Title               : Microsoft PPP CHAP Extensions, Version 2
Publication Date    : January 2000
Author(s)           : G. Zorn
Category            : INFORMATIONAL
Source              : Point-to-Point Protocol Extensions
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From carlsonj@workingcode.com  Thu Oct 22 13:40:30 2009
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B57E23A6861 for <pppext@core3.amsl.com>; Thu, 22 Oct 2009 13:40:30 -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=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34VKphHlKx3E for <pppext@core3.amsl.com>; Thu, 22 Oct 2009 13:40:29 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 5C7183A659B for <pppext@ietf.org>; Thu, 22 Oct 2009 13:40:29 -0700 (PDT)
Received: from [10.50.24.188] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.3) with ESMTP id n9MKeSSK000225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Oct 2009 16:40:28 -0400 (EDT)
Message-ID: <4AE0C33B.8030905@workingcode.com>
Date: Thu, 22 Oct 2009 16:40:27 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: RFC Errata System <rfc-editor@rfc-editor.org>
References: <200910222016.n9MKGJmB012996@boreas.isi.edu>
In-Reply-To: <200910222016.n9MKGJmB012996@boreas.isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-dmv.com-Metrics: carlson 1181; Body=7 Fuz1=7 Fuz2=7
Cc: pppext@ietf.org, gwz@acm.org, james.d.carlson@sun.com, rdroms@cisco.com, alexey.melnikov@isode.com
Subject: Re: [Pppext] [Technical Errata Reported] RFC2759 (1924)
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2009 20:40:30 -0000

RFC Errata System wrote:
> The following errata report has been submitted for RFC2759,
> "Microsoft PPP CHAP Extensions, Version 2".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2759&eid=1924

Yes, that change is accurate.  The same issue affects the description
for GenerateNTResponse() in 8.1, GenerateAuthenticatorResponse() in 8.7,
NewPasswordEncryptedWithOldNtPasswordHash() in 8.9, and
OldNtPasswordHashEncryptedWithNewNtPasswordHash() in 8.12.  In all cases
where a "0-to-256-unicode-char Password" is used, the algorithm actually
expects 16 bit little-endian Unicode.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
