headers
Chenxin (Xin | 15 May 2013 03:40
Favicon

FW: New Version Notification for draft-chenxin-behave-turn-websocket-00.txt

This draft defines a websocket extension to TURN to make TURN data have the ability to transport over the
websocket connection.

This method could be a option to solve the Http-fallback requirement in RTCWEB. 

    F37            The browser MUST be able to send streams and
                   data to a peer in the presence of FWs that only
                   allows http(s) traffic.

Besides, Turn server with websokcet extension could be a general relay server for some over websocket
protocol, such as BFCP over websocket or MSRP over websocket. This could satisfy some Peer to Peer scene
when using these protocol in the web environment , without a specific center server.

Comments and suggestions are welcome.

Best Regards,
     Xin 

-----Original Message-----
From: internet-drafts <at> ietf.org [mailto:internet-drafts <at> ietf.org] 
Sent: Tuesday, May 14, 2013 9:15 AM
To: Chenxin (Xin); Chenxin (Xin)
Subject: New Version Notification for draft-chenxin-behave-turn-websocket-00.txt

A new version of I-D, draft-chenxin-behave-turn-websocket-00.txt
has been successfully submitted by Xin Chen and posted to the
IETF repository.

Filename:	 draft-chenxin-behave-turn-websocket
Revision:	 00
(Continue reading)

Permalink | Reply | 9 comments |
headers
Ram Mohan R (rmohanr | 5 May 2013 19:41
Picon
Favicon

FW: New Version Notification for draft-reddy-behave-turn-auth-01.txt

This draft is a revision to the earlier version by incorporating the
comments given by Simon Perreault.

comments and suggestions are welcome.

Best Regards,
Authors.

> On 05/05/13 11:07 PM, "internet-drafts <at> ietf.org"
><internet-drafts <at> ietf.org> wrote:

>
>A new version of I-D, draft-reddy-behave-turn-auth-01.txt
>has been successfully submitted by Tirumaleswar Reddy and posted to the
>IETF repository.
>
>Filename:	 draft-reddy-behave-turn-auth
>Revision:	 01
>Title:		 Problems with STUN Authentication for TURN
>Creation date:	 2013-05-05
>Group:		 Individual Submission
>Number of pages: 7
>URL:             
>http://www.ietf.org/internet-drafts/draft-reddy-behave-turn-auth-01.txt
>Status:          
>http://datatracker.ietf.org/doc/draft-reddy-behave-turn-auth
>Htmlized:        
>http://tools.ietf.org/html/draft-reddy-behave-turn-auth-01
>Diff:            
>http://www.ietf.org/rfcdiff?url2=draft-reddy-behave-turn-auth-01
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan Wing | 4 May 2013 00:43
Picon
Favicon

call for adoption, draft-penno-behave-rfc4787-5382-5508-bis

The authors of draft-penno-behave-rfc4787-5382-5508-bis have asked that it become a working group
document.  Please send review nits, spelling corrections, and suchlike to the authors.  Please send
feedback about this becoming a working group document to the chairs, authors, or list, as you feel
appropriate; clear indications of 'support' or 'do not support' are appreciated.  

  http://tools.ietf.org/html/draft-penno-behave-rfc4787-5382-5508-bis-04

-d
Permalink | Reply | 6 comments |
headers
Tom Taylor | 3 May 2013 03:07
Picon

SYSLOG strategy for organizing NAT logging event parameters

In organizing the encoding for the SYSLOG approach, I need to decide how 
to define the structured data elements. Each such element is identified 
by an SD-ID and contains a specified set of parameters.

I have eight events in all (including "invalid port detected"), and 
twenty different parameters. The accounting is a little different from 
IPFIX because some IPFIX parameters end up in the SYSLOG headers 
instead. One parameter is common to all of the events, a few are common 
to at least four of them, and the rest are more scattered. There may be 
some reconciliation required when I submit the SYSLOG update.

The question is how to define the structured data elements. Here are the 
possibilities:

(a) define only one structured data element, within which all parameters 
are optional from the point of view of SYSLOG, but individual parameters 
may be mandatory from the application point of view depending on the 
event type. Every event would use the same structured data element.

(b) define one structured data element per event, with mandatory and 
optional parameters as required. The same parameter would then be 
registered formally with IANA once for each event using it.

(c) variation on (a): partition the parameters amongst multiple 
structured data elements, more than one of which may be needed to make 
up a complete event report. One possible use is to group parameters 
relating to a given NAT type. The disadvantage is a bit longer log 
lengths because of the additional structured data headers.

Are there any opinions on all this? SYSLOG is defined in RFC 5424.
(Continue reading)

Permalink | Reply | 3 comments |
headers
ietfdbh | 3 May 2013 01:14
Picon

nat-mib-06: separate MIB modules

Hi,

I would like to suggest a change.
If I understand correctly, this document deprecates the entire RFC4008
NAT-MIB, and proposes a completely new MIB under the same name.
I think this is sub-optimal.
In NMS applications that support multiple devices, some of which support
RFC4008 and some of which support this new MIB module, it will be
potentially confusing to call them by the same name.
You really have two completely different MIB modules that you are trying to
sell under the same name.
I think that is not a good idea.

I recommend writing an RFC4008bis document to deprecate the RFC4008 NAT-MIB.
Then put your proposed new MIB objects into a separate MIB module, using a
different name for the newly designed MIB for managing NATs
(maybe NEW-NAT-MIB, but I'd hope for something that more accurately
describes the modified purpose of the MIB, maybe NAT-MONITORING-MIB)
Put this in a separate RFC.

I think that would be a much cleaner solution, and much more obvious what
you are doing here.

David Harrington
ietfdbh <at> comcast.net
+1-603-828-1401

-----Original Message-----
From: behave-bounces <at> ietf.org [mailto:behave-bounces <at> ietf.org] On Behalf Of
Simon Perreault
(Continue reading)

Permalink | Reply | 2 comments |
headers
internet-drafts | 1 May 2013 10:28
Picon
Favicon

I-D Action: draft-ietf-behave-nat-mib-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.

	Title           : Additional Managed Objects for Network Address Translators (NAT)
	Author(s)       : Simon Perreault
                          Tina Tsou
                          Senthil Sivakumar
	Filename        : draft-ietf-behave-nat-mib-06.txt
	Pages           : 82
	Date            : 2013-05-01

Abstract:
   This memo defines a portion of the Management Information Base (MIB)
   for devices implementing Network Address Translator (NAT) function.
   This MIB module may be used for monitoring of a device capable of NAT
   function.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-behave-nat-mib

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-behave-nat-mib-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-behave-nat-mib-06

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
(Continue reading)

Permalink | Reply | 1 comment |
headers
johnsonhammond2 | 27 Apr 2013 19:14
Favicon

Biggest Fake Conference in Computer Science

Biggest Fake Conference in Computer Science

We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.

We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware

Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 

We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tom Taylor | 25 Apr 2013 13:35
Picon

NAT Logging -- Port violation event for MAP-E or LW4over6 BR

The MAP-E and LW4over6 border routers are responsible for checking that 
the ports assigned by the CE are within the set allocated to that CE. I 
think we need a NAT logging event to report detection of an out-of-range 
port.

Tom Taylor
Permalink | Reply | 3 comments |
headers
Tirumaleswar Reddy (tireddy | 24 Apr 2013 05:22
Picon
Favicon

FW: New Version Notification for draft-reddy-behave-turn-auth-00.txt

This draft discusses some of the problems with current TURN authentication so that it can serve as the basis
for stronger TURN authentication mechanisms.  

comments and suggestions are welcome.

Best Regards,
--Authors.

-----Original Message-----
From: internet-drafts <at> ietf.org [mailto:internet-drafts <at> ietf.org] 
Sent: Tuesday, April 23, 2013 6:04 PM
To: Ram Mohan R (rmohanr); Tirumaleswar Reddy (tireddy); Muthu Arul Mozhi Perumal (mperumal); Alper
Yegin; Ram Mohan R (rmohanr); Alper E. Yegin; Muthu Arul Mozhi Perumal (mperumal)
Subject: New Version Notification for draft-reddy-behave-turn-auth-00.txt

A new version of I-D, draft-reddy-behave-turn-auth-00.txt
has been successfully submitted by Tirumaleswar Reddy and posted to the
IETF repository.

Filename:	 draft-reddy-behave-turn-auth
Revision:	 00
Title:		 Problems with TURN Authentication
Creation date:	 2013-04-23
Group:		 Individual Submission
Number of pages: 6
URL:             http://www.ietf.org/internet-drafts/draft-reddy-behave-turn-auth-00.txt
Status:          http://datatracker.ietf.org/doc/draft-reddy-behave-turn-auth
Htmlized:        http://tools.ietf.org/html/draft-reddy-behave-turn-auth-00

Abstract:
(Continue reading)

Permalink | Reply | 6 comments |
headers
Tom Taylor | 19 Apr 2013 22:03
Picon

NAT logging for DS-Lite

I think we have to add a parameter to the session records for logging at 
the DS-Lite AFTR. Since the source IPv4 address may not be unique, the 
IPv6 tunnel address should also be logged.

Is there enough deployment of GW-initiated DS-Lite that we should be 
considering other types of tunnel identifier too?

Tom Taylor
Permalink | Reply | 1 comment |
headers
Tom Taylor | 11 Apr 2013 17:43
Picon

IETF86 minutes

I looked over the IETF86 minutes in preparation for updating the Syslog 
draft and noted that a bit was missing from the discussion at the end of 
the logging topic. We agreed, I believe, that it might be practical to 
do per-session logging using Syslog in specific situations where the 
number of events per second was limited. As a result, per-session 
logging would also be added to the Syslog draft along with an 
applicability statement.

Tom Taylor
Permalink | Reply | 0 comments |

Gmane