from Wiktionary, Creative Commons Attribution/Share-Alike License

  • Asynchronous Transfer Mode Adaption Layer Type 5, ATM Adaption Layer Type 5.


Sorry, no etymologies found.


  • A 48 byte MTU is too small, so we use an encapsulation called AAL5, which takes 8 bytes from the last cell in a set, and lets you have up to 65535 bytes of payload.

    Archive 2010-02-01

  • It also works well for AAL5; AAL5 uses 8 bytes from every group of up to 1366 cells, leaving 40 bytes in that cell and 48 bytes in the remaining cells in the group for user data; two 188 byte packets plus 8 bytes of AAL5 overhead fit precisely in 8 cells with no padding.

    How a 1980s telecoms compromise helped set the Bluray video format.

  • A 1478 byte MTU, with the 10 bytes of PPP and AAL5 overhead works out to precisely

    Archive 2010-02-01

  • This becomes 31 cells carrying 48 bytes of payload each, a cell carrying 44 bytes of payload and 4 bytes padding, and a cell carrying 40 bytes padding and 8 bytes of AAL5 overhead.

    Archive 2010-02-01

  • There are two sensible ATM Adaptation Layers for MPEG-2; AAL1, meant for constant bit rate services such as carrying a multiplex from BBC headquarters to the Freeview transmission sites around the country, and AAL5, for services that can cope with a long delay.

    How a 1980s telecoms compromise helped set the Bluray video format.

  • If you're doing PPPoA, this 1502 bytes becomes 31 cells containing 48 bytes of payload, and a cell containing 14 bytes payload, 26 bytes padding, and the 8 byte AAL5 trailer.

    Archive 2010-02-01

  • Two cells contain 48 bytes each of payload, and the last cell contains 40 bytes of padding, and 8 bytes of AAL5 trailer.

    Archive 2010-02-01

  • So, 100 bytes of payload in AAL5 is carried in 3 cells; the first two cells have 48 bytes each of the payload, and the last cell has 4 bytes of payload, 36 bytes of padding, and 8 bytes AAL5 trailer.

    Archive 2010-02-01

  • Providing a common API and software environment across the iSPAN series, the iWARE SDS is an integrated set of embedded firmware, protocol layers (MTP1-2, AAL5, SSCOP, SSCF, etc.), APIs, host drivers, and utilities that accelerates the development of applications and eases the integration of iSPAN modules. News Articles

  • IIRC, I once had a stack that started with an SONET physical entity, put ATM with AAL5 on top of that, ran 802.3 LANE with 802.2

    Citizendium, the Citizens' Compendium - Recent changes [en]


Log in or sign up to get involved in the conversation. It's quick and easy.