[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue I002 (Was Re: Proposed Resolution to PROT I-D Issues List)

To: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: Issue I002 (Was Re: Proposed Resolution to PROT I-D Issues List)
From: Andy Bierman <abierman@cisco.com>
Date: Fri, 11 Feb 2005 16:39:31 -0800
Cc: netconf@ops.ietf.org
In-reply-to: <p06200727be32fa641297@[192.168.2.2]>
References: <4.3.2.7.2.20050211124136.0270e4a8@fedex.cisco.com> <4.3.2.7.2.20050211124136.0270e4a8@fedex.cisco.com>

At 04:15 PM 2/11/2005, Margaret Wasserman wrote:

>A comment on issue I002:
>
>I002)
>
>Session ID)  How is this conveyed to the client?
>
>  ** OPEN **
>  Doesn't seem to be a mechanism for an app to know its
>  own session ID.
>
>
>I have suggested in the past that the server should return the session ID to the client in the server's <hello> message.  Is there some reason why that is impractical or undesirable?

no -- it needs to be specified in all the drafts.


>Margaret

Andy

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>

References:
- Proposed Resolution to PROT I-D Issues List
  - From: Andy Bierman <abierman@cisco.com>
- Issue I002 (Was Re: Proposed Resolution to PROT I-D Issues List)
  - From: Margaret Wasserman <margaret@thingmagic.com>

Prev by Date: Issue I002 (Was Re: Proposed Resolution to PROT I-D Issues List)
Next by Date: Re: Issue I002 (Was Re: Proposed Resolution to PROT I-D Issues List)
Previous by thread: Issue I002 (Was Re: Proposed Resolution to PROT I-D Issues List)
Next by thread: Re: Issue I002 (Was Re: Proposed Resolution to PROT I-D Issues List)
Index(es):
- Date
- Thread