From c4a0eb2fb9b610cf71ee9c6706409308b4d2dd58 Mon Sep 17 00:00:00 2001 From: Ram Mohan R Date: Tue, 11 Aug 2015 14:48:31 +0530 Subject: [PATCH 1/2] Update draft-ietf-rtcweb-stun-consent-freshness.xml Barry's comments on Consent draft --- draft-ietf-rtcweb-stun-consent-freshness.xml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/draft-ietf-rtcweb-stun-consent-freshness.xml b/draft-ietf-rtcweb-stun-consent-freshness.xml index 27f8ae9..0fd56bc 100644 --- a/draft-ietf-rtcweb-stun-consent-freshness.xml +++ b/draft-ietf-rtcweb-stun-consent-freshness.xml @@ -263,7 +263,7 @@
A full ICE implementation obtains consent to send using ICE. After ICE concludes on a particular candidate pair and whenever the endpoint - sends application data on that pair consent MUST be maintained + sends application data on that pair consent is maintained following the procedure described in this document. An endpoint MUST NOT send data other than the messages used to @@ -429,9 +429,6 @@ - - @@ -445,6 +442,8 @@ + + From 87b0146cc5231151c5996e7a70c4ea7ccad8bfd7 Mon Sep 17 00:00:00 2001 From: Ram Mohan R Date: Tue, 11 Aug 2015 17:55:47 +0530 Subject: [PATCH 2/2] Update draft-ietf-rtcweb-stun-consent-freshness.xml Few more comments of Bary to move rfc6263, rtcweb-security drafts to informative section from normative reference --- draft-ietf-rtcweb-stun-consent-freshness.xml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/draft-ietf-rtcweb-stun-consent-freshness.xml b/draft-ietf-rtcweb-stun-consent-freshness.xml index 0fd56bc..7c8f628 100644 --- a/draft-ietf-rtcweb-stun-consent-freshness.xml +++ b/draft-ietf-rtcweb-stun-consent-freshness.xml @@ -425,11 +425,7 @@ - - - - @@ -444,6 +440,8 @@ + +