Search results

From RFC-Wiki
  • | global routing prefix | subnet ID | interface ID | site, and the interface ID is as defined in section 2.5.1 of [ARCH].
    8 KB (1,020 words) - 05:02, 4 October 2020
  • allow system administrators to change. The specific variable names, ISATAP interface:
    24 KB (3,320 words) - 17:11, 4 October 2020
  • allow system administrators to change. The specific variable names, ISATAP interface:
    24 KB (3,302 words) - 13:38, 11 October 2020
  • misconfigurations by users or administrators, or possibly malicious interface, causing incorrect RAs to appear on links and causing hosts
    30 KB (4,569 words) - 03:21, 22 October 2020
  • administrators apply coherent BGP policies. routing environment, and network administrators SHOULD carefully
    48 KB (7,283 words) - 07:56, 2 October 2020
  • manual keying mechanism and provides the interface for future message AO's current manual keying have the following interface:
    26 KB (3,564 words) - 14:59, 21 October 2020
  • o The system should expose the archive using an IMAP interface, with o This interface must work with standard IMAP clients.
    8 KB (1,155 words) - 23:23, 1 October 2020
  • primitive interface. constitutes authorization. The network administrators of a pool need
    31 KB (4,535 words) - 17:01, 11 October 2020
  • interface that the recipient will experience. Differences in the user interface could include localization information or commercial
    21 KB (2,875 words) - 18:02, 11 October 2020
  • domain administrators can direct clients towards more capable == Advice for DNS Administrators ==
    26 KB (4,019 words) - 01:27, 4 October 2020
  • out common mistakes system administrators tend to make and why they zone files have mostly been configured by system administrators, by
    17 KB (2,727 words) - 08:56, 18 October 2020
  • interface (except decremented by 1). Therefore, the internal administrators of the respective firewalls.
    25 KB (3,789 words) - 00:26, 20 October 2020
  • It is suggested that administrators configure their SNMPv2 entities It is suggested that administrators configure their SNMPv2 entities
    22 KB (2,978 words) - 11:48, 19 October 2020
  • | 1 | Interface-Local scope | [[RFC4291]], [[RFC7346|RFC 7346]] | Interface-Local, Link-Local, and Realm-Local scope boundaries are
    10 KB (1,224 words) - 05:50, 2 October 2020
  • network administrators have been facing, and then it describes IPFIX parallel. Network administrators need to adjust the parameters of
    46 KB (6,311 words) - 01:08, 22 October 2020
  • administrators and future protocol developers. The primary intent of includes network administrators and future protocol developers.
    38 KB (5,893 words) - 04:34, 22 October 2020
  • and Application Programming Interface (API) issues relating to using Programming Interface (API), the application can issue a system call
    30 KB (4,745 words) - 16:42, 11 October 2020
  • FR interface by a Data Link Connection Identifier (DLCI). [[RFC1294|RFC 1294]] capability [2]. Under the NBMA model, the physical FR interface on a
    13 KB (1,973 words) - 09:29, 18 October 2020
  • used to describe handle administrators or administrator groups. HS_SITE is a pre-defined data type to describe the service interface
    90 KB (12,362 words) - 06:17, 4 October 2020
  • There is only one type of interface that VNS routing supports and simply forwarded to the specified network layer interface and sent to
    25 KB (4,138 words) - 23:10, 29 September 2020

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)