Re: [Pana] work items

Frank,

You can post it somewhere on the web and send a link on the mailing list.

Alper 

> -----Original Message-----
> From: Frank Xia [mailto:xiayangsong@huawei.com]
> Sent: Monday, February 25, 2008 10:25 PM
> To: Alper Yegin; pana@ietf.org
> Cc: John Kaippallimalil
> Subject: Re: [Pana] work items
> 
> Hi Alper
> 
> We had a draft  called "simplified Protocol for Carrying Authentication
> for Network Access"
> which missed the deadline of the submission.
> IMO, it is a good topic to discuss in the meeting.
> 
> I  wonder if  it is proper to send out through the mailing list.
> 
> The abstract is:
> "   This document describes simplified Protocol for Carrying
>    Authentication for Network Access (sPANA).  Since in the broadband
>    (e.g.  DSL forum, WiMAX forum) architecture, a Network Access Server
>    (NAS) is one IP hop away from the user, it is possible to relax the
>    need in PANA to obtain an IP address prior to authentication.  The
>    PANA client (PaC) could use a unspecified IP address (i.e. 0.0.0.0)
>    for authentication.  This document also defines PANA Attribute-Value
>    Pairs (AVPs) and procedures that allow for a Challenge-Handshake
>    Authentication Protocol(CHAP) exchange to occur in PANA.  PANA CHAP
>    support facilitate smooth migration from Point-to-Point Protocol
>    (PPP) sessions to IP sessions in a DSL Broadband network environment.
>    The sPANA protocol is fully compatible with the basic PANA protocol."
> 
> BR
> Frank
> 
> ----- Original Message -----
> From: "Alper Yegin" <alper.yegin@yegin.org>
> To: <pana@ietf.org>
> Sent: Sunday, February 24, 2008 4:41 PM
> Subject: [Pana] work items
> 
> 
> >
> > One of the things we'd be discussing in the PANA meeting is work scope
> and
> > re-chartering.
> >
> > Now that we delivered the base specification to the RFC editor, we are
> > advised by the ADs to revise the charter. Also, we have several work
> items
> > on our plate and we need to go back and see where each one is standing
> and
> > discuss what to do with them.
> >
> > We are going to have a discussion on that in Philadelphia and seek WG's
> > input. Please be prepared.
> >
> > These are the current WG documents (except for the ones in RFC editor's
> > queue):
> >
> > Active:
> > http://tools.ietf.org/html/draft-ietf-pana-preauth-02
> > http://tools.ietf.org/html/draft-ietf-pana-statemachine-06
> >
> > IESG Processing:
> > http://tools.ietf.org/html/draft-ietf-pana-ipsec-07
> >
> > Expired:
> > http://tools.ietf.org/html/draft-ieft-pana-aaa-interworking-00
> > http://tools.ietf.org/html/draft-ietf-pana-cxtp-01
> > http://tools.ietf.org/html/draft-ietf-pana-mobopts-01
> >
> > The following two are expired, but in fact they should not even show up
> in
> > WG list as we had decided to kill them:
> > http://tools.ietf.org/html/draft-ietf-pana-snmp-06
> > http://tools.ietf.org/html/draft-ietf-pana-usage-scenarios-06
> >
> >
> > For each of these documents, we need to discuss the current status and
> > future plan. Also, if there are new documents to be considered as a WG
> item,
> > that should also be brought up.
> >
> > Early feedback on the mailing list is welcome.
> >
> > - Chairs
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > http://www.ietf.org/mailman/listinfo/pana
> >

_______________________________________________
Pana mailing list
Pana@ietf.org
http://www.ietf.org/mailman/listinfo/pana