
From alper.yegin@yegin.org  Wed Jun  1 01:33:09 2011
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3692AE06AC for <pana@ietfa.amsl.com>; Wed,  1 Jun 2011 01:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xR-e5LG0hUl9 for <pana@ietfa.amsl.com>; Wed,  1 Jun 2011 01:33:07 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEC0E07B2 for <pana@ietf.org>; Wed,  1 Jun 2011 01:33:06 -0700 (PDT)
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MStm1-1PzojL12l3-00S9r0; Wed, 01 Jun 2011 04:32:52 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yoshihiro.ohba@toshiba.co.jp>
References: <4D5AA4A7.3050104@toshiba.co.jp> <4DDCE436.2010507@piuha.net> <4DDDA869.204@toshiba.co.jp> <4DDDDE0B.4070601@piuha.net> <4DE31809.1040100@toshiba.co.jp> <4DE33DAA.9060307@piuha.net> <00a001cc1ea6$e40b4510$ac21cf30$%yegin@yegin.org> <4DE4F97A.1040406@toshiba.co.jp>
In-Reply-To: <4DE4F97A.1040406@toshiba.co.jp>
Date: Wed, 1 Jun 2011 11:32:44 +0300
Message-ID: <003f01cc2036$7fb5b780$7f212680$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwfniE/v/PyyzHqT/iF+suHrSXa9gAlEhDQ
Content-Language: en-us
X-Provags-ID: V02:K0:YIVIj0xelH4/rKnk1aD80jmZJ8xBTsIKkawOiNrYkBS 5nHKbYhpqUw+nrBxuIzrt0DtgNruXR9yREV8zZWZjH9h6qRD48 HCUFmI0kuSs8VRwHB6TbSKOW5rxAr6x5L77ll6HRDm6AkZZdT4 4PhhPiw1go68lbjokX3tipHCxH3ZhsizCofoItmIuILulUCqJz Vj4OpoGTPXZeBL3rXKg2tGBzTSigF0ODvvHwzhX3WY=
Cc: pana@ietf.org, 'Ralph Droms' <rdroms@cisco.com>
Subject: Re: [Pana] Explicit error indication
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 08:33:09 -0000

Yoshi,

I'm afraid my worries are coming true. I was worried that this would grow on
us. Now we are talking about supporting different classes of error cases.
Most probably we'd have to define bunch of error types. We'll try to be
complete there. And then there are also case handling (e.g., whether session
id is available, etc.). On top of that, defining general error messaging in
this "extension" draft is not the right thing. That better have a separate
base, if we decide to do such a work. One more thing: this impacts the PaC.
Relaying did not have any impact on the PaC until that.

On top of that, defining such error signaling is something we had debated
long time in the base spec development and had agreed to remove. And again
we had the same discussion in the context of PANA-relay, and then again
decided to remove. Both after long debates and coming to conscious
decisions. Such error messages are not useful for protocol operation, it is
only good for debugging. As far as I know, we don't do these kind of error
signaling in our IETF protocols. Silent discarding and optionally logging an
error is what we do.

I'm recapping Jari's email below. I'd like to go with his "I don't mind that
we skip specifying this functionality now.", and take care of his "At the
very least, we should
specify what happens if you end up receiving an already relayed message." as
follows:


	If the PRE is not configured with any PAA information, it SHALL
silently discard the 
	incoming PANA messages and it MAY log an error.

	If the PRE receives an PRY message from another PRE, then it SHOULD
silently discard 
	that message and it MAY log an error. Future extensions may define a
multi-hop relay 
	procedure which can change the PRE behavior in this respect.


What do you think?

Alper


------- Jari's email ----------------

> This specification assumes there is at most one PRE between the PaC
> and the PAA.  Performing relay operation on a PANA message that is
> already relayed (i.e., carried inside a PRY message) is out-of scope
> of this specification.
>   

This is problematic, as it may occur. At the very least, we should
specify what happens if you end up receiving an already relayed message.
Loops may also occur.

I don't mind that we skip specifying this functionality now. What I'm
worried about is the upgrade to doing something better in the future. If
we don't do something now, how do we know tomorrow that our messages are
being correctly relayed?

I would recommend the following behaviour, actually. If the relay
detects an already existing relay attributes or has no configuration to
actually be able to send something to a PAA, it would reply with the
relevant PANA message and set Result-Code to <TBD = Relay cannot route
message>. This would allow the client to at least know something is
wrong. This would also allow the relay to signal other erroneous
conditions to the client.

-----------------------------






> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp]
> Sent: Tuesday, May 31, 2011 5:22 PM
> To: Alper Yegin
> Cc: 'Jari Arkko'; 'Ralph Droms'; pana@ietf.org
> Subject: Re: [Pana] Explicit error indication
> 
> Hi Alper,
> 
> In the first part of your email, PRE-to-PRE error indication is
> mentioned.  I only considered PRE-to-PaC error indication in my
> previous email, but I think we can support PRE-to-PRE error indication
> as well.  I think both PRY with an error indication AVP and a new
> error indication message can be workable here, but
> a Result-Code AVP may not be appropriate for temporal errors (see
> below) because the use of a Result-Code AVP is to indicate whether EAP
> authentication was completed successfully.
> 
> For PRE-to-PaC error indication, I thought that using a
> Result-Code for that purpose has an impact on existing RFC 5191
> implementations that do not expect to receive a Result-Code in the
> first PAR with the 'S' bit set, because in the current use of a
> Result-Code is for the last PAR message with the 'C' bit set, but RFC
> 5191 explicitly prohibits to set both the 'S' bit and 'C' bit at the
> same time.  So I thought defining a new message (just as we define
> PRY) has less impact on RFC 5191 as an implementation that does not
> support the new message will simply discard the message and the
> initial PAR-PAN exchange part is kept intact.  Maybe I am missing
> something.  If a Result-Code in the initial PAR works without
> impacting on RFC 5191, then I am also ok with it.
> 
> Regarding types of error, some error can be temporary.  For example,
> temporal buffer shortage or temporal routing fluctuations (e.g., even
> if the PRE has the  PAA information there may be no next hop towards
> the PAA), both can be recoverable (so a PaC may retry PANA
> authentication later on).  I think it would be good we can
> support both non-temporal and temporal errors as long as the impact on
> RFC 5191 is low.
> 
> Regarding which session identifier should be used for a new message
> for error indication, I think the session id contained in the message
> that caused the error should be used.  When the error indication
> message is sent in response to PCI or PRY, then session id is zero,
> otherwise non-zero.
> 
> Regards,
> Yoshihiro Ohba
> 
> 
> 
> (2011/05/30 17:52), Alper Yegin wrote:
> >
> >
> > For relaying already relayed messages... The Result-Code AVP
> (something like
> > MULTIPLE-RELAYING-DISALLOWED) would be included in the PRY message
> sent from
> > one PRE to the other.
> > In response to a PRY that was received from the latter one.
> >
> > How seq no and PANA SA are used for PRY is already defined. There'd
> not be
> > any special considerations here.
> >
> > Right?
> >
> >
> > The other Result-Code would be something like RELAY-REJECTED-NO-PAA-
> INFO.
> > This can be carried in a PAR in response to the PCI received from the
> PaC.
> > (Defining it in response to any other message is less justified [why
> would
> > PER lose the PAA info in the middle of a session relaying?], and also
> less
> > trivial [what would the session id be set to??]
> >
> > I'm trying to see if we can achieve this with the minimum impact.
> >
> > I don't think we need a new message. We just need new Result-Codes.
> >
> >
> > We shouldn't have to touch RFC 5191.
> >
> > Alper
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
> Of
> >> Jari Arkko
> >> Sent: Monday, May 30, 2011 9:48 AM
> >> To: Yoshihiro Ohba
> >> Cc: Ralph Droms; pana@ietf.org
> >> Subject: Re: [Pana] Explicit error indication
> >>
> >> That would work for me.
> >>
> >> Jari
> >>
> >> Yoshihiro Ohba kirjoitti:
> >>> Let me start a new thread on this subject.
> >>>
> >>> I remember a ZigBee member asked if explicit error indication can
> be
> >>> sent by a PRE when a PANA message cannot be relayed for some
> reasons
> >>> (buffer shortage, no route to PAA, etc.).  I think it would be
> useful
> >>> to add such a feature if there is little impact to RFC 5191 to
> >> support
> >>> the feature, as it could reduce unnecessarily retransmissions of
> PCIs
> >>> from PaCs.  Reduce unnecessarily retransmissions may be good for
> >>> resource constrained networks such as ZigBee.
> >>>
> >>> Explicit error indication can be by means of a new PANA message or
> a
> >>> new Result-Code.
> >>>
> >>> Processing explicit error indication is like handling
> >>> exceptions/interruptions.  So considerations would be necessarily
> >>> not to interfere with the PANA sequence number processing rule.
> >>> Especially this would be the case where an error indication is
> >>> protected by a PANA SA.  I would expect that we don't need to
> support
> >>> protected error indication as it would require a complex sequence
> >>> number processing rule such as a separate sequence number space
> >>> dedicated to error indications.
> >>>
> >>> IMHO, a new PANA message (e.g., PANA-Error-Indication)
> >>> carrying sequence number of zero (0) may be simple, something like
> >> this:
> >>>
> >>> PaC     PRE
> >>>      --->      PCI
> >>>      <---     PEI[Error-Code="Relay-failed"] // seqno=0
> >>>
> >>> PEI message is unprotected and it can be used only as a hint.
> >>>
> >>> Regards,
> >>> Yoshihiro Ohba
> >>>
> >>> (2011/05/26 13:58), Jari Arkko wrote:
> >>>
> >>>> Yoshihiro,
> >>>>
> >>>>
> >>>>> Let me give some time to analyze the impact of this
> recommendation.
> >>>>>
> >>>>>
> >>>> Ok. I' not claiming that my solution is necessarily the way
> forward,
> >> but
> >>>> I am worried about the issue.
> >>>>
> >>>> Jari
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Pana mailing list
> >> Pana@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pana
> >
> >


From yoshihiro.ohba@toshiba.co.jp  Wed Jun  1 03:11:08 2011
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 133CFE0780 for <pana@ietfa.amsl.com>; Wed,  1 Jun 2011 03:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level: 
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[AWL=0.815,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jb+OY2-nvI6M for <pana@ietfa.amsl.com>; Wed,  1 Jun 2011 03:11:07 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id CD758E0764 for <pana@ietf.org>; Wed,  1 Jun 2011 03:11:06 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id p51AB3Ed012946; Wed, 1 Jun 2011 19:11:03 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id p51AB3M2007173; Wed, 1 Jun 2011 19:11:03 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id VAA07172; Wed, 1 Jun 2011 19:11:03 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id p51AB2sA020319; Wed, 1 Jun 2011 19:11:02 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p51AB2aG019681; Wed, 1 Jun 2011 19:11:02 +0900 (JST)
Received: from [133.196.17.34] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LM300K09WAEXDD0@mail.po.toshiba.co.jp>; Wed, 01 Jun 2011 19:11:02 +0900 (JST)
Date: Wed, 01 Jun 2011 19:10:54 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <003f01cc2036$7fb5b780$7f212680$%yegin@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <4DE6102E.7040703@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <4D5AA4A7.3050104@toshiba.co.jp> <4DDCE436.2010507@piuha.net> <4DDDA869.204@toshiba.co.jp> <4DDDDE0B.4070601@piuha.net> <4DE31809.1040100@toshiba.co.jp> <4DE33DAA.9060307@piuha.net> <00a001cc1ea6$e40b4510$ac21cf30$%yegin@yegin.org> <4DE4F97A.1040406@toshiba.co.jp> <003f01cc2036$7fb5b780$7f212680$%yegin@yegin.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
Cc: pana@ietf.org, 'Ralph Droms' <rdroms@cisco.com>
Subject: Re: [Pana] Explicit error indication
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 10:11:08 -0000

Alper,

If Jari is ok with your suggested text, there is no reason for me to
object it.

Regards,
Yoshihiro Ohba


(2011/06/01 17:32), Alper Yegin wrote:
> Yoshi,
> 
> I'm afraid my worries are coming true. I was worried that this would grow on
> us. Now we are talking about supporting different classes of error cases.
> Most probably we'd have to define bunch of error types. We'll try to be
> complete there. And then there are also case handling (e.g., whether session
> id is available, etc.). On top of that, defining general error messaging in
> this "extension" draft is not the right thing. That better have a separate
> base, if we decide to do such a work. One more thing: this impacts the PaC.
> Relaying did not have any impact on the PaC until that.
> 
> On top of that, defining such error signaling is something we had debated
> long time in the base spec development and had agreed to remove. And again
> we had the same discussion in the context of PANA-relay, and then again
> decided to remove. Both after long debates and coming to conscious
> decisions. Such error messages are not useful for protocol operation, it is
> only good for debugging. As far as I know, we don't do these kind of error
> signaling in our IETF protocols. Silent discarding and optionally logging an
> error is what we do.
> 
> I'm recapping Jari's email below. I'd like to go with his "I don't mind that
> we skip specifying this functionality now.", and take care of his "At the
> very least, we should
> specify what happens if you end up receiving an already relayed message." as
> follows:
> 
> 
> 	If the PRE is not configured with any PAA information, it SHALL
> silently discard the
> 	incoming PANA messages and it MAY log an error.
> 
> 	If the PRE receives an PRY message from another PRE, then it SHOULD
> silently discard
> 	that message and it MAY log an error. Future extensions may define a
> multi-hop relay
> 	procedure which can change the PRE behavior in this respect.
> 
> 
> What do you think?
> 
> Alper
> 
> 
> ------- Jari's email ----------------
> 
>> This specification assumes there is at most one PRE between the PaC
>> and the PAA.  Performing relay operation on a PANA message that is
>> already relayed (i.e., carried inside a PRY message) is out-of scope
>> of this specification.
>>
> 
> This is problematic, as it may occur. At the very least, we should
> specify what happens if you end up receiving an already relayed message.
> Loops may also occur.
> 
> I don't mind that we skip specifying this functionality now. What I'm
> worried about is the upgrade to doing something better in the future. If
> we don't do something now, how do we know tomorrow that our messages are
> being correctly relayed?
> 
> I would recommend the following behaviour, actually. If the relay
> detects an already existing relay attributes or has no configuration to
> actually be able to send something to a PAA, it would reply with the
> relevant PANA message and set Result-Code to<TBD = Relay cannot route
> message>. This would allow the client to at least know something is
> wrong. This would also allow the relay to signal other erroneous
> conditions to the client.
> 
> -----------------------------
> 
> 
> 
> 
> 
> 
>> -----Original Message-----
>> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp]
>> Sent: Tuesday, May 31, 2011 5:22 PM
>> To: Alper Yegin
>> Cc: 'Jari Arkko'; 'Ralph Droms'; pana@ietf.org
>> Subject: Re: [Pana] Explicit error indication
>>
>> Hi Alper,
>>
>> In the first part of your email, PRE-to-PRE error indication is
>> mentioned.  I only considered PRE-to-PaC error indication in my
>> previous email, but I think we can support PRE-to-PRE error indication
>> as well.  I think both PRY with an error indication AVP and a new
>> error indication message can be workable here, but
>> a Result-Code AVP may not be appropriate for temporal errors (see
>> below) because the use of a Result-Code AVP is to indicate whether EAP
>> authentication was completed successfully.
>>
>> For PRE-to-PaC error indication, I thought that using a
>> Result-Code for that purpose has an impact on existing RFC 5191
>> implementations that do not expect to receive a Result-Code in the
>> first PAR with the 'S' bit set, because in the current use of a
>> Result-Code is for the last PAR message with the 'C' bit set, but RFC
>> 5191 explicitly prohibits to set both the 'S' bit and 'C' bit at the
>> same time.  So I thought defining a new message (just as we define
>> PRY) has less impact on RFC 5191 as an implementation that does not
>> support the new message will simply discard the message and the
>> initial PAR-PAN exchange part is kept intact.  Maybe I am missing
>> something.  If a Result-Code in the initial PAR works without
>> impacting on RFC 5191, then I am also ok with it.
>>
>> Regarding types of error, some error can be temporary.  For example,
>> temporal buffer shortage or temporal routing fluctuations (e.g., even
>> if the PRE has the  PAA information there may be no next hop towards
>> the PAA), both can be recoverable (so a PaC may retry PANA
>> authentication later on).  I think it would be good we can
>> support both non-temporal and temporal errors as long as the impact on
>> RFC 5191 is low.
>>
>> Regarding which session identifier should be used for a new message
>> for error indication, I think the session id contained in the message
>> that caused the error should be used.  When the error indication
>> message is sent in response to PCI or PRY, then session id is zero,
>> otherwise non-zero.
>>
>> Regards,
>> Yoshihiro Ohba
>>
>>
>>
>> (2011/05/30 17:52), Alper Yegin wrote:
>>>
>>>
>>> For relaying already relayed messages... The Result-Code AVP
>> (something like
>>> MULTIPLE-RELAYING-DISALLOWED) would be included in the PRY message
>> sent from
>>> one PRE to the other.
>>> In response to a PRY that was received from the latter one.
>>>
>>> How seq no and PANA SA are used for PRY is already defined. There'd
>> not be
>>> any special considerations here.
>>>
>>> Right?
>>>
>>>
>>> The other Result-Code would be something like RELAY-REJECTED-NO-PAA-
>> INFO.
>>> This can be carried in a PAR in response to the PCI received from the
>> PaC.
>>> (Defining it in response to any other message is less justified [why
>> would
>>> PER lose the PAA info in the middle of a session relaying?], and also
>> less
>>> trivial [what would the session id be set to??]
>>>
>>> I'm trying to see if we can achieve this with the minimum impact.
>>>
>>> I don't think we need a new message. We just need new Result-Codes.
>>>
>>>
>>> We shouldn't have to touch RFC 5191.
>>>
>>> Alper
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
>> Of
>>>> Jari Arkko
>>>> Sent: Monday, May 30, 2011 9:48 AM
>>>> To: Yoshihiro Ohba
>>>> Cc: Ralph Droms; pana@ietf.org
>>>> Subject: Re: [Pana] Explicit error indication
>>>>
>>>> That would work for me.
>>>>
>>>> Jari
>>>>
>>>> Yoshihiro Ohba kirjoitti:
>>>>> Let me start a new thread on this subject.
>>>>>
>>>>> I remember a ZigBee member asked if explicit error indication can
>> be
>>>>> sent by a PRE when a PANA message cannot be relayed for some
>> reasons
>>>>> (buffer shortage, no route to PAA, etc.).  I think it would be
>> useful
>>>>> to add such a feature if there is little impact to RFC 5191 to
>>>> support
>>>>> the feature, as it could reduce unnecessarily retransmissions of
>> PCIs
>>>>> from PaCs.  Reduce unnecessarily retransmissions may be good for
>>>>> resource constrained networks such as ZigBee.
>>>>>
>>>>> Explicit error indication can be by means of a new PANA message or
>> a
>>>>> new Result-Code.
>>>>>
>>>>> Processing explicit error indication is like handling
>>>>> exceptions/interruptions.  So considerations would be necessarily
>>>>> not to interfere with the PANA sequence number processing rule.
>>>>> Especially this would be the case where an error indication is
>>>>> protected by a PANA SA.  I would expect that we don't need to
>> support
>>>>> protected error indication as it would require a complex sequence
>>>>> number processing rule such as a separate sequence number space
>>>>> dedicated to error indications.
>>>>>
>>>>> IMHO, a new PANA message (e.g., PANA-Error-Indication)
>>>>> carrying sequence number of zero (0) may be simple, something like
>>>> this:
>>>>>
>>>>> PaC     PRE
>>>>>       --->       PCI
>>>>>       <---     PEI[Error-Code="Relay-failed"] // seqno=0
>>>>>
>>>>> PEI message is unprotected and it can be used only as a hint.
>>>>>
>>>>> Regards,
>>>>> Yoshihiro Ohba
>>>>>
>>>>> (2011/05/26 13:58), Jari Arkko wrote:
>>>>>
>>>>>> Yoshihiro,
>>>>>>
>>>>>>
>>>>>>> Let me give some time to analyze the impact of this
>> recommendation.
>>>>>>>
>>>>>>>
>>>>>> Ok. I' not claiming that my solution is necessarily the way
>> forward,
>>>> but
>>>>>> I am worried about the issue.
>>>>>>
>>>>>> Jari
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Pana mailing list
>>>> Pana@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pana
>>>
>>>
> 
> 


From yoshihiro.ohba@toshiba.co.jp  Wed Jun  8 20:46:47 2011
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2CC21F8544 for <pana@ietfa.amsl.com>; Wed,  8 Jun 2011 20:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.889
X-Spam-Level: 
X-Spam-Status: No, score=-3.889 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tsOv+xxXdG1T for <pana@ietfa.amsl.com>; Wed,  8 Jun 2011 20:46:42 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 2818E21F853B for <pana@ietf.org>; Wed,  8 Jun 2011 20:46:42 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id p593kdY5026830 for <pana@ietf.org>; Thu, 9 Jun 2011 12:46:39 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id p593kdBf003749 for pana@ietf.org; Thu, 9 Jun 2011 12:46:39 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id NAA03746; Thu, 9 Jun 2011 12:46:39 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id p593kdoE029767 for <pana@ietf.org>; Thu, 9 Jun 2011 12:46:39 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p593kccO013413; Thu, 9 Jun 2011 12:46:38 +0900 (JST)
Received: from [133.199.18.125] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LMI0001Z7TQOKK0@mail.po.toshiba.co.jp> for pana@ietf.org; Thu, 09 Jun 2011 12:46:38 +0900 (JST)
Date: Thu, 09 Jun 2011 12:46:31 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
To: pana@ietf.org
Message-id: <4DF04217.3080304@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
Subject: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt> (Protocol for Carrying Authentication for Network Access (PANA) Relay Element) to Proposed Standard
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 03:46:47 -0000

We have received the following question from IANA.

Since the 'R' (Request) bit is not set for PANA-Relay, I think it
should be filled with "Ans" (not "Req").

BTW, I've found that PCI, for which the 'R' (Request) bit is not set,
is filled with "Req" in the IANA registry.  I think this should have
been filled with "Ans" as well.

Any opinions?

Yoshihiro Ohba

-------- Original Message --------
Subject: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt>
(Protocol for Carrying Authentication for Network Access (PANA) Relay
Element) to Proposed Standard
Date: Wed, 08 Jun 2011 20:37:04 +0000
From: Amanda Baber via RT <drafts-lastcall@iana.org>
Reply-To: drafts-lastcall@iana.org
CC: paduffy@cisco.com, samitac2@gmail.com,
robert.cragie@gridmerge.com, yoshihiro.ohba@toshiba.co.jp,
alper.yegin@yegin.org, iesg@ietf.org

IESG:

IANA has reviewed draft-ohba-pana-relay-03.txt and has the following
comments:

IANA has questions about the IANA Actions in this document.

IANA understands that, upon approval of this document, there are two
IANA Actions that must be completed.

First, in the Message Types registry in the Protocol for Carrying
Authentication for Network Access (PANA) Parameters registry located at:

http://www.iana.org/assignments/pana-parameters/pana-parameters.xml

a single, new message type will be added as follows:

Value [ TBD ]
Name: PANA-Relay

IANA QUESTION --> How should the following field in the registry be
filled in?
Req/Ans: [ ??? ]

Abbrev: PRY
Reference: [ RFC-to-be ]

IANA notes that the authors request the value "5" for the Value of this
Message Type.

Second, in the AVP Codes registry in the the Protocol for Carrying
Authentication for Network Access (PANA) Parameters registry located at:

http://www.iana.org/assignments/pana-parameters/pana-parameters.xml

two new AVP Codes will be added as follows:

Code: [tbd2]
Attribute name: PaC-Information AVP
Reference: [ RFC-to-be ]

Code: [tbd3]
Attribute name: Relayed-Message AVP
Reference: [ RFC-to-be ]

IANA notes that the authors have requested codes "10" and "11" for
[tbd2] and [tbd3] respectively.

IANA understands that these two actions are the only ones required upon
approval of this document.

Note:  The actions requested in this document will not be completed
until the document has been approved for publication as an RFC. This
message is only to confirm what actions will be performed.

Thanks,

Amanda Baber
IANA

On Wed May 25 13:37:06 2011, noreply@ietf.org wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Protocol for Carrying Authentication for Network Access (PANA) Relay
>    Element'
>   <draft-ohba-pana-relay-03.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-06-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
> This document specifies Protocol for carrying Authentication for
> Network Access (PANA) Relay Element functionality which enables PANA
> messaging between a PANA Client (PaC) and a PANA Authentication Agent
> (PAA) where the two nodes cannot reach each other by means of regular
> IP routing.
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 





From alper.yegin@yegin.org  Fri Jun 10 00:58:21 2011
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE0B11E80C5 for <pana@ietfa.amsl.com>; Fri, 10 Jun 2011 00:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1.449, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q+dtb2kxVOti for <pana@ietfa.amsl.com>; Fri, 10 Jun 2011 00:58:18 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 718F511E8070 for <pana@ietf.org>; Fri, 10 Jun 2011 00:58:18 -0700 (PDT)
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MTSbX-1Q5siR3jiZ-00SUn2; Fri, 10 Jun 2011 03:58:16 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yoshihiro.ohba@toshiba.co.jp>, <pana@ietf.org>
References: <4DF04217.3080304@toshiba.co.jp>
In-Reply-To: <4DF04217.3080304@toshiba.co.jp>
Date: Fri, 10 Jun 2011 10:58:09 +0300
Message-ID: <00f901cc2744$26bd95c0$7438c140$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00FA_01CC275D.4C0ACDC0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwmV92sKKfT1l1QSQusbMqX26mUtQA68rCg
Content-Language: en-us
X-Provags-ID: V02:K0:0ODwUwDsXEniBOR2T0r6xlUMvSvvoKn2iJ5gVPlL5rN ZM75/v5v8opN+I0XqkET+2V2tB2lxfH1N7TZM7F116/OLcpZtU SePPT34kfNXxmqnqM9iak7PfmCBli9M0tE5XrFatj34SY8dAJ7 mFVmk+4FrKHyE3LugQgz4K9KpK/t0sgGZlapi9vPUjVLVsgYt6 NVNCHp0/Ku3/8qRBT556j/+V0Ip3blyVioRPLnRUL8=
Subject: Re: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt> (Protocol for Carrying Authentication for Network Access (PANA) Relay Element) to Proposed Standard
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 07:58:22 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00FA_01CC275D.4C0ACDC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

 

I didn't understand why IANA assignment cares about the Req/Ans bit. Is it
really needed for IANA assignments?

 

If we need to use it, one option is to put "not applicable for PCI and PRY".

 

And if that's not acceptable/practical, then I'd say marking both PCI and
PRY with Req is OK. We could perceive them as requests that do not expect
answers. They are one-way messages. This is more logical to me than to
define an answer for which there is no outstanding request.

 

Alper

 

 

 

 

 

 

 

 

 

 

> -----Original Message-----

> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of

> Yoshihiro Ohba

> Sent: Thursday, June 09, 2011 6:47 AM

> To: pana@ietf.org

> Subject: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-

> 03.txt> (Protocol for Carrying Authentication for Network Access (PANA)

> Relay Element) to Proposed Standard

> 

> We have received the following question from IANA.

> 

> Since the 'R' (Request) bit is not set for PANA-Relay, I think it

> should be filled with "Ans" (not "Req").

> 

> BTW, I've found that PCI, for which the 'R' (Request) bit is not set,

> is filled with "Req" in the IANA registry.  I think this should have

> been filled with "Ans" as well.

> 

> Any opinions?

> 

> Yoshihiro Ohba

> 

> -------- Original Message --------

> Subject: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt>

> (Protocol for Carrying Authentication for Network Access (PANA) Relay

> Element) to Proposed Standard

> Date: Wed, 08 Jun 2011 20:37:04 +0000

> From: Amanda Baber via RT <drafts-lastcall@iana.org>

> Reply-To: drafts-lastcall@iana.org

> CC: paduffy@cisco.com, samitac2@gmail.com,

> robert.cragie@gridmerge.com, yoshihiro.ohba@toshiba.co.jp,

> alper.yegin@yegin.org, iesg@ietf.org

> 

> IESG:

> 

> IANA has reviewed draft-ohba-pana-relay-03.txt and has the following

> comments:

> 

> IANA has questions about the IANA Actions in this document.

> 

> IANA understands that, upon approval of this document, there are two

> IANA Actions that must be completed.

> 

> First, in the Message Types registry in the Protocol for Carrying

> Authentication for Network Access (PANA) Parameters registry located

> at:

> 

> http://www.iana.org/assignments/pana-parameters/pana-parameters.xml

> 

> a single, new message type will be added as follows:

> 

> Value [ TBD ]

> Name: PANA-Relay

> 

> IANA QUESTION --> How should the following field in the registry be

> filled in?

> Req/Ans: [ ??? ]

> 

> Abbrev: PRY

> Reference: [ RFC-to-be ]

> 

> IANA notes that the authors request the value "5" for the Value of this

> Message Type.

> 

> Second, in the AVP Codes registry in the the Protocol for Carrying

> Authentication for Network Access (PANA) Parameters registry located

> at:

> 

> http://www.iana.org/assignments/pana-parameters/pana-parameters.xml

> 

> two new AVP Codes will be added as follows:

> 

> Code: [tbd2]

> Attribute name: PaC-Information AVP

> Reference: [ RFC-to-be ]

> 

> Code: [tbd3]

> Attribute name: Relayed-Message AVP

> Reference: [ RFC-to-be ]

> 

> IANA notes that the authors have requested codes "10" and "11" for

> [tbd2] and [tbd3] respectively.

> 

> IANA understands that these two actions are the only ones required upon

> approval of this document.

> 

> Note:  The actions requested in this document will not be completed

> until the document has been approved for publication as an RFC. This

> message is only to confirm what actions will be performed.

> 

> Thanks,

> 

> Amanda Baber

> IANA

> 

> On Wed May 25 13:37:06 2011, noreply@ietf.org wrote:

> >

> > The IESG has received a request from an individual submitter to

> consider

> > the following document:

> > - 'Protocol for Carrying Authentication for Network Access (PANA)

> Relay

> >    Element'

> >   <draft-ohba-pana-relay-03.txt> as a Proposed Standard

> >

> > The IESG plans to make a decision in the next few weeks, and solicits

> > final comments on this action. Please send substantive comments to

> the

> > ietf@ietf.org mailing lists by 2011-06-22. Exceptionally, comments

> may be

> > sent to iesg@ietf.org instead. In either case, please retain the

> > beginning of the Subject line to allow automated sorting.

> >

> > Abstract

> >

> >

> > This document specifies Protocol for carrying Authentication for

> > Network Access (PANA) Relay Element functionality which enables PANA

> > messaging between a PANA Client (PaC) and a PANA Authentication Agent

> > (PAA) where the two nodes cannot reach each other by means of regular

> > IP routing.

> >

> >

> >

> > The file can be obtained via

> > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/

> >

> > IESG discussion can be tracked via

> > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/

> >

> >

> > No IPR declarations have been submitted directly on this I-D.

> >

> >

> 

> 

> 

> 

> _______________________________________________

> Pana mailing list

> Pana@ietf.org

> https://www.ietf.org/mailman/listinfo/pana


------=_NextPart_000_00FA_01CC275D.4C0ACDC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 92.4pt 1.0in 92.4pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>I didn't understand why IANA assignment cares =
about the
Req/Ans bit. Is it really needed for IANA assignments?<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>If we need to use it, one option is to put =
&#8220;not
applicable for PCI and PRY&#8221;.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>And if that&#8217;s not acceptable/practical, =
then I&#8217;d say marking
both PCI and PRY with Req is OK. We could perceive them as requests that =
do not
expect answers. They are one-way messages. This is more logical to me =
than to
define an answer for which there is no outstanding =
request.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Alper<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; -----Original Message-----</p>

<p class=3DMsoPlainText>&gt; From: pana-bounces@ietf.org
[mailto:pana-bounces@ietf.org] On Behalf Of</p>

<p class=3DMsoPlainText>&gt; Yoshihiro Ohba</p>

<p class=3DMsoPlainText>&gt; Sent: Thursday, June 09, 2011 6:47 AM</p>

<p class=3DMsoPlainText>&gt; To: pana@ietf.org</p>

<p class=3DMsoPlainText>&gt; Subject: [Pana] Fwd: [IANA #454490] Last =
Call:
&lt;draft-ohba-pana-relay-</p>

<p class=3DMsoPlainText>&gt; 03.txt&gt; (Protocol for Carrying =
Authentication for
Network Access (PANA)</p>

<p class=3DMsoPlainText>&gt; Relay Element) to Proposed Standard</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; We have received the following question =
from IANA.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Since the 'R' (Request) bit is not set for =
PANA-Relay,
I think it</p>

<p class=3DMsoPlainText>&gt; should be filled with &quot;Ans&quot; (not
&quot;Req&quot;).</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; BTW, I've found that PCI, for which the 'R'
(Request) bit is not set,</p>

<p class=3DMsoPlainText>&gt; is filled with &quot;Req&quot; in the IANA
registry.&nbsp; I think this should have</p>

<p class=3DMsoPlainText>&gt; been filled with &quot;Ans&quot; as =
well.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Any opinions?</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Yoshihiro Ohba</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; -------- Original Message --------</p>

<p class=3DMsoPlainText>&gt; Subject: [IANA #454490] Last Call:
&lt;draft-ohba-pana-relay-03.txt&gt;</p>

<p class=3DMsoPlainText>&gt; (Protocol for Carrying Authentication for =
Network
Access (PANA) Relay</p>

<p class=3DMsoPlainText>&gt; Element) to Proposed Standard</p>

<p class=3DMsoPlainText>&gt; Date: Wed, 08 Jun 2011 20:37:04 +0000</p>

<p class=3DMsoPlainText>&gt; From: Amanda Baber via RT
&lt;drafts-lastcall@iana.org&gt;</p>

<p class=3DMsoPlainText>&gt; Reply-To: drafts-lastcall@iana.org</p>

<p class=3DMsoPlainText>&gt; CC: paduffy@cisco.com, =
samitac2@gmail.com,</p>

<p class=3DMsoPlainText>&gt; robert.cragie@gridmerge.com,
yoshihiro.ohba@toshiba.co.jp,</p>

<p class=3DMsoPlainText>&gt; alper.yegin@yegin.org, iesg@ietf.org</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IESG:</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IANA has reviewed =
draft-ohba-pana-relay-03.txt and
has the following</p>

<p class=3DMsoPlainText>&gt; comments:</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IANA has questions about the IANA Actions =
in this
document.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IANA understands that, upon approval of =
this
document, there are two</p>

<p class=3DMsoPlainText>&gt; IANA Actions that must be completed.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; First, in the Message Types registry in the =
Protocol
for Carrying</p>

<p class=3DMsoPlainText>&gt; Authentication for Network Access (PANA) =
Parameters
registry located</p>

<p class=3DMsoPlainText>&gt; at:</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; =
http://www.iana.org/assignments/pana-parameters/pana-parameters.xml</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; a single, new message type will be added as =
follows:</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Value [ TBD ]</p>

<p class=3DMsoPlainText>&gt; Name: PANA-Relay</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IANA QUESTION --&gt; How should the =
following field
in the registry be</p>

<p class=3DMsoPlainText>&gt; filled in?</p>

<p class=3DMsoPlainText>&gt; Req/Ans: [ ??? ]</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Abbrev: PRY</p>

<p class=3DMsoPlainText>&gt; Reference: [ RFC-to-be ]</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IANA notes that the authors request the =
value
&quot;5&quot; for the Value of this</p>

<p class=3DMsoPlainText>&gt; Message Type.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Second, in the AVP Codes registry in the =
the
Protocol for Carrying</p>

<p class=3DMsoPlainText>&gt; Authentication for Network Access (PANA) =
Parameters
registry located</p>

<p class=3DMsoPlainText>&gt; at:</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; =
http://www.iana.org/assignments/pana-parameters/pana-parameters.xml</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; two new AVP Codes will be added as =
follows:</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Code: [tbd2]</p>

<p class=3DMsoPlainText>&gt; Attribute name: PaC-Information AVP</p>

<p class=3DMsoPlainText>&gt; Reference: [ RFC-to-be ]</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Code: [tbd3]</p>

<p class=3DMsoPlainText>&gt; Attribute name: Relayed-Message AVP</p>

<p class=3DMsoPlainText>&gt; Reference: [ RFC-to-be ]</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IANA notes that the authors have requested =
codes
&quot;10&quot; and &quot;11&quot; for</p>

<p class=3DMsoPlainText>&gt; [tbd2] and [tbd3] respectively.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; IANA understands that these two actions are =
the only
ones required upon</p>

<p class=3DMsoPlainText>&gt; approval of this document.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Note:&nbsp; The actions requested in this =
document will
not be completed</p>

<p class=3DMsoPlainText>&gt; until the document has been approved for =
publication
as an RFC. This</p>

<p class=3DMsoPlainText>&gt; message is only to confirm what actions =
will be
performed.</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Thanks,</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; Amanda Baber</p>

<p class=3DMsoPlainText>&gt; IANA</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; On Wed May 25 13:37:06 2011, =
noreply@ietf.org wrote:</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt; The IESG has received a request from =
an
individual submitter to</p>

<p class=3DMsoPlainText>&gt; consider</p>

<p class=3DMsoPlainText>&gt; &gt; the following document:</p>

<p class=3DMsoPlainText>&gt; &gt; - 'Protocol for Carrying =
Authentication for
Network Access (PANA)</p>

<p class=3DMsoPlainText>&gt; Relay</p>

<p class=3DMsoPlainText>&gt; &gt;&nbsp;&nbsp;&nbsp; Element'</p>

<p class=3DMsoPlainText>&gt; &gt;&nbsp;&nbsp; =
&lt;draft-ohba-pana-relay-03.txt&gt; as a
Proposed Standard</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt; The IESG plans to make a decision in =
the next
few weeks, and solicits</p>

<p class=3DMsoPlainText>&gt; &gt; final comments on this action. Please =
send
substantive comments to</p>

<p class=3DMsoPlainText>&gt; the</p>

<p class=3DMsoPlainText>&gt; &gt; ietf@ietf.org mailing lists by =
2011-06-22.
Exceptionally, comments</p>

<p class=3DMsoPlainText>&gt; may be</p>

<p class=3DMsoPlainText>&gt; &gt; sent to iesg@ietf.org instead. In =
either case,
please retain the</p>

<p class=3DMsoPlainText>&gt; &gt; beginning of the Subject line to allow
automated sorting.</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt; Abstract</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt; This document specifies Protocol for =
carrying
Authentication for</p>

<p class=3DMsoPlainText>&gt; &gt; Network Access (PANA) Relay Element
functionality which enables PANA</p>

<p class=3DMsoPlainText>&gt; &gt; messaging between a PANA Client (PaC) =
and a
PANA Authentication Agent</p>

<p class=3DMsoPlainText>&gt; &gt; (PAA) where the two nodes cannot reach =
each other
by means of regular</p>

<p class=3DMsoPlainText>&gt; &gt; IP routing.</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt; The file can be obtained via</p>

<p class=3DMsoPlainText>&gt; &gt;
http://datatracker.ietf.org/doc/draft-ohba-pana-relay/</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt; IESG discussion can be tracked via</p>

<p class=3DMsoPlainText>&gt; &gt;
http://datatracker.ietf.org/doc/draft-ohba-pana-relay/</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt; No IPR declarations have been =
submitted
directly on this I-D.</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; &gt;</p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; </p>

<p class=3DMsoPlainText>&gt; =
_______________________________________________</p>

<p class=3DMsoPlainText>&gt; Pana mailing list</p>

<p class=3DMsoPlainText>&gt; Pana@ietf.org</p>

<p class=3DMsoPlainText>&gt; =
https://www.ietf.org/mailman/listinfo/pana</p>

</div>

</body>

</html>

------=_NextPart_000_00FA_01CC275D.4C0ACDC0--


From yoshihiro.ohba@toshiba.co.jp  Fri Jun 10 23:28:47 2011
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F1111E8085 for <pana@ietfa.amsl.com>; Fri, 10 Jun 2011 23:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.245
X-Spam-Level: 
X-Spam-Status: No, score=-3.245 tagged_above=-999 required=5 tests=[AWL=-0.645, BAYES_05=-1.11, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3vMYODgObBeU for <pana@ietfa.amsl.com>; Fri, 10 Jun 2011 23:28:46 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id 2595111E8083 for <pana@ietf.org>; Fri, 10 Jun 2011 23:28:45 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id p5B6SicN028205; Sat, 11 Jun 2011 15:28:44 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id p5B6Si4d012232; Sat, 11 Jun 2011 15:28:44 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id RAA12231; Sat, 11 Jun 2011 15:28:44 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id p5B6ShUH011997; Sat, 11 Jun 2011 15:28:43 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p5B6ShkW018978; Sat, 11 Jun 2011 15:28:43 +0900 (JST)
Received: from [133.199.18.190] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LMM00IM44NVREL0@mail.po.toshiba.co.jp>; Sat, 11 Jun 2011 15:28:43 +0900 (JST)
Date: Sat, 11 Jun 2011 15:28:34 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <00f901cc2744$26bd95c0$7438c140$%yegin@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <4DF30B12.5010903@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <4DF04217.3080304@toshiba.co.jp> <00f901cc2744$26bd95c0$7438c140$%yegin@yegin.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
Cc: pana@ietf.org
Subject: Re: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt> (Protocol for Carrying Authentication for Network Access (PANA) Relay Element) to Proposed Standard
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jun 2011 06:28:47 -0000

Alper,

(2011/06/10 16:58), Alper Yegin wrote:
> I didn't understand why IANA assignment cares about the Req/Ans bit. 
> Is it really needed for IANA assignments?

I agree, Req/Ans distinction may not be needed for IANA assignments.

> 
> If we need to use it, one option is to put $B!H(Bnot applicable for PCI and 
> PRY$B!I(B.
> 
> And if that$B!G(Bs not acceptable/practical, then I$B!G(Bd say marking both PCI 
> and PRY with Req is OK. We could perceive them as requests that do not 
> expect answers. They are one-way messages. This is more logical to me 
> than to define an answer for which there is no outstanding request.
> 

I agree to respond with IANA that Req/Ans distinction is not
applicable for PCI and PRY, with a back up plan of marking both PCI
and PRY as Req.

Thanks,
Yoshihiro Ohba


> Alper
> 
>  > -----Original Message-----
> 
>  > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of
> 
>  > Yoshihiro Ohba
> 
>  > Sent: Thursday, June 09, 2011 6:47 AM
> 
>  > To: pana@ietf.org
> 
>  > Subject: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-
> 
>  > 03.txt> (Protocol for Carrying Authentication for Network Access (PANA)
> 
>  > Relay Element) to Proposed Standard
> 
>  >
> 
>  > We have received the following question from IANA.
> 
>  >
> 
>  > Since the 'R' (Request) bit is not set for PANA-Relay, I think it
> 
>  > should be filled with "Ans" (not "Req").
> 
>  >
> 
>  > BTW, I've found that PCI, for which the 'R' (Request) bit is not set,
> 
>  > is filled with "Req" in the IANA registry. I think this should have
> 
>  > been filled with "Ans" as well.
> 
>  >
> 
>  > Any opinions?
> 
>  >
> 
>  > Yoshihiro Ohba
> 
>  >
> 
>  > -------- Original Message --------
> 
>  > Subject: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt>
> 
>  > (Protocol for Carrying Authentication for Network Access (PANA) Relay
> 
>  > Element) to Proposed Standard
> 
>  > Date: Wed, 08 Jun 2011 20:37:04 +0000
> 
>  > From: Amanda Baber via RT <drafts-lastcall@iana.org>
> 
>  > Reply-To: drafts-lastcall@iana.org
> 
>  > CC: paduffy@cisco.com, samitac2@gmail.com,
> 
>  > robert.cragie@gridmerge.com, yoshihiro.ohba@toshiba.co.jp,
> 
>  > alper.yegin@yegin.org, iesg@ietf.org
> 
>  >
> 
>  > IESG:
> 
>  >
> 
>  > IANA has reviewed draft-ohba-pana-relay-03.txt and has the following
> 
>  > comments:
> 
>  >
> 
>  > IANA has questions about the IANA Actions in this document.
> 
>  >
> 
>  > IANA understands that, upon approval of this document, there are two
> 
>  > IANA Actions that must be completed.
> 
>  >
> 
>  > First, in the Message Types registry in the Protocol for Carrying
> 
>  > Authentication for Network Access (PANA) Parameters registry located
> 
>  > at:
> 
>  >
> 
>  > http://www.iana.org/assignments/pana-parameters/pana-parameters.xml
> 
>  >
> 
>  > a single, new message type will be added as follows:
> 
>  >
> 
>  > Value [ TBD ]
> 
>  > Name: PANA-Relay
> 
>  >
> 
>  > IANA QUESTION --> How should the following field in the registry be
> 
>  > filled in?
> 
>  > Req/Ans: [ ??? ]
> 
>  >
> 
>  > Abbrev: PRY
> 
>  > Reference: [ RFC-to-be ]
> 
>  >
> 
>  > IANA notes that the authors request the value "5" for the Value of this
> 
>  > Message Type.
> 
>  >
> 
>  > Second, in the AVP Codes registry in the the Protocol for Carrying
> 
>  > Authentication for Network Access (PANA) Parameters registry located
> 
>  > at:
> 
>  >
> 
>  > http://www.iana.org/assignments/pana-parameters/pana-parameters.xml
> 
>  >
> 
>  > two new AVP Codes will be added as follows:
> 
>  >
> 
>  > Code: [tbd2]
> 
>  > Attribute name: PaC-Information AVP
> 
>  > Reference: [ RFC-to-be ]
> 
>  >
> 
>  > Code: [tbd3]
> 
>  > Attribute name: Relayed-Message AVP
> 
>  > Reference: [ RFC-to-be ]
> 
>  >
> 
>  > IANA notes that the authors have requested codes "10" and "11" for
> 
>  > [tbd2] and [tbd3] respectively.
> 
>  >
> 
>  > IANA understands that these two actions are the only ones required upon
> 
>  > approval of this document.
> 
>  >
> 
>  > Note: The actions requested in this document will not be completed
> 
>  > until the document has been approved for publication as an RFC. This
> 
>  > message is only to confirm what actions will be performed.
> 
>  >
> 
>  > Thanks,
> 
>  >
> 
>  > Amanda Baber
> 
>  > IANA
> 
>  >
> 
>  > On Wed May 25 13:37:06 2011, noreply@ietf.org wrote:
> 
>  > >
> 
>  > > The IESG has received a request from an individual submitter to
> 
>  > consider
> 
>  > > the following document:
> 
>  > > - 'Protocol for Carrying Authentication for Network Access (PANA)
> 
>  > Relay
> 
>  > > Element'
> 
>  > > <draft-ohba-pana-relay-03.txt> as a Proposed Standard
> 
>  > >
> 
>  > > The IESG plans to make a decision in the next few weeks, and solicits
> 
>  > > final comments on this action. Please send substantive comments to
> 
>  > the
> 
>  > > ietf@ietf.org mailing lists by 2011-06-22. Exceptionally, comments
> 
>  > may be
> 
>  > > sent to iesg@ietf.org instead. In either case, please retain the
> 
>  > > beginning of the Subject line to allow automated sorting.
> 
>  > >
> 
>  > > Abstract
> 
>  > >
> 
>  > >
> 
>  > > This document specifies Protocol for carrying Authentication for
> 
>  > > Network Access (PANA) Relay Element functionality which enables PANA
> 
>  > > messaging between a PANA Client (PaC) and a PANA Authentication Agent
> 
>  > > (PAA) where the two nodes cannot reach each other by means of regular
> 
>  > > IP routing.
> 
>  > >
> 
>  > >
> 
>  > >
> 
>  > > The file can be obtained via
> 
>  > > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
> 
>  > >
> 
>  > > IESG discussion can be tracked via
> 
>  > > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
> 
>  > >
> 
>  > >
> 
>  > > No IPR declarations have been submitted directly on this I-D.
> 
>  > >
> 
>  > >
> 
>  >
> 
>  >
> 
>  >
> 
>  >
> 
>  > _______________________________________________
> 
>  > Pana mailing list
> 
>  > Pana@ietf.org
> 
>  > https://www.ietf.org/mailman/listinfo/pana
> 


From rdroms.ietf@gmail.com  Thu Jun 23 08:09:53 2011
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E44011E811A for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 08:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.223
X-Spam-Level: 
X-Spam-Status: No, score=-103.223 tagged_above=-999 required=5 tests=[AWL=0.375, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CbZKNfPg5Ozn for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 08:09:50 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id CE1E011E808D for <pana@ietf.org>; Thu, 23 Jun 2011 08:09:48 -0700 (PDT)
Received: by ewy19 with SMTP id 19so741765ewy.31 for <pana@ietf.org>; Thu, 23 Jun 2011 08:09:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=X/5E6sTuuD2q+UzvNhgBwQoDrU7HGA1/nyAhtf3/xks=; b=MVJl/BbMj0Rn3AVGrjbn8UDQBoLkMPcLyKtFgeVA4mv6tabfh+kaqXcqi/ASI/MGTj +k0Ngyt5b/QzYNLdD0rN+ay2BQ/4oL6EDRkmlL/fBRj+Tsg2Wa+pxmrb/+ezASVIfs5h ZV8Uc6aO6L9DoSTT3NKHikDNnmCv5Wja3DnTM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kNJwJE1SpN7xfh4oS/z9xvyb7iaCoLFkLE2dxlU+R79jCVCrwewUa7Sv2HtUKigOxd Gkp3xk81ziZAxSgmvqjCjSo/JVv8r9TRREmuj947qULObe/UtmvtYoyhoaL03VFLOQpd UP5WUsOR5jzzKypw6w+hLHMvpeKwP2V3ekCFg=
MIME-Version: 1.0
Received: by 10.14.127.68 with SMTP id c44mr1549813eei.103.1308841787452; Thu, 23 Jun 2011 08:09:47 -0700 (PDT)
Received: by 10.213.105.77 with HTTP; Thu, 23 Jun 2011 08:09:47 -0700 (PDT)
In-Reply-To: <6491375641982933760@unknownmsgid>
References: <4DF04217.3080304@toshiba.co.jp> <6491375641982933760@unknownmsgid>
Date: Thu, 23 Jun 2011 11:09:47 -0400
Message-ID: <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com>
From: Ralph Droms <rdroms.ietf@gmail.com>
To: Alper Yegin <alper.yegin@yegin.org>
Content-Type: multipart/alternative; boundary=90e6ba5bb945ceecfe04a662797d
Cc: pana@ietf.org, robert.cragie@gridmerge.com, samitac2@gmail.com, int-ads@tools.ietf.org, draft-ohba-pana-relay@tools.ietf.org
Subject: Re: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt> (Protocol for Carrying Authentication for Network Access (PANA) Relay Element) to Proposed Standard
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 15:09:53 -0000

--90e6ba5bb945ceecfe04a662797d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 10, 2011 at 3:58 AM, Alper Yegin <alper.yegin@yegin.org> wrote:

>  ** **
>
> ** **
>
> I didn't understand why IANA assignment cares about the Req/Ans bit. Is i=
t
> really needed for IANA assignments?
>

The Req/Ans column is needed to differentiate some of the messages, e.g.,
PAR and PAN, which have different abbreviations but share the same message
code.

> ****
>
> ** **
>
> If we need to use it, one option is to put =93not applicable for PCI and
> PRY=94.
>

Reading RFC 5191 and the registry, I suggest that the Message Types registr=
y
needs to be clarified a little, so that the column currently labeled Req/An=
s
is tied directly to the 'R' Message Flag in the Message Flags registry.
 Giving the exact value for the 'R' flag in that column seems more direct.
 Perhaps rename "Req/Ans" to "R Message Flag", with values in the column of
'1', '0' or 'N/A' (the latter for PCI and PRE messages; although PCI is a
little tricky as its ABNF is defined without "REQ" and I don't know if that
ABNF implies the R Message Flag MUST be 0 or if it's a "don't care").

- Ralph



****
>
> ** **
>
> And if that=92s not acceptable/practical, then I=92d say marking both PCI=
 and
> PRY with Req is OK. We could perceive them as requests that do not expect
> answers. They are one-way messages. This is more logical to me than to
> define an answer for which there is no outstanding request.****
>
> ** **
>
> Alper****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> > -----Original Message-----
>
> > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of
>
> > Yoshihiro Ohba
>
> > Sent: Thursday, June 09, 2011 6:47 AM
>
> > To: pana@ietf.org
>
> > Subject: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-
>
> > 03.txt> (Protocol for Carrying Authentication for Network Access (PANA)
>
> > Relay Element) to Proposed Standard
>
> >
>
> > We have received the following question from IANA.
>
> >
>
> > Since the 'R' (Request) bit is not set for PANA-Relay, I think it
>
> > should be filled with "Ans" (not "Req").
>
> >
>
> > BTW, I've found that PCI, for which the 'R' (Request) bit is not set,
>
> > is filled with "Req" in the IANA registry.  I think this should have
>
> > been filled with "Ans" as well.
>
> >
>
> > Any opinions?
>
> >
>
> > Yoshihiro Ohba
>
> >
>
> > -------- Original Message --------
>
> > Subject: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt>
>
> > (Protocol for Carrying Authentication for Network Access (PANA) Relay
>
> > Element) to Proposed Standard
>
> > Date: Wed, 08 Jun 2011 20:37:04 +0000
>
> > From: Amanda Baber via RT <drafts-lastcall@iana.org>
>
> > Reply-To: drafts-lastcall@iana.org
>
> > CC: paduffy@cisco.com, samitac2@gmail.com,
>
> > robert.cragie@gridmerge.com, yoshihiro.ohba@toshiba.co.jp,
>
> > alper.yegin@yegin.org, iesg@ietf.org
>
> >
>
> > IESG:
>
> >
>
> > IANA has reviewed draft-ohba-pana-relay-03.txt and has the following
>
> > comments:
>
> >
>
> > IANA has questions about the IANA Actions in this document.
>
> >
>
> > IANA understands that, upon approval of this document, there are two
>
> > IANA Actions that must be completed.
>
> >
>
> > First, in the Message Types registry in the Protocol for Carrying
>
> > Authentication for Network Access (PANA) Parameters registry located
>
> > at:
>
> >
>
> > http://www.iana.org/assignments/pana-parameters/pana-parameters.xml
>
> >
>
> > a single, new message type will be added as follows:
>
> >
>
> > Value [ TBD ]
>
> > Name: PANA-Relay
>
> >
>
> > IANA QUESTION --> How should the following field in the registry be
>
> > filled in?
>
> > Req/Ans: [ ??? ]
>
> >
>
> > Abbrev: PRY
>
> > Reference: [ RFC-to-be ]
>
> >
>
> > IANA notes that the authors request the value "5" for the Value of this
>
> > Message Type.
>
> >
>
> > Second, in the AVP Codes registry in the the Protocol for Carrying
>
> > Authentication for Network Access (PANA) Parameters registry located
>
> > at:
>
> >
>
> > http://www.iana.org/assignments/pana-parameters/pana-parameters.xml
>
> >
>
> > two new AVP Codes will be added as follows:
>
> >
>
> > Code: [tbd2]
>
> > Attribute name: PaC-Information AVP
>
> > Reference: [ RFC-to-be ]
>
> >
>
> > Code: [tbd3]
>
> > Attribute name: Relayed-Message AVP
>
> > Reference: [ RFC-to-be ]
>
> >
>
> > IANA notes that the authors have requested codes "10" and "11" for
>
> > [tbd2] and [tbd3] respectively.
>
> >
>
> > IANA understands that these two actions are the only ones required upon
>
> > approval of this document.
>
> >
>
> > Note:  The actions requested in this document will not be completed
>
> > until the document has been approved for publication as an RFC. This
>
> > message is only to confirm what actions will be performed.
>
> >
>
> > Thanks,
>
> >
>
> > Amanda Baber
>
> > IANA
>
> >
>
> > On Wed May 25 13:37:06 2011, noreply@ietf.org wrote:
>
> > >
>
> > > The IESG has received a request from an individual submitter to
>
> > consider
>
> > > the following document:
>
> > > - 'Protocol for Carrying Authentication for Network Access (PANA)
>
> > Relay
>
> > >    Element'
>
> > >   <draft-ohba-pana-relay-03.txt> as a Proposed Standard
>
> > >
>
> > > The IESG plans to make a decision in the next few weeks, and solicits
>
> > > final comments on this action. Please send substantive comments to
>
> > the
>
> > > ietf@ietf.org mailing lists by 2011-06-22. Exceptionally, comments
>
> > may be
>
> > > sent to iesg@ietf.org instead. In either case, please retain the
>
> > > beginning of the Subject line to allow automated sorting.
>
> > >
>
> > > Abstract
>
> > >
>
> > >
>
> > > This document specifies Protocol for carrying Authentication for
>
> > > Network Access (PANA) Relay Element functionality which enables PANA
>
> > > messaging between a PANA Client (PaC) and a PANA Authentication Agent
>
> > > (PAA) where the two nodes cannot reach each other by means of regular
>
> > > IP routing.
>
> > >
>
> > >
>
> > >
>
> > > The file can be obtained via
>
> > > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
>
> > >
>
> > > IESG discussion can be tracked via
>
> > > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
>
> > >
>
> > >
>
> > > No IPR declarations have been submitted directly on this I-D.
>
> > >
>
> > >
>
> >
>
> >
>
> >
>
> >
>
> > _______________________________________________
>
> > Pana mailing list
>
> > Pana@ietf.org
>
> > https://www.ietf.org/mailman/listinfo/pana
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
>
>

--90e6ba5bb945ceecfe04a662797d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Jun 10, 2011 at 3:58 AM, Alper Y=
egin <span dir=3D"ltr">&lt;<a href=3D"mailto:alper.yegin@yegin.org">alper.y=
egin@yegin.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">









<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">

<div>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p>I didn&#39;t understand why IANA assignment cares about the
Req/Ans bit. Is it really needed for IANA assignments?</p></div></div></blo=
ckquote><div><br></div><div>The Req/Ans column is needed to differentiate s=
ome of the messages, e.g., PAR and PAN, which have different abbreviations =
but share the same message code.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div lang=3D"EN-US" link=3D"blue" vlink=3D"=
purple"><div><p><u></u><u></u></p>

<p><u></u>=A0<u></u></p>

<p>If we need to use it, one option is to put =93not
applicable for PCI and PRY=94.</p></div></div></blockquote><div><br></div><=
div>Reading RFC 5191 and the registry, I suggest that the Message Types reg=
istry needs to be clarified a little, so that the column currently labeled =
Req/Ans is tied directly to the &#39;R&#39; Message Flag in the Message Fla=
gs registry. =A0Giving the exact value for the &#39;R&#39; flag in that col=
umn seems more direct. =A0Perhaps rename &quot;Req/Ans&quot; to &quot;R Mes=
sage Flag&quot;, with values in the column of &#39;1&#39;, &#39;0&#39; or &=
#39;N/A&#39; (the latter for PCI and PRE messages; although PCI is a little=
 tricky as its ABNF is defined without &quot;REQ&quot; and I don&#39;t know=
 if that ABNF implies the R Message Flag MUST be 0 or if it&#39;s a &quot;d=
on&#39;t care&quot;).</div>
<div><br></div><div>- Ralph</div><div><br></div><div><br></div><div><br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex;"><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple">
<div><p><u></u><u></u></p>

<p><u></u>=A0<u></u></p>

<p>And if that=92s not acceptable/practical, then I=92d say marking
both PCI and PRY with Req is OK. We could perceive them as requests that do=
 not
expect answers. They are one-way messages. This is more logical to me than =
to
define an answer for which there is no outstanding request.<u></u><u></u></=
p>

<p><u></u>=A0<u></u></p>

<p>Alper<u></u><u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p><u></u>=A0<u></u></p>

<p>&gt; -----Original Message-----</p>

<p>&gt; From: <a href=3D"mailto:pana-bounces@ietf.org" target=3D"_blank">pa=
na-bounces@ietf.org</a>
[mailto:<a href=3D"mailto:pana-bounces@ietf.org" target=3D"_blank">pana-bou=
nces@ietf.org</a>] On Behalf Of</p>

<p>&gt; Yoshihiro Ohba</p>

<p>&gt; Sent: Thursday, June 09, 2011 6:47 AM</p>

<p>&gt; To: <a href=3D"mailto:pana@ietf.org" target=3D"_blank">pana@ietf.or=
g</a></p>

<p>&gt; Subject: [Pana] Fwd: [IANA #454490] Last Call:
&lt;draft-ohba-pana-relay-</p><div><div></div><div class=3D"h5">

<p>&gt; 03.txt&gt; (Protocol for Carrying Authentication for
Network Access (PANA)</p>

<p>&gt; Relay Element) to Proposed Standard</p>

<p>&gt; </p>

<p>&gt; We have received the following question from IANA.</p>

<p>&gt; </p>

<p>&gt; Since the &#39;R&#39; (Request) bit is not set for PANA-Relay,
I think it</p>

<p>&gt; should be filled with &quot;Ans&quot; (not
&quot;Req&quot;).</p>

<p>&gt; </p>

<p>&gt; BTW, I&#39;ve found that PCI, for which the &#39;R&#39;
(Request) bit is not set,</p>

<p>&gt; is filled with &quot;Req&quot; in the IANA
registry.=A0 I think this should have</p>

<p>&gt; been filled with &quot;Ans&quot; as well.</p>

<p>&gt; </p>

<p>&gt; Any opinions?</p>

<p>&gt; </p>

<p>&gt; Yoshihiro Ohba</p>

<p>&gt; </p>

<p>&gt; -------- Original Message --------</p>

<p>&gt; Subject: [IANA #454490] Last Call:
&lt;draft-ohba-pana-relay-03.txt&gt;</p>

<p>&gt; (Protocol for Carrying Authentication for Network
Access (PANA) Relay</p>

<p>&gt; Element) to Proposed Standard</p>

<p>&gt; Date: Wed, 08 Jun 2011 20:37:04 +0000</p>

<p>&gt; From: Amanda Baber via RT
&lt;<a href=3D"mailto:drafts-lastcall@iana.org" target=3D"_blank">drafts-la=
stcall@iana.org</a>&gt;</p>

<p>&gt; Reply-To: <a href=3D"mailto:drafts-lastcall@iana.org" target=3D"_bl=
ank">drafts-lastcall@iana.org</a></p>

<p>&gt; CC: <a href=3D"mailto:paduffy@cisco.com" target=3D"_blank">paduffy@=
cisco.com</a>, <a href=3D"mailto:samitac2@gmail.com" target=3D"_blank">sami=
tac2@gmail.com</a>,</p>

<p>&gt; <a href=3D"mailto:robert.cragie@gridmerge.com" target=3D"_blank">ro=
bert.cragie@gridmerge.com</a>,
<a href=3D"mailto:yoshihiro.ohba@toshiba.co.jp" target=3D"_blank">yoshihiro=
.ohba@toshiba.co.jp</a>,</p>

<p>&gt; <a href=3D"mailto:alper.yegin@yegin.org" target=3D"_blank">alper.ye=
gin@yegin.org</a>, <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@=
ietf.org</a></p>

<p>&gt; </p>

<p>&gt; IESG:</p>

<p>&gt; </p>

<p>&gt; IANA has reviewed draft-ohba-pana-relay-03.txt and
has the following</p>

<p>&gt; comments:</p>

<p>&gt; </p>

<p>&gt; IANA has questions about the IANA Actions in this
document.</p>

<p>&gt; </p>

<p>&gt; IANA understands that, upon approval of this
document, there are two</p>

<p>&gt; IANA Actions that must be completed.</p>

<p>&gt; </p>

<p>&gt; First, in the Message Types registry in the Protocol
for Carrying</p>

<p>&gt; Authentication for Network Access (PANA) Parameters
registry located</p>

<p>&gt; at:</p>

<p>&gt; </p>

<p>&gt; <a href=3D"http://www.iana.org/assignments/pana-parameters/pana-par=
ameters.xml" target=3D"_blank">http://www.iana.org/assignments/pana-paramet=
ers/pana-parameters.xml</a></p>

<p>&gt; </p>

<p>&gt; a single, new message type will be added as follows:</p>

<p>&gt; </p>

<p>&gt; Value [ TBD ]</p>

<p>&gt; Name: PANA-Relay</p>

<p>&gt; </p>

<p>&gt; IANA QUESTION --&gt; How should the following field
in the registry be</p>

<p>&gt; filled in?</p>

<p>&gt; Req/Ans: [ ??? ]</p>

<p>&gt; </p>

<p>&gt; Abbrev: PRY</p>

<p>&gt; Reference: [ RFC-to-be ]</p>

<p>&gt; </p>

<p>&gt; IANA notes that the authors request the value
&quot;5&quot; for the Value of this</p>

<p>&gt; Message Type.</p>

<p>&gt; </p>

<p>&gt; Second, in the AVP Codes registry in the the
Protocol for Carrying</p>

<p>&gt; Authentication for Network Access (PANA) Parameters
registry located</p>

<p>&gt; at:</p>

<p>&gt; </p>

<p>&gt; <a href=3D"http://www.iana.org/assignments/pana-parameters/pana-par=
ameters.xml" target=3D"_blank">http://www.iana.org/assignments/pana-paramet=
ers/pana-parameters.xml</a></p>

<p>&gt; </p>

<p>&gt; two new AVP Codes will be added as follows:</p>

<p>&gt; </p>

<p>&gt; Code: [tbd2]</p>

<p>&gt; Attribute name: PaC-Information AVP</p>

<p>&gt; Reference: [ RFC-to-be ]</p>

<p>&gt; </p>

<p>&gt; Code: [tbd3]</p>

<p>&gt; Attribute name: Relayed-Message AVP</p>

<p>&gt; Reference: [ RFC-to-be ]</p>

<p>&gt; </p>

<p>&gt; IANA notes that the authors have requested codes
&quot;10&quot; and &quot;11&quot; for</p>

<p>&gt; [tbd2] and [tbd3] respectively.</p>

<p>&gt; </p>

<p>&gt; IANA understands that these two actions are the only
ones required upon</p>

<p>&gt; approval of this document.</p>

<p>&gt; </p>

<p>&gt; Note:=A0 The actions requested in this document will
not be completed</p>

<p>&gt; until the document has been approved for publication
as an RFC. This</p>

<p>&gt; message is only to confirm what actions will be
performed.</p>

<p>&gt; </p>

<p>&gt; Thanks,</p>

<p>&gt; </p>

<p>&gt; Amanda Baber</p>

<p>&gt; IANA</p>

<p>&gt; </p>

<p>&gt; On Wed May 25 13:37:06 2011, <a href=3D"mailto:noreply@ietf.org" ta=
rget=3D"_blank">noreply@ietf.org</a> wrote:</p>

<p>&gt; &gt;</p>

<p>&gt; &gt; The IESG has received a request from an
individual submitter to</p>

<p>&gt; consider</p>

<p>&gt; &gt; the following document:</p>

<p>&gt; &gt; - &#39;Protocol for Carrying Authentication for
Network Access (PANA)</p>

<p>&gt; Relay</p>

<p>&gt; &gt;=A0=A0=A0 Element&#39;</p>

<p>&gt; &gt;=A0=A0 &lt;draft-ohba-pana-relay-03.txt&gt; as a
Proposed Standard</p>

<p>&gt; &gt;</p>

<p>&gt; &gt; The IESG plans to make a decision in the next
few weeks, and solicits</p>

<p>&gt; &gt; final comments on this action. Please send
substantive comments to</p>

<p>&gt; the</p>

<p>&gt; &gt; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.o=
rg</a> mailing lists by 2011-06-22.
Exceptionally, comments</p>

<p>&gt; may be</p>

<p>&gt; &gt; sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">ies=
g@ietf.org</a> instead. In either case,
please retain the</p>

<p>&gt; &gt; beginning of the Subject line to allow
automated sorting.</p>

<p>&gt; &gt;</p>

<p>&gt; &gt; Abstract</p>

<p>&gt; &gt;</p>

<p>&gt; &gt;</p>

<p>&gt; &gt; This document specifies Protocol for carrying
Authentication for</p>

<p>&gt; &gt; Network Access (PANA) Relay Element
functionality which enables PANA</p>

<p>&gt; &gt; messaging between a PANA Client (PaC) and a
PANA Authentication Agent</p>

<p>&gt; &gt; (PAA) where the two nodes cannot reach each other
by means of regular</p>

<p>&gt; &gt; IP routing.</p>

<p>&gt; &gt;</p>

<p>&gt; &gt;</p>

<p>&gt; &gt;</p>

<p>&gt; &gt; The file can be obtained via</p>

<p>&gt; &gt;
<a href=3D"http://datatracker.ietf.org/doc/draft-ohba-pana-relay/" target=
=3D"_blank">http://datatracker.ietf.org/doc/draft-ohba-pana-relay/</a></p>

<p>&gt; &gt;</p>

<p>&gt; &gt; IESG discussion can be tracked via</p>

<p>&gt; &gt;
<a href=3D"http://datatracker.ietf.org/doc/draft-ohba-pana-relay/" target=
=3D"_blank">http://datatracker.ietf.org/doc/draft-ohba-pana-relay/</a></p>

<p>&gt; &gt;</p>

<p>&gt; &gt;</p>

<p>&gt; &gt; No IPR declarations have been submitted
directly on this I-D.</p>

<p>&gt; &gt;</p>

<p>&gt; &gt;</p>

<p>&gt; </p>

<p>&gt; </p>

<p>&gt; </p>

<p>&gt; </p>

<p>&gt; _______________________________________________</p>

<p>&gt; Pana mailing list</p>

<p>&gt; <a href=3D"mailto:Pana@ietf.org" target=3D"_blank">Pana@ietf.org</a=
></p>

<p>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pana" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/pana</a></p>

</div></div></div>

</div>


<br>_______________________________________________<br>
Pana mailing list<br>
<a href=3D"mailto:Pana@ietf.org">Pana@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pana" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/pana</a><br>
<br></blockquote></div><br>

--90e6ba5bb945ceecfe04a662797d--

From yoshihiro.ohba@toshiba.co.jp  Thu Jun 23 08:20:35 2011
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4CE09E8055 for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 08:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[AWL=0.229,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73ZTtcrveFLa for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 08:20:34 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4E09E8058 for <pana@ietf.org>; Thu, 23 Jun 2011 08:20:34 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id p5NFKM6B029352; Fri, 24 Jun 2011 00:20:22 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id p5NFKM42016451; Fri, 24 Jun 2011 00:20:22 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id AAA16450; Fri, 24 Jun 2011 00:20:22 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id p5NFKLj4007006; Fri, 24 Jun 2011 00:20:21 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p5NFKLai026252; Fri, 24 Jun 2011 00:20:21 +0900 (JST)
Received: from [133.199.17.57] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LN900A0Q19X6YD0@mail.po.toshiba.co.jp>; Fri, 24 Jun 2011 00:20:21 +0900 (JST)
Date: Fri, 24 Jun 2011 00:20:10 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Message-id: <4E0359AA.9020008@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <4DF04217.3080304@toshiba.co.jp> <6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
Cc: pana@ietf.org, robert.cragie@gridmerge.com, samitac2@gmail.com, int-ads@tools.ietf.org, draft-ohba-pana-relay@tools.ietf.org
Subject: Re: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt> (Protocol for Carrying Authentication for Network Access (PANA) Relay Element) to Proposed Standard
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 15:20:35 -0000

I agree with Ralph's suggestion to rename "Req/Ans" to "R Message
Flag".   In that case, the value in the column shall be either '1' or
'0' (and no 'N/A').

Regards,
Yoshihiro Ohba


(2011/06/24 0:09), Ralph Droms wrote:
> 
> 
> On Fri, Jun 10, 2011 at 3:58 AM, Alper Yegin <alper.yegin@yegin.org 
> <mailto:alper.yegin@yegin.org>> wrote:
> 
>     __ __
> 
>     __ __
> 
>     I didn't understand why IANA assignment cares about the Req/Ans
>     bit. Is it really needed for IANA assignments?
> 
> 
> The Req/Ans column is needed to differentiate some of the messages, 
> e.g., PAR and PAN, which have different abbreviations but share the 
> same message code.
> 
>     ____
> 
>     __ __
> 
>     If we need to use it, one option is to put $B!H(Bnot applicable for PCI
>     and PRY$B!I(B.
> 
> 
> Reading RFC 5191 and the registry, I suggest that the Message Types 
> registry needs to be clarified a little, so that the column currently 
> labeled Req/Ans is tied directly to the 'R' Message Flag in the 
> Message Flags registry.  Giving the exact value for the 'R' flag in 
> that column seems more direct.  Perhaps rename "Req/Ans" to "R Message 
> Flag", with values in the column of '1', '0' or 'N/A' (the latter for 
> PCI and PRE messages; although PCI is a little tricky as its ABNF is 
> defined without "REQ" and I don't know if that ABNF implies the R 
> Message Flag MUST be 0 or if it's a "don't care").
> 
> - Ralph
> 
> 
> 
>     ____
> 
>     __ __
> 
>     And if that$B!G(Bs not acceptable/practical, then I$B!G(Bd say marking both
>     PCI and PRY with Req is OK. We could perceive them as requests
>     that do not expect answers. They are one-way messages. This is
>     more logical to me than to define an answer for which there is no
>     outstanding request.____
> 
>     __ __
> 
>     Alper____
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>      > -----Original Message-----
> 
>      > From: pana-bounces@ietf.org <mailto:pana-bounces@ietf.org>
>     [mailto:pana-bounces@ietf.org <mailto:pana-bounces@ietf.org>] On
>     Behalf Of
> 
>      > Yoshihiro Ohba
> 
>      > Sent: Thursday, June 09, 2011 6:47 AM
> 
>      > To: pana@ietf.org <mailto:pana@ietf.org>
> 
>      > Subject: [Pana] Fwd: [IANA #454490] Last Call:
>     <draft-ohba-pana-relay-
> 
>      > 03.txt> (Protocol for Carrying Authentication for Network
>     Access (PANA)
> 
>      > Relay Element) to Proposed Standard
> 
>      >
> 
>      > We have received the following question from IANA.
> 
>      >
> 
>      > Since the 'R' (Request) bit is not set for PANA-Relay, I think it
> 
>      > should be filled with "Ans" (not "Req").
> 
>      >
> 
>      > BTW, I've found that PCI, for which the 'R' (Request) bit is
>     not set,
> 
>      > is filled with "Req" in the IANA registry.  I think this should
>     have
> 
>      > been filled with "Ans" as well.
> 
>      >
> 
>      > Any opinions?
> 
>      >
> 
>      > Yoshihiro Ohba
> 
>      >
> 
>      > -------- Original Message --------
> 
>      > Subject: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt>
> 
>      > (Protocol for Carrying Authentication for Network Access (PANA)
>     Relay
> 
>      > Element) to Proposed Standard
> 
>      > Date: Wed, 08 Jun 2011 20:37:04 +0000
> 
>      > From: Amanda Baber via RT <drafts-lastcall@iana.org
>     <mailto:drafts-lastcall@iana.org>>
> 
>      > Reply-To: drafts-lastcall@iana.org
>     <mailto:drafts-lastcall@iana.org>
> 
>      > CC: paduffy@cisco.com <mailto:paduffy@cisco.com>,
>     samitac2@gmail.com <mailto:samitac2@gmail.com>,
> 
>      > robert.cragie@gridmerge.com
>     <mailto:robert.cragie@gridmerge.com>, yoshihiro.ohba@toshiba.co.jp
>     <mailto:yoshihiro.ohba@toshiba.co.jp>,
> 
>      > alper.yegin@yegin.org <mailto:alper.yegin@yegin.org>,
>     iesg@ietf.org <mailto:iesg@ietf.org>
> 
>      >
> 
>      > IESG:
> 
>      >
> 
>      > IANA has reviewed draft-ohba-pana-relay-03.txt and has the
>     following
> 
>      > comments:
> 
>      >
> 
>      > IANA has questions about the IANA Actions in this document.
> 
>      >
> 
>      > IANA understands that, upon approval of this document, there
>     are two
> 
>      > IANA Actions that must be completed.
> 
>      >
> 
>      > First, in the Message Types registry in the Protocol for Carrying
> 
>      > Authentication for Network Access (PANA) Parameters registry
>     located
> 
>      > at:
> 
>      >
> 
>      > http://www.iana.org/assignments/pana-parameters/pana-parameters.xml
> 
>      >
> 
>      > a single, new message type will be added as follows:
> 
>      >
> 
>      > Value [ TBD ]
> 
>      > Name: PANA-Relay
> 
>      >
> 
>      > IANA QUESTION --> How should the following field in the registry be
> 
>      > filled in?
> 
>      > Req/Ans: [ ??? ]
> 
>      >
> 
>      > Abbrev: PRY
> 
>      > Reference: [ RFC-to-be ]
> 
>      >
> 
>      > IANA notes that the authors request the value "5" for the Value
>     of this
> 
>      > Message Type.
> 
>      >
> 
>      > Second, in the AVP Codes registry in the the Protocol for Carrying
> 
>      > Authentication for Network Access (PANA) Parameters registry
>     located
> 
>      > at:
> 
>      >
> 
>      > http://www.iana.org/assignments/pana-parameters/pana-parameters.xml
> 
>      >
> 
>      > two new AVP Codes will be added as follows:
> 
>      >
> 
>      > Code: [tbd2]
> 
>      > Attribute name: PaC-Information AVP
> 
>      > Reference: [ RFC-to-be ]
> 
>      >
> 
>      > Code: [tbd3]
> 
>      > Attribute name: Relayed-Message AVP
> 
>      > Reference: [ RFC-to-be ]
> 
>      >
> 
>      > IANA notes that the authors have requested codes "10" and "11" for
> 
>      > [tbd2] and [tbd3] respectively.
> 
>      >
> 
>      > IANA understands that these two actions are the only ones
>     required upon
> 
>      > approval of this document.
> 
>      >
> 
>      > Note:  The actions requested in this document will not be completed
> 
>      > until the document has been approved for publication as an RFC.
>     This
> 
>      > message is only to confirm what actions will be performed.
> 
>      >
> 
>      > Thanks,
> 
>      >
> 
>      > Amanda Baber
> 
>      > IANA
> 
>      >
> 
>      > On Wed May 25 13:37:06 2011, noreply@ietf.org
>     <mailto:noreply@ietf.org> wrote:
> 
>      > >
> 
>      > > The IESG has received a request from an individual submitter to
> 
>      > consider
> 
>      > > the following document:
> 
>      > > - 'Protocol for Carrying Authentication for Network Access (PANA)
> 
>      > Relay
> 
>      > >    Element'
> 
>      > > <draft-ohba-pana-relay-03.txt> as a Proposed Standard
> 
>      > >
> 
>      > > The IESG plans to make a decision in the next few weeks, and
>     solicits
> 
>      > > final comments on this action. Please send substantive
>     comments to
> 
>      > the
> 
>      > > ietf@ietf.org <mailto:ietf@ietf.org> mailing lists by
>     2011-06-22. Exceptionally, comments
> 
>      > may be
> 
>      > > sent to iesg@ietf.org <mailto:iesg@ietf.org> instead. In
>     either case, please retain the
> 
>      > > beginning of the Subject line to allow automated sorting.
> 
>      > >
> 
>      > > Abstract
> 
>      > >
> 
>      > >
> 
>      > > This document specifies Protocol for carrying Authentication for
> 
>      > > Network Access (PANA) Relay Element functionality which
>     enables PANA
> 
>      > > messaging between a PANA Client (PaC) and a PANA
>     Authentication Agent
> 
>      > > (PAA) where the two nodes cannot reach each other by means of
>     regular
> 
>      > > IP routing.
> 
>      > >
> 
>      > >
> 
>      > >
> 
>      > > The file can be obtained via
> 
>      > > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
> 
>      > >
> 
>      > > IESG discussion can be tracked via
> 
>      > > http://datatracker.ietf.org/doc/draft-ohba-pana-relay/
> 
>      > >
> 
>      > >
> 
>      > > No IPR declarations have been submitted directly on this I-D.
> 
>      > >
> 
>      > >
> 
>      >
> 
>      >
> 
>      >
> 
>      >
> 
>      > _______________________________________________
> 
>      > Pana mailing list
> 
>      > Pana@ietf.org <mailto:Pana@ietf.org>
> 
>      > https://www.ietf.org/mailman/listinfo/pana
> 
> 
>     _______________________________________________
>     Pana mailing list
>     Pana@ietf.org <mailto:Pana@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pana
> 
> 


From jari.arkko@piuha.net  Thu Jun 23 10:40:52 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE7711E817E for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 10:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.465
X-Spam-Level: 
X-Spam-Status: No, score=-102.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ia4do2xIuuuX for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 10:40:51 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 7C38911E8172 for <pana@ietf.org>; Thu, 23 Jun 2011 10:40:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 695AC2CC3B; Thu, 23 Jun 2011 20:40:46 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YRZxBVbGBEBN; Thu, 23 Jun 2011 20:40:46 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id D1BB62CC2F; Thu, 23 Jun 2011 20:40:45 +0300 (EEST)
Message-ID: <4E037A9D.8080200@piuha.net>
Date: Thu, 23 Jun 2011 20:40:45 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>, pana@ietf.org
References: <4DF04217.3080304@toshiba.co.jp>	<6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com>
In-Reply-To: <4E037743.2060602@gridmerge.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ohba-pana-relay@tools.ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 17:40:52 -0000

We discussed this draft today. The remaining Discuss was about how 
mandatory we should make IPsec. You had discussed about a SHOULD with 
Stephen. I suggested that while interoperability is useful and 
mandatory-to-implement mechanisms are good for it, we also have to talk 
about how much value we bring with a security mechanism. In this case 
there are some issues like MITMs able to block PANA packets. However, 
some of these vulnerabilities are not helped by relay - PAA security, as 
the relay can still do bad things, and because ARP/ND vulnerabilities 
between the client and relay in any case make it possible to become a 
MITM. Stephen had some suggested text that I agree with:

"PRE/PAA security is OPTIONAL since PANA messages are designed to be 
used in untrusted networks, but if cryptographic mechanism is supported, 
it SHOULD be IPsec."

Jari


From yoshihiro.ohba@toshiba.co.jp  Thu Jun 23 15:44:47 2011
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76C3711E8084 for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 15:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nMba3uBv6p8g for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 15:44:47 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id AED5E11E8078 for <pana@ietf.org>; Thu, 23 Jun 2011 15:44:46 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id p5NMiSWQ008261; Fri, 24 Jun 2011 07:44:28 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id p5NMiSmF017927; Fri, 24 Jun 2011 07:44:28 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id HAA17925; Fri, 24 Jun 2011 07:44:28 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id p5NMiRFs002581; Fri, 24 Jun 2011 07:44:28 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p5NMiR5S020440; Fri, 24 Jun 2011 07:44:27 +0900 (JST)
Received: from [133.196.17.93] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LN900AP9LU36XG0@mail.po.toshiba.co.jp>; Fri, 24 Jun 2011 07:44:27 +0900 (JST)
Date: Fri, 24 Jun 2011 07:44:17 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <4E0381D0.9090605@gridmerge.com>
To: robert.cragie@gridmerge.com
Message-id: <4E03C1C1.3060701@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <4DF04217.3080304@toshiba.co.jp> <6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com> <4E037A9D.8080200@piuha.net> <16D60F43CA0B724F8052D7E9323565D71E66160BE8@EUSAACMS0715.eamcs.ericsson.se> <4E0381D0.9090605@gridmerge.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
Cc: "draft-ohba-pana-relay@tools.ietf.org" <draft-ohba-pana-relay@tools.ietf.org>, Samita Chakrabarti <samita.chakrabarti@ericsson.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "pana@ietf.org" <pana@ietf.org>
Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 22:44:47 -0000

+1.

Yoshihiro Ohba

(2011/06/24 3:11), Robert Cragie wrote:
> I have no objection to either the text below or what was agreed with 
> Stephen earlier. On balance, I think the text below is preferable.
> 
> Robert
> 
> On 23/06/2011 6:47 PM, Samita Chakrabarti wrote:
>> As a co-author of the document, I am fine with the suggested text 
>> below.
>>
>> -Samita
>>
>> -----Original Message-----
>> From: Jari Arkko [mailto:jari.arkko@piuha.net]
>> Sent: Thursday, June 23, 2011 10:41 AM
>> To: Yoshihiro Ohba; pana@ietf.org
>> Cc: Stephen Farrell; draft-ohba-pana-relay@tools.ietf.org
>> Subject: IESG discussions on draft-ohba-pana-relay
>>
>> We discussed this draft today. The remaining Discuss was about how 
>> mandatory we should make IPsec. You had discussed about a SHOULD 
>> with Stephen. I suggested that while interoperability is useful and 
>> mandatory-to-implement mechanisms are good for it, we also have to 
>> talk about how much value we bring with a security mechanism. In 
>> this case there are some issues like MITMs able to block PANA 
>> packets. However, some of these vulnerabilities are not helped by 
>> relay - PAA security, as the relay can still do bad things, and 
>> because ARP/ND vulnerabilities between the client and relay in any 
>> case make it possible to become a MITM. Stephen had some suggested 
>> text that I agree with:
>>
>> "PRE/PAA security is OPTIONAL since PANA messages are designed to be 
>> used in untrusted networks, but if cryptographic mechanism is 
>> supported, it SHOULD be IPsec."
>>
>> Jari
>>
>>
> 


From yoshihiro.ohba@toshiba.co.jp  Thu Jun 23 17:12:34 2011
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 339F911E8084 for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 17:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQ9MPWBAIqj7 for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 17:12:33 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id B20A611E807C for <pana@ietf.org>; Thu, 23 Jun 2011 17:12:32 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id p5O0CMTc017245; Fri, 24 Jun 2011 09:12:22 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id p5O0CMbx007146; Fri, 24 Jun 2011 09:12:22 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id KAA07143; Fri, 24 Jun 2011 09:12:22 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id p5O0CLTa013959; Fri, 24 Jun 2011 09:12:22 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p5O0CLDI014264; Fri, 24 Jun 2011 09:12:21 +0900 (JST)
Received: from [133.196.17.93] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LN900AGDPWL6XJ0@mail.po.toshiba.co.jp>; Fri, 24 Jun 2011 09:12:21 +0900 (JST)
Date: Fri, 24 Jun 2011 09:12:10 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <4E038264.1080602@gridmerge.com>
To: robert.cragie@gridmerge.com
Message-id: <4E03D65A.8030702@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <4DF04217.3080304@toshiba.co.jp> <6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com> <4E037F0D.3060508@gridmerge.com> <4E038264.1080602@gridmerge.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
Cc: pana@ietf.org, draft-ohba-pana-relay@tools.ietf.org, Ralph Droms <rdroms.ietf@gmail.com>, samitac2@gmail.com, int-ads@tools.ietf.org
Subject: Re: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt> (Protocol for Carrying Authentication for Network Access (PANA) Relay Element) to Proposed Standard
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 00:12:34 -0000

This table looks good to me.

Thanks,
Yoshihiro Ohba


(2011/06/24 3:13), Robert Cragie wrote:
> Too hasty with the cut and paste (too many PTR/PTA). Revised table:
> 
> Value        | R flag | Abbrev | Name                      | Reference |
> ------------------------------------------------------------------------
>   0           |        |        | Reserved                  | [RFC5191] |
>   1           | 0      | PCI    | PANA-Client-Initiation    | [RFC5191] |
>   2           | 1      | PAR    | PANA-Auth-Request         | [RFC5191] |
>   2           | 0      | PAN    | PANA-Auth-Answer          | [RFC5191] |
>   3           | 1      | PTR    | PANA-Termination-Request  | [RFC5191] |
>   3           | 0      | PTA    | PANA-Termination-Answer   | [RFC5191] |
>   4           | 1      | PNR    | PANA-Notification-Request | [RFC5191] |
>   4           | 0      | PNA    | PANA-Notification-Answer  | [RFC5191] |
>   5           | 0      | PRY    | PANA-Relay                | [RFCxxxx] |
>   6-65519     |        |        | Unassigned                | [RFC5191] |
>   65520-65535 |        |        | Reserved (Experimental)   | [RFC5191] |
> 
> On 23/06/2011 6:59 PM, Robert Cragie wrote:
>> As a follow up: as I read it in RFC 5191, the ABNF for PCI 
>> explicitly sets the R flag to 0. In some respects, given the 
>> definition of the R flag, this implies PCI is an answer, which is 
>> not really true. I don't know how important that is; it is used 
>> primarily for subclassifying a Message Type.
>>
>> On that basis, I think the table needs to look something like:
>>
>> Value        | R flag | Abbrev | Name                      | Reference |
>> ------------------------------------------------------------------------
>>  0           |        |        | Reserved                  | [RFC5191] |
>>  1           | 0      | PCI    | PANA-Client-Initiation    | [RFC5191] |
>>  2           | 1      | PAR    | PANA-Auth-Request         | [RFC5191] |
>>  2           | 0      | PAN    | PANA-Auth-Answer          | [RFC5191] |
>>  3           | 1      | PTR    | PANA-Termination-Request  | [RFC5191] |
>>  3           | 0      | PTA    | PANA-Termination-Answer   | [RFC5191] |
>>  4           | 1      | PTR    | PANA-Notification-Request | [RFC5191] |
>>  4           | 0      | PTA    | PANA-Notification-Answer  | [RFC5191] |
>>  5           | 0      | PRY    | PANA-Relay                | [RFCxxxx] |
>>  6-65519     |        |        | Unassigned                | [RFC5191] |
>>  65520-65535 |        |        | Reserved (Experimental)   | [RFC5191] |
>>
>>
>> Robert
>>
>> On 23/06/2011 6:26 PM, Robert Cragie wrote:
>>> Ralph,
>>>
>>> I like your suggestion for the Message Types registry. I guess 
>>> there is an assumption if the field is not declared in the ABNF it 
>>> becomes the same as reserved and thus follows the "set to zero and 
>>> ignored on receipt" rule. Does this need to be explicitly stated 
>>> anywhere?
>>>
>>> Robert
>>>
>>


From gwz@net-zen.net  Thu Jun 23 18:39:18 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB32A11E81B6 for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 18:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOFd2W49vzjd for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 18:39:18 -0700 (PDT)
Received: from smtpauth12.prod.mesa1.secureserver.net (smtpauth12.prod.mesa1.secureserver.net [64.202.165.35]) by ietfa.amsl.com (Postfix) with SMTP id 490DF11E80A2 for <pana@ietf.org>; Thu, 23 Jun 2011 18:39:18 -0700 (PDT)
Received: (qmail 22794 invoked from network); 24 Jun 2011 01:39:17 -0000
Received: from unknown (124.122.156.23) by smtpauth12.prod.mesa1.secureserver.net (64.202.165.35) with ESMTP; 24 Jun 2011 01:39:16 -0000
Message-ID: <4E03EABF.501@net-zen.net>
Date: Fri, 24 Jun 2011 08:39:11 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4DF04217.3080304@toshiba.co.jp>	<6491375641982933760@unknownmsgid>	<BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com>	<4E037743.2060602@gridmerge.com> <4E037A9D.8080200@piuha.net>
In-Reply-To: <4E037A9D.8080200@piuha.net>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------060708000504060207020101"
Cc: draft-ohba-pana-relay@tools.ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>, pana@ietf.org
Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 01:39:19 -0000

This is a multi-part message in MIME format.
--------------060708000504060207020101
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 6/24/2011 12:40 AM, Jari Arkko wrote:

> We discussed this draft today. The remaining Discuss was about how
> mandatory we should make IPsec. You had discussed about a SHOULD with
> Stephen. I suggested that while interoperability is useful and
> mandatory-to-implement mechanisms are good for it, we also have to talk
> about how much value we bring with a security mechanism. In this case
> there are some issues like MITMs able to block PANA packets. However,
> some of these vulnerabilities are not helped by relay - PAA security, as
> the relay can still do bad things, and because ARP/ND vulnerabilities
> between the client and relay in any case make it possible to become a
> MITM. Stephen had some suggested text that I agree with:
> 
> "PRE/PAA security is OPTIONAL since PANA messages are designed to be
> used in untrusted networks, but if cryptographic mechanism is supported,
> it SHOULD be IPsec."

This is an interesting statement.  Just one question: if it is not
possible to use the protocol in a secure fashion (the claim being that
MITM attacks are impossible to prevent), how is it that the protocol is
"designed to be used in untrusted networks"?

...

--------------060708000504060207020101
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------060708000504060207020101--

From alper.yegin@yegin.org  Fri Jun 24 00:52:07 2011
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE6C11E8090 for <pana@ietfa.amsl.com>; Fri, 24 Jun 2011 00:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djzXYECHkjwX for <pana@ietfa.amsl.com>; Fri, 24 Jun 2011 00:52:06 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id AFFE811E8089 for <pana@ietf.org>; Fri, 24 Jun 2011 00:52:06 -0700 (PDT)
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MePod-1Qxtz02sN5-00QGEA; Fri, 24 Jun 2011 03:52:01 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yoshihiro.ohba@toshiba.co.jp>, <robert.cragie@gridmerge.com>
References: <4DF04217.3080304@toshiba.co.jp> <6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com> <4E037F0D.3060508@gridmerge.com> <4E038264.1080602@gridmerge.com> <4E03D65A.8030702@toshiba.co.jp>
In-Reply-To: <4E03D65A.8030702@toshiba.co.jp>
Date: Fri, 24 Jun 2011 10:51:37 +0300
Message-ID: <020f01cc3243$943f5d40$bcbe17c0$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwyA3EOkl19+AAZSdenRtjyRNiTTgAQBacw
Content-Language: en-us
X-Provags-ID: V02:K0:gQvUhpOuP/w/L5559n6Mj+haKG+2BDOLwY1M/r2+v0y dLpIDwmVlMf7rtPIFW92WyPoVH6BPCs7o+bu1CLQSnb/PTJFcY F/rDxKr9IjfILUyOlMJwLBjxXrNM92zSwBmIkKHUhhlKhgoYwX C6UYkq1U8yezWF/LWDyivGhtGFNUfcuIfWskeb/KeQf6mtCzuK 7+pWyWcgE5KDX9EFu+Bg23D994B9Dq65ZqIf5LQ8WQ=
Cc: pana@ietf.org, draft-ohba-pana-relay@tools.ietf.org, 'Ralph Droms' <rdroms.ietf@gmail.com>, samitac2@gmail.com, int-ads@tools.ietf.org
Subject: Re: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-relay-03.txt> (Protocol for Carrying Authentication for Network Access (PANA) Relay Element) to Proposed Standard
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 07:52:07 -0000

Let's go with this.


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp]
> Sent: Friday, June 24, 2011 3:12 AM
> To: robert.cragie@gridmerge.com
> Cc: Ralph Droms; Alper Yegin; int-ads@tools.ietf.org; pana@ietf.org;
> paduffy@cisco.com; samitac2@gmail.com; draft-ohba-pana-
> relay@tools.ietf.org; margaretw42@gmail.com
> Subject: Re: [Pana] Fwd: [IANA #454490] Last Call: <draft-ohba-pana-
> relay-03.txt> (Protocol for Carrying Authentication for Network Access
> (PANA) Relay Element) to Proposed Standard
> 
> This table looks good to me.
> 
> Thanks,
> Yoshihiro Ohba
> 
> 
> (2011/06/24 3:13), Robert Cragie wrote:
> > Too hasty with the cut and paste (too many PTR/PTA). Revised table:
> >
> > Value        | R flag | Abbrev | Name                      |
> Reference |
> > ---------------------------------------------------------------------
> ---
> >   0           |        |        | Reserved                  |
> [RFC5191] |
> >   1           | 0      | PCI    | PANA-Client-Initiation    |
> [RFC5191] |
> >   2           | 1      | PAR    | PANA-Auth-Request         |
> [RFC5191] |
> >   2           | 0      | PAN    | PANA-Auth-Answer          |
> [RFC5191] |
> >   3           | 1      | PTR    | PANA-Termination-Request  |
> [RFC5191] |
> >   3           | 0      | PTA    | PANA-Termination-Answer   |
> [RFC5191] |
> >   4           | 1      | PNR    | PANA-Notification-Request |
> [RFC5191] |
> >   4           | 0      | PNA    | PANA-Notification-Answer  |
> [RFC5191] |
> >   5           | 0      | PRY    | PANA-Relay                |
> [RFCxxxx] |
> >   6-65519     |        |        | Unassigned                |
> [RFC5191] |
> >   65520-65535 |        |        | Reserved (Experimental)   |
> [RFC5191] |
> >
> > On 23/06/2011 6:59 PM, Robert Cragie wrote:
> >> As a follow up: as I read it in RFC 5191, the ABNF for PCI
> >> explicitly sets the R flag to 0. In some respects, given the
> >> definition of the R flag, this implies PCI is an answer, which is
> >> not really true. I don't know how important that is; it is used
> >> primarily for subclassifying a Message Type.
> >>
> >> On that basis, I think the table needs to look something like:
> >>
> >> Value        | R flag | Abbrev | Name                      |
> Reference |
> >> --------------------------------------------------------------------
> ----
> >>  0           |        |        | Reserved                  |
> [RFC5191] |
> >>  1           | 0      | PCI    | PANA-Client-Initiation    |
> [RFC5191] |
> >>  2           | 1      | PAR    | PANA-Auth-Request         |
> [RFC5191] |
> >>  2           | 0      | PAN    | PANA-Auth-Answer          |
> [RFC5191] |
> >>  3           | 1      | PTR    | PANA-Termination-Request  |
> [RFC5191] |
> >>  3           | 0      | PTA    | PANA-Termination-Answer   |
> [RFC5191] |
> >>  4           | 1      | PTR    | PANA-Notification-Request |
> [RFC5191] |
> >>  4           | 0      | PTA    | PANA-Notification-Answer  |
> [RFC5191] |
> >>  5           | 0      | PRY    | PANA-Relay                |
> [RFCxxxx] |
> >>  6-65519     |        |        | Unassigned                |
> [RFC5191] |
> >>  65520-65535 |        |        | Reserved (Experimental)   |
> [RFC5191] |
> >>
> >>
> >> Robert
> >>
> >> On 23/06/2011 6:26 PM, Robert Cragie wrote:
> >>> Ralph,
> >>>
> >>> I like your suggestion for the Message Types registry. I guess
> >>> there is an assumption if the field is not declared in the ABNF it
> >>> becomes the same as reserved and thus follows the "set to zero and
> >>> ignored on receipt" rule. Does this need to be explicitly stated
> >>> anywhere?
> >>>
> >>> Robert
> >>>
> >>


From alper.yegin@yegin.org  Fri Jun 24 01:10:10 2011
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A56C11E8089 for <pana@ietfa.amsl.com>; Fri, 24 Jun 2011 01:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PmARxJLHWs65 for <pana@ietfa.amsl.com>; Fri, 24 Jun 2011 01:10:09 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 1864711E8087 for <pana@ietf.org>; Fri, 24 Jun 2011 01:10:09 -0700 (PDT)
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0Lon23-1RGo7S2FA3-00fx6P; Fri, 24 Jun 2011 04:09:40 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Jari Arkko'" <jari.arkko@piuha.net>, "'Yoshihiro Ohba'" <yoshihiro.ohba@toshiba.co.jp>, <pana@ietf.org>
References: <4DF04217.3080304@toshiba.co.jp>	<6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com> <4E037A9D.8080200@piuha.net>
In-Reply-To: <4E037A9D.8080200@piuha.net>
Date: Fri, 24 Jun 2011 11:09:21 +0300
Message-ID: <021a01cc3246$0b890390$229b0ab0$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwxzLSaaiXIpFF7SoaV+7DotegRqwAd597g
Content-Language: en-us
X-Provags-ID: V02:K0:j7DiO5+X4D/Xs4laS04ohoSkbpqRyGZ6pGJ1tj5ofVh mbdG+j+3of4z7elY+Q9gUllx0EMyvdreShfa6/dY/7r43bb9Gj j4LuV91mTxz8VHVfaDA8x4ppoEgQGxmFQ9ItxvXWSTzgVYVF3a O3k2JPUDBFpbvPSTBAcwTFgzuzk/YZzuZ29KugigV4ZMHmCmG+ 0hs4oGkl5uHmoK+vg8M8hpD2uKJ4H+HFMcaeE3/SSM=
Cc: draft-ohba-pana-relay@tools.ietf.org, 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>
Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 08:10:10 -0000

I think importing text from the other one Stephen had suggested would be an
improvement. Like this:


3. Security of Messages Sent between PRE and PAA

PRE/PAA security is OPTIONAL since PANA messages are designed to be
used in untrusted networks, but if cryptographic mechanism is
supported, it SHOULD be IPsec. When the device characteristics preclude
support for IPsec, an alternative mechanism such as DTLS [REF], or
link-layer cryptographic security, etc. may be used instead. This section
describes how IPsec [RFC4301] can be used for securing the PANA relay
messages.

Alper




> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]
> Sent: Thursday, June 23, 2011 8:41 PM
> To: Yoshihiro Ohba; pana@ietf.org
> Cc: Stephen Farrell; draft-ohba-pana-relay@tools.ietf.org
> Subject: IESG discussions on draft-ohba-pana-relay
> 
> We discussed this draft today. The remaining Discuss was about how
> mandatory we should make IPsec. You had discussed about a SHOULD with
> Stephen. I suggested that while interoperability is useful and
> mandatory-to-implement mechanisms are good for it, we also have to talk
> about how much value we bring with a security mechanism. In this case
> there are some issues like MITMs able to block PANA packets. However,
> some of these vulnerabilities are not helped by relay - PAA security,
> as
> the relay can still do bad things, and because ARP/ND vulnerabilities
> between the client and relay in any case make it possible to become a
> MITM. Stephen had some suggested text that I agree with:
> 
> "PRE/PAA security is OPTIONAL since PANA messages are designed to be
> used in untrusted networks, but if cryptographic mechanism is
> supported,
> it SHOULD be IPsec."
> 
> Jari


From alper.yegin@yegin.org  Fri Jun 24 02:29:13 2011
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE5EE21F854C for <pana@ietfa.amsl.com>; Fri, 24 Jun 2011 02:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wyysWIEJyC4 for <pana@ietfa.amsl.com>; Fri, 24 Jun 2011 02:29:13 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 7C07221F854A for <pana@ietf.org>; Fri, 24 Jun 2011 02:29:13 -0700 (PDT)
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MPF2u-1QeQPM3aEq-004oeq; Fri, 24 Jun 2011 05:29:08 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Carsten Bormann'" <cabo@tzi.org>
References: <4DF04217.3080304@toshiba.co.jp>	<6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com> <4E037A9D.8080200@piuha.net> <021a01cc3246$0b890390$229b0ab0$@yegin@yegin.org> <E42296DA-CE9A-408C-AF9C-D2F5A3AD3AFE@tzi.org>
In-Reply-To: <E42296DA-CE9A-408C-AF9C-D2F5A3AD3AFE@tzi.org>
Date: Fri, 24 Jun 2011 12:28:48 +0300
Message-ID: <027601cc3251$25ba06f0$712e14d0$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwyTC69x8mAZjI7RC+CPJltAZf4OAABFcgQ
Content-Language: en-us
X-Provags-ID: V02:K0:IpDFK+FvcbHZK+rwsPIjRywlHCnZXTd03MapoL0pbAn CnTMvV4HuIafYwAYPWCl4zDy35j0fyMg2OFFRs/w6rC9GVwZbh eg6WWT0wxi4jJ6YFiMOHZTbgAXWzNf7y6yzh/2hImEhgjILTCf mbr1YprP97PYTy8TVMyJr78knzGTvt60Wo6pzAh20SOa1pvKjQ R/fRRAJ1hriUxSIJ0M4Gim8EGnVWF8eoIkoxUWUhB0=
Cc: draft-ohba-pana-relay@tools.ietf.org, 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>, pana@ietf.org
Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 09:29:14 -0000

Carsten,

Section 6. Security Considerations talks about the threats, some of which
are already handled by the base EAP/PANA design. Other threats that are
relevant to introduction of the PRE, they are described and the PRE-PAA
security is pointed accordingly.

Alper




> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org]
> Sent: Friday, June 24, 2011 11:52 AM
> To: Alper Yegin
> Cc: 'Jari Arkko'; 'Yoshihiro Ohba'; pana@ietf.org; draft-ohba-pana-
> relay@tools.ietf.org; 'Stephen Farrell'
> Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
> 
> On Jun 24, 2011, at 10:09, Alper Yegin wrote:
> 
> > PRE/PAA security is OPTIONAL since PANA messages are designed to be
> > used in untrusted networks, but if cryptographic mechanism is
> > supported, it SHOULD be IPsec. When the device characteristics
> preclude
> > support for IPsec, an alternative mechanism such as DTLS [REF], or
> > link-layer cryptographic security, etc. may be used instead. This
> section
> > describes how IPsec [RFC4301] can be used for securing the PANA relay
> > messages.
> 
> It would be useful to be very explicit what the objectives for this
> "PRE/PAA security" might be.
> Section 6 seems to suggest there is no real need for this at all (but
> then nebulously talks about "residual risks").
> So, unless we say what this is good for, it is hard to assess whether
> the "PRE/PAA security" is actually meeting those objectives.
> (E.g., if the purpose is DoS mitigation, a security scheme that is as
> susceptible to DoS attacks as the PAA itself, isn't that useful.)
> 
> Gruesse, Carsten


From jari.arkko@piuha.net  Thu Jun 30 14:01:06 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 509A821F86C0 for <pana@ietfa.amsl.com>; Thu, 30 Jun 2011 14:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.314
X-Spam-Level: 
X-Spam-Status: No, score=-102.314 tagged_above=-999 required=5 tests=[AWL=0.285, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EdtQNdcx2-4e for <pana@ietfa.amsl.com>; Thu, 30 Jun 2011 14:01:05 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id A26A221F86BF for <pana@ietf.org>; Thu, 30 Jun 2011 14:01:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8BE5E2CEA0; Fri,  1 Jul 2011 00:01:04 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izZKL9XSFITR; Fri,  1 Jul 2011 00:01:03 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 3424D2CC39; Fri,  1 Jul 2011 00:01:03 +0300 (EEST)
Message-ID: <4E0CE40F.10202@piuha.net>
Date: Thu, 30 Jun 2011 23:01:03 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
References: <4DF04217.3080304@toshiba.co.jp>	<6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com> <4E037A9D.8080200@piuha.net> <021a01cc3246$0b890390$229b0ab0$@yegin@yegin.org>
In-Reply-To: <021a01cc3246$0b890390$229b0ab0$@yegin@yegin.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ohba-pana-relay@tools.ietf.org, 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>, pana@ietf.org
Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 21:01:06 -0000

I'm fine this version as well.

jari

Alper Yegin kirjoitti:
> I think importing text from the other one Stephen had suggested would be an
> improvement. Like this:
>
>
> 3. Security of Messages Sent between PRE and PAA
>
> PRE/PAA security is OPTIONAL since PANA messages are designed to be
> used in untrusted networks, but if cryptographic mechanism is
> supported, it SHOULD be IPsec. When the device characteristics preclude
> support for IPsec, an alternative mechanism such as DTLS [REF], or
> link-layer cryptographic security, etc. may be used instead. This section
> describes how IPsec [RFC4301] can be used for securing the PANA relay
> messages.
>
> Alper
>
>
>
>
>   
>> -----Original Message-----
>> From: Jari Arkko [mailto:jari.arkko@piuha.net]
>> Sent: Thursday, June 23, 2011 8:41 PM
>> To: Yoshihiro Ohba; pana@ietf.org
>> Cc: Stephen Farrell; draft-ohba-pana-relay@tools.ietf.org
>> Subject: IESG discussions on draft-ohba-pana-relay
>>
>> We discussed this draft today. The remaining Discuss was about how
>> mandatory we should make IPsec. You had discussed about a SHOULD with
>> Stephen. I suggested that while interoperability is useful and
>> mandatory-to-implement mechanisms are good for it, we also have to talk
>> about how much value we bring with a security mechanism. In this case
>> there are some issues like MITMs able to block PANA packets. However,
>> some of these vulnerabilities are not helped by relay - PAA security,
>> as
>> the relay can still do bad things, and because ARP/ND vulnerabilities
>> between the client and relay in any case make it possible to become a
>> MITM. Stephen had some suggested text that I agree with:
>>
>> "PRE/PAA security is OPTIONAL since PANA messages are designed to be
>> used in untrusted networks, but if cryptographic mechanism is
>> supported,
>> it SHOULD be IPsec."
>>
>> Jari
>>     
>
>
>   


From jari.arkko@piuha.net  Thu Jun 30 14:11:38 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D74F11E8245 for <pana@ietfa.amsl.com>; Thu, 30 Jun 2011 14:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.33
X-Spam-Level: 
X-Spam-Status: No, score=-102.33 tagged_above=-999 required=5 tests=[AWL=0.269, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COkwb2nGem4t for <pana@ietfa.amsl.com>; Thu, 30 Jun 2011 14:11:38 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 34F7311E8267 for <pana@ietf.org>; Thu, 30 Jun 2011 14:11:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5EAEE2CEA0; Fri,  1 Jul 2011 00:11:15 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZ4oUUrngrX6; Fri,  1 Jul 2011 00:11:11 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 603E52CC39; Fri,  1 Jul 2011 00:11:11 +0300 (EEST)
Message-ID: <4E0CE66F.2040203@piuha.net>
Date: Thu, 30 Jun 2011 23:11:11 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <4DF04217.3080304@toshiba.co.jp>	<6491375641982933760@unknownmsgid>	<BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com>	<4E037743.2060602@gridmerge.com> <4E037A9D.8080200@piuha.net> <4E03EABF.501@net-zen.net> <4E04595B.4070908@cs.tcd.ie>
In-Reply-To: <4E04595B.4070908@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ohba-pana-relay@tools.ietf.org, pana@ietf.org
Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 21:11:38 -0000

Stephen, Glen,

>>> "PRE/PAA security is OPTIONAL since PANA messages are designed to be
>>> used in untrusted networks, but if cryptographic mechanism is supported,
>>> it SHOULD be IPsec."
>>>       
>> This is an interesting statement.  Just one question: if it is not
>> possible to use the protocol in a secure fashion (the claim being that
>> MITM attacks are impossible to prevent), how is it that the protocol is
>> "designed to be used in untrusted networks"?
>>     
>
> So the suggested text does assume that the pana messages are well
> protected between the PaC and PAA and that the PRE is security-wise
> just the same as any old router on the path.
>
> If pana messages are actually commonly sent that are vulnerable to
> some attacks on the messages themselves, then IPsec between the PRE
> and PAA would add enough value that I'd want it as a SHOULD.
>
> However, I'm told that this is not the case and so the text above
> should be fine.
>
> But if the reality differs, I'd like to know about that.
>   

Obviously, we do not necessarily know what the reality will be with PANA 
use, there is not much deployed practice to look at. I think most people 
would run a cryptographically well designed EAP methods.

My point was that even with such methods, a MITM can cause PANA to fail 
and network access to be prevented. This is true of many things, 
including IPsec. If I'm in a position to drop selected messages, for 
instance, I can prevent an IPsec tunnel from being established. Still, 
we like to think that IPsec has been designed to be used in untrusted 
environments. It just cannot deal with all types of attacks, just with 
some. Just like PANA.

I have sent an approved message for this draft with an RFC Editor note 
using Alper's suggested text. If there are further text tweaks please 
handle them in AUTH48. If there is further discussion of bigger issues, 
we can bring the document back for another look at the IESG.

Jari

