![](https://dblp.uni-trier.de/img/logo.ua.320x120.png)
![](https://dblp.uni-trier.de/img/dropdown.dark.16x16.png)
![](https://dblp.uni-trier.de/img/peace.dark.16x16.png)
Остановите войну!
for scientists:
![search dblp search dblp](https://dblp.uni-trier.de/img/search.dark.16x16.png)
![search dblp](https://dblp.uni-trier.de/img/search.dark.16x16.png)
default search action
Francois Le Faucheur
Person information
Refine list
![note](https://dblp.uni-trier.de/img/note-mark.dark.12x12.png)
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2010 – 2019
- 2017
- [j3]Christian Jacquenet, Yannick Lair, Francois Le Faucheur, Kevin J. Ma, A. Jean Mahoney, Brian Rosen, Timothy B. Terriberry, Mo Zanaty, Roni Even, Bron Gondwana, Barry Leiba, Scott Mansfield, Bruce Gracie, Jaafar Elmirghanni, Gonzalo Camarillo, Robert Sparks, Russ Housley:
Standards News. IEEE Commun. Stand. Mag. 1(2): 13-19 (2017) - 2016
- [i26]Francois Le Faucheur, Gilles Bertrand, Iuniana Oprescu, Roy Peterkofsky:
Content Distribution Network Interconnection (CDNI) Logging Interface. RFC 7937: 1-63 (2016) - 2015
- [i25]Himanshu Shah, Eric C. Rosen, Francois Le Faucheur, Giles Heron:
IP-Only LAN Service (IPLS). RFC 7436: 1-32 (2015) - 2014
- [i24]Francois Le Faucheur, Roberta Maglione, Tom Taylor:
Multicast Control Extensions for the Access Node Control Protocol (ANCP). RFC 7256: 1-99 (2014) - 2013
- [i23]Ray van Brandenburg, Oskar van Deventer, Francois Le Faucheur, Kent Leung:
Models for HTTP-Adaptive-Streaming-Aware Content Distribution Network Interconnection (CDNI). RFC 6983: 1-45 (2013) - 2012
- [i22]Ben Niven-Jenkins, Francois Le Faucheur, Nabil Bitar:
Content Distribution Network Interconnection (CDNI) Problem Statement. RFC 6707: 1-32 (2012) - [i21]Lou Berger, Francois Le Faucheur, Ashok Narayanan:
RSVP ASSOCIATION Object Extensions. RFC 6780: 1-17 (2012) - 2011
- [i20]Francois Le Faucheur:
IP Router Alert Considerations and Usage. RFC 6398: 1-19 (2011) - [i19]Francois Le Faucheur, James M. Polk, Ken Carlberg:
RSVP Extensions for Admission Priority. RFC 6401: 1-32 (2011) - [i18]Michael H. Behringer, Francois Le Faucheur, Brian Weis:
Applicability of Keying Methods for RSVP Security. RFC 6411: 1-19 (2011) - 2010
- [i17]Francois Le Faucheur, Jukka Manner
, Dan Wing, Allan Guillou:
Resource Reservation Protocol (RSVP) Proxy Approaches. RFC 5945: 1-50 (2010) - [i16]Francois Le Faucheur, Jukka Manner
, Ashok Narayanan, Allan Guillou, Hemant Malik:
Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy. RFC 5946: 1-35 (2010) - [i15]Bruce Davie, Francois Le Faucheur, Ashok Narayanan:
Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs. RFC 6016: 1-38 (2010)
2000 – 2009
- 2009
- [j2]Javed Asghar, Francois Le Faucheur, Ian Hood:
Preserving Video Quality in IPTV Networks. IEEE Trans. Broadcast. 55(2): 386-395 (2009) - [i14]Francois Le Faucheur, Eric C. Rosen:
Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop. RFC 5549: 1-10 (2009) - 2007
- [i13]Jeremy De Clercq, Dirk Ooms, Stuart Prevost, Francois Le Faucheur:
Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE). RFC 4798: 1-14 (2007) - [i12]Francois Le Faucheur:
Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels. RFC 4804: 1-31 (2007) - [i11]Francois Le Faucheur, Bruce Davie, Pratik Bose, Chris Christou, Michael Davenport:
Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations. RFC 4860: 1-32 (2007) - 2006
- [i10]Jeremy De Clercq, Dirk Ooms, Marco Carugi, Francois Le Faucheur:
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN. RFC 4659: 1-18 (2006) - 2005
- [j1]Mallik Tatipamula, Francois Le Faucheur, Tomohiro Otani, Hiroshi Esaki:
Implementation of IPv6 services over a GMPLS-based IP/optical network. IEEE Commun. Mag. 43(5): 114-122 (2005) - [i9]Francois Le Faucheur:
Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering. RFC 4124: 1-37 (2005) - [i8]Francois Le Faucheur, Wai Sum Lai:
Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering. RFC 4125: 1-12 (2005) - [i7]Francois Le Faucheur:
Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering. RFC 4127: 1-13 (2005) - 2004
- [i6]Francois Le Faucheur, Ramesh Uppili, Alain Vedrenne, Pierre Merckx, Thomas Telkamp:
Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric. RFC 3785: 1-8 (2004) - 2003
- [i5]Francois Le Faucheur, Wai Sum Lai:
Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering. RFC 3564: 1-22 (2003) - 2002
- [i4]Francois Le Faucheur, Liwen Wu, Bruce Davie, Shahram Davari, Pasi Vaananen, Ram Krishnan, Pierrick Cheval, Juha Heinänen:
Multi-Protocol Label Switching (MPLS) Support of Differentiated Services. RFC 3270: 1-64 (2002) - 2001
- [i3]David L. Black, Scott W. Brim, Brian E. Carpenter
, Francois Le Faucheur:
Per Hop Behavior Identification Codes. RFC 3140: 1-8 (2001) - [i2]Fred Baker, Carol Iturralde, Francois Le Faucheur, Bruce Davie:
Aggregation of RSVP for IPv4 and IPv6 Reservations. RFC 3175: 1-36 (2001) - 2000
- [i1]Scott W. Brim, Brian E. Carpenter
, Francois Le Faucheur:
Per Hop Behavior Identification Codes. RFC 2836: 1-7 (2000)
Coauthor Index
![](https://dblp.uni-trier.de/img/cog.dark.24x24.png)
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from ,
, and
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and
to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-24 23:21 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint