Forwarding to SIMPLE mailing list...
-Original Message-
From: Pandurangan R S [mailto:pandurangan@gmail.com]
Sent: Friday, April 09, 2010 12:07 PM
To: Vavilapalli Srikanth-A19563
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Question on RFC 4662
RFC 4662 states
The third mandatory attribute is "fullState". The "fullState"
attribute indicates whether the NOTIFY message contains information
for every resource in the list. If it does, the value of the
attribute is "true" (or "1"); otherwise, it is "false" (or "0"). The
firs
Responses inline
Regards
Ranjit
-Original Message-
From: Vavilapalli Srikanth-A19563
Sent: Friday, April 09, 2010 11:27 AM
To: Avasarala Ranjit-A20990
Cc: 'sip-implementors@lists.cs.columbia.edu'
Subject: RE: [Sip-implementors] Question on RFC 4662 - Resource List
Subscr
Avasarala Ranjit-A20990
Sent: Friday, April 09, 2010 11:15 AM
To: Vavilapalli Srikanth-A19563
Cc: sip-implementors@lists.cs.columbia.edu
Subject: RE: [Sip-implementors] Question on RFC 4662 - Resource List
Subscription
Hi Srikant
RFC 4662 mandates the presence of "fullstate" attrib
alf Of
Vavilapalli Srikanth-A19563
Sent: Friday, April 09, 2010 10:49 AM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Question on RFC 4662 - Resource List
Subscription
Hi
I have a question related to first NOTIFY being generated for a Resource
List Subscription assuming wher
Hi
I have a question related to first NOTIFY being generated for a Resource
List Subscription assuming where the all the entities support only
unreliable UDP transport and message size is limitied by path MTU size
(because of for ex. No support for UDP fragmentation by the intermediate
routers on
