RE: Call for volunteers for C/C++ API liaison manager

["Dearlove, Christopher (UK)" <[e-mail]>]

C++ has now standardised multithreading, from the 2011 C++ standard (C++11).

-- 
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: [phone] |  Fax: [phone]
[e-mail] | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf [mailto:[e-mail]] On Behalf Of Alessandro Vesely
Sent: 02 May 2014 13:13
To: [e-mail]
Cc: IAB
Subject: Re: Call for volunteers for C/C++ API liaison manager

----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
Consider carefully whether you should click on any links, open any attachments or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.
--------------------------------------------------------

On Thu 01/May/2014 04:36:49 +0200 Melinda Shore wrote:
> 
> I'm thinking of IPSec, newer DNS features, etc.  I think it's very 
> much in the interest of the IETF to have someone around who can talk 
> to some of the language standards bodies about how to expose protocol 
> features, how to deal with options, etc.

+1.  But I don't think the call refers to "language standards".  C and
C++, in particular, don't standardize such fundamental features as
multithreading.  Although it mentioned WG14 and WG21, the IAB call didn't say ISO/IEC JTC1/SC22 also participates in the Single Unix Specification, which would seem a more appropriate place for Internet related APIs.

Ale


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************