IETF Logo Mail Archive

Re: [its] New draft on scenarios and requirements for IP in ITS

Rex Buddenberg <budden@nps.navy.mil> Fri, 13 July 2012 17:35 UTC

Return-Path: <budden@nps.edu>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F51221F867F for <its@ietfa.amsl.com>; Fri, 13 Jul 2012 10:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFXLfcJXs4tc for <its@ietfa.amsl.com>; Fri, 13 Jul 2012 10:35:29 -0700 (PDT)
Received: from mule.nps.edu (mule.nps.edu [205.155.65.106]) by ietfa.amsl.com (Postfix) with ESMTP id 71F8421F867E for <its@ietf.org>; Fri, 13 Jul 2012 10:35:29 -0700 (PDT)
X-ASG-Debug-ID: 1342200966-036c9204953ab370001-m4RtKs
Received: from gulfstream.ern.nps.edu (gulfstream.ern.nps.edu [172.20.24.113]) by mule.nps.edu with ESMTP id Cm8kfsUyG4kVr9Ll; Fri, 13 Jul 2012 10:36:06 -0700 (PDT)
X-Barracuda-Envelope-From: budden@nps.edu
Received: from [172.20.58.67] (172.20.58.67) by smtp.nps.edu (172.20.24.113) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 13 Jul 2012 10:36:04 -0700
From: Rex Buddenberg <budden@nps.navy.mil>
X-ASG-Orig-Subj: Re: [its] New draft on scenarios and requirements for IP in ITS
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <5000551E.9000800@gmail.com>
References: <5000551E.9000800@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 13 Jul 2012 10:35:12 -0700
Message-ID: <1342200913.981.57.camel@localhost.localdomain>
MIME-Version: 1.0
X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14)
Content-Transfer-Encoding: 7bit
X-Barracuda-Connect: gulfstream.ern.nps.edu[172.20.24.113]
X-Barracuda-Start-Time: 1342200966
X-Barracuda-URL: http://205.155.65.106:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at nps.edu
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.102596 Rule breakdown below pts rule name description ---- ---------------------- --------------------------------------------------
Cc: "its@ietf.org" <its@ietf.org>
Subject: Re: [its] New draft on scenarios and requirements for IP in ITS
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Intelligent Transportation Systems discussion list." <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/its>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 17:35:30 -0000

Alex,

Suggest an additional scenario: voyage planning.  In this case, the
automobile navigator needs road, weather and other information from
external.  In addition, the navigator will need internal information
(e.g. how full is fuel tank?).  
	
Increasingly, the external information is migrating to Common Alerting
Protocol data format (an XML schema).



Scenario 2 outlines a solution, but not a problem.



On Fri, 2012-07-13 at 19:04 +0200, Alexandru Petrescu wrote:
> Participants to ITS informal effort at IETF,
> 
> Per our recent discussions, we submitted a new draft about scenarios and
> requirements for IP in ITS:
> 
>           draft-petrescu-its-scenarios-reqs-01.txt
> 
> I would like to request feedback about the scenarios and requirements
> described in this draft.
> 
> Thanks in advance,
> 
> Alex and on behalf of co-authors.
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its

v2.23.0 | Report a Bug | By Email