Le 2015-10-12 01:49, Meral Shirazipour a écrit :
> Minor issues:
> -[Page 7], Section 4.1, "If the PCP Client does not know the exact number of
> ports its requires, it MAY then set the Port Set Size to 0x, indicating
> that it is willing to accept as many ports as the PCP server can offer."
Le 2014-07-26 11:00, Brian E Carpenter a écrit :
Problem 6 (Hosting multiple realms on a single IP address is challenging...)
doesn't really seem to be a problem with authentication as such, so while
it's clearly a problem, is it in scope? It isn't quite clear to me that
there's a security
On 27 juillet 2014 16:40:40 HAE, Brian E Carpenter
brian.e.carpen...@gmail.com wrote:
Bonjour Simon,
On 28/07/2014 03:09, Simon Perreault wrote:
Le 2014-07-26 11:00, Brian E Carpenter a écrit :
Problem 6 (Hosting multiple realms on a single IP address is
challenging...)
doesn't really seem
On 07/03/12 05:51, Eggert, Lars wrote:
On Jul 3, 2012, at 14:24, Alexey Melnikov wrote:
I found it is to be odd to have a requirements document as a BCP, but I am sure
you can sort the right status out with IESG.
+1
I fail to see why Informational wouldn't be the better status.
I don't
On 2011-05-24 15:42, Russ Housley wrote:
Sorry for the delayed response. I would prefer the use of confidentiality
instead of privacy in the paragraph. That would better align with the
definitions in RFC 2828.
I'll make the change.
Thanks,
Simon
--
DTN made easy, lean, and smart --
On 2011-04-09 08:03, kathleen.moria...@emc.com wrote:
The last is not a Gen-ART, but was put
there for adding considerations to the security section. I just
meant that it should state that there may be privacy concerns with
some of the information. I listed the regulations to give examples,
On 2011-04-11 09:42, kathleen.moria...@emc.com wrote:
Thank you for the update. How about the following which slightly changes
your proposed text:
o vCards often carry information that can be sensitive (e.g.
birthday, address, and phone information). Although vCards have no
On 04/08/2011 11:21 PM, kathleen.moria...@emc.com wrote:
Section 3.2, paragraph 2:
It reads as a 4 element list instead of 2, here is one option:
Change from: (space, ASCII decimal 32, or horizontal tab, ASCII decimal 9).
To: (space (ASCII decimal 32) or horizontal tab (ASCII decimal 9)).
On 04/08/2011 05:45 PM, Mary Barnes wrote:
Major issue:
- The document is listed as Standards Track but but does not contain the
RFC 2119 boilerplate. There is some RFC 2119 terminology used, however,
there seems to be a lot of cases where RFC 2119 language is appropriate
but not used.
Right.
McCann Peter-A001034 wrote, on 01/04/10 11:16 AM:
TURN can run over UDP and TCP,
as it allows for a client to request address/port pairs for receiving
both UDP and TCP.
Should say and instead of as.
Will be fixed.
Thanks for the review!
Simon
--
NAT64/DNS64 open-source --
10 matches
Mail list logo